Quick overview
Job description
Role at a glance
We are rebuilding our web presence on the same principle we deliver on. The site is a technical asset, not a brochure, and it has to be legible to crawlers, to answer engines, and to the AI agents that increasingly stand between a CTO and a shortlist.
Our category claim is technical. The people we sell to are technical. But our site currently under-performs on exactly the dimensions our buyers would judge us on: rendering behaviour, structured data, Core Web Vitals, and crawl efficiency across a large migration of legacy URLs.
We are not hiring a keyword strategist. We are hiring the person who owns the machine-readable layer of Mactores, meaning the schema graph, the render path, the crawl budget, the redirect map and the performance envelope, and who can sit with an engineer, read the framework code, and say precisely what needs to change and why. The short version: if the fix requires a pull request, you should be able to specify it, review it, and defend it in code review, not file a ticket and hope.
This is a senior individual-contributor seat with high autonomy and direct influence over engineering priorities. You get ownership of a channel that matters to the business, an engineering-led firm that will actually implement what you specify including agent-assisted implementation, and compensation benchmarked to senior engineering rather than to marketing. It is the wrong role if your technical SEO work has been running an audit tool and forwarding the PDF to a developer, if you need someone else to tell you whether a page is server-rendered, or if you are looking to manage a team rather than do the work.
