Requirements

• At least five (5) years as a software engineer, including three (3) at the senior level, building front end for content-driven or marketing platforms.
• Real ownership of a content model in Sanity. You've designed schemas other people had to live with, and you have opinions about references vs. embedded objects, when a variant belongs in the schema versus at runtime, and how to stop a section library sprawling. GROQ and Portable Text are familiar territory.
• Deep front-end expertise: expert HTML, CSS and TypeScript, with a strong command of component API design and the developer experience of a shared library.
• You can work end to end. Comfortable owning the server side as well as the front end: SSR, serverless and edge runtimes, API routes, a SQL database, secrets and CI. You should be able to take a feature from schema to component to the route that serves it without handing off, and be happy debugging something that only reproduces in production.
• Solid understanding of responsive design, cross-browser compatibility and web performance, and comfortable building to WCAG 2.2 AA. Accessibility is part of your definition of done, not a separate pass.
• You care that marketing sites are measured, on performance, SEO, analytics events, and conversion, and you're happy being accountable to those numbers.
• A strong sense of craft and attention to detail, and the judgment to balance design intent against engineering constraints.
• Strong communication and collaboration skills. You explain your reasoning, review generously, and treat leveling up the people around you as part of the job.

Nice to haves

• Prior experience working on a large SaaS marketing website, at real traffic and with real stakes attached.
• Astro, or another islands or static-site framework.
• Cloudflare Workers, or another edge or serverless platform.
• Experience with AWS Lambda.
• Tailwind CSS v4, and experience working from a token-based design system.
• Experience, or strong interest, in making component libraries and content models consumable by AI agents.
• A strong design sensibility: an eye for visual detail and the judgment to push back on and improve design decisions, not just build them.
• Experience with localization and internationalization at scale for a global audience.
• Analytics and tag management implementation: dataLayer events, server-side tagging, getting attribution right without hurting performance.

What you'll be doing

• Build, scale, and evolve the section library: the Astro components, Sanity schemas, and design tokens that let us compose marketing pages consistently and accessibly.
• Own the content model. Design schemas that resist misuse, so an editor, or an agent, can build a page that is correct by construction rather than correct by review.
• Take Figma component specs all the way to production: responsive across mobile, tablet, and desktop, accessible by default, matching design intent precisely.
• Extend the platform for AI-assisted development, so coding agents can generate on-brand, on-spec sections from a design spec as reliably as a person can.
• Own SEO integrity as a first-class engineering concern: canonicals, sitemaps, structured data, redirects, and no traffic cliffs on launch.
• Raise the bar on engineering standards across the website surface: thorough code review, patterns others can follow, and tests around the parts that actually break.
• Maintain and extend localization across nine locales and a translation pipeline, so the system works for a global audience.
• Shape the technical direction of the website platform over the next 6 to 12 months and champion its adoption with the people who publish on it.

Perks and benefits

• Our preference is for this role to be based either in-office or remote in London, UK. We can also accommodate remote workers elsewhere in Europe subject to compliance and right to work checks.
• This is full-time employment only, usually through OysterHR. No contractors possible.