Technical SEO Engineer
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 1d ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 8d ago
The date the source published, not the day we noticed it (2026-09-23). Last seen at its source 1h ago.
We have tracked this listing since 23 Sep 2026 (8 days). The employer's own board has carried it every time we have read it, most recently 1 hour ago.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
Mumbai
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay $6,750–7,250/mo
Middle 50% of 9 listings that do state pay — Engineering · all levels · India · USD/month. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
lever employer's own board first seen 8d ago · last seen 1h ago
The listing
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.
What you'll do?
What we're looking for?
- A degree in Computer Science, Software Engineering, Information Technology or a closely related engineering discipline. This role requires someone who was trained to read and reason about code, not someone who picked up HTML alongside marketing work.
- 6+ years in a dedicated SEO role, with the majority of that time spent on the technical side rather than general digital marketing with SEO as one of several responsibilities.
- Demonstrable in-depth Schema.org expertise. You have designed a multi-entity graph from scratch and can explain the choices you made and what they earned.
- A proven record of guiding development teams through performance optimization, with before and after field data and a clear account of what you specified versus what the engineers built.
- Working proficiency in HTML, CSS and JavaScript, comfort reading a modern JS framework codebase, fluency with Git and pull-request review, and the ability to write Python or SQL for data work.
- Experience owning technical SEO through at least one large site migration or replatform.
- Written communication strong enough that an engineering lead reading your ticket knows exactly what to do and why it matters.
- Sustained availability for daily overlap with US hours.
You'll be preferred if you:
- Come from B2B technology or enterprise services, with long sales cycles, technical buyers and low-volume high-intent search.
- Are familiar with cloud, data or AI subject matter, and can hold a conversation about AWS, data platforms or agentic systems without a translator.
- Have hands-on experience with AI and LLM visibility, meaning how content gets retrieved, cited and surfaced by answer engines and agents.
- Have built your own tooling: crawlers, API pipelines, monitors, or scripts that replaced a manual process.
- Have done edge-compute or CDN-level SEO work in Cloudflare Workers, Lambda@Edge or similar.