01Overview
OverviewWe are looking for a Frontend Software Engineer (0-1 years of experience) to join our CMS engineering team, the entry step of our frontend track, with a mandate focused on content publishing and shipping pages at pace across our multibrand platform. This role isn't about waiting on tickets or filing them. It's about owning the pages themselves, building them, publishing them, and holding the quality bar on how they render, load, and perform. You'll sharpen your frontend fundamentals faster here than in almost any other role, because the volume of realworld pagebuilding is high and the platform demands care on rendering strategy, caching, and Web Vitals. You'll work inside a multibrand content platform: a headless CMS monorepo powered by Payload CMS and Next.js. Seven to eight brand sites and a checkout flow live in the same repository. Thousands of pages are moving off three legacy systems (WordPress, Java/Spring, Intercom) and each brand's marketing team needs a technical partner who can turn campaigns into live pages without every request becoming a platform ticket.
ResponsibilitiesOwn the page publishing pipeline across brands from brief to live hitting the platform's standards for rendering strategy, caching, and Core Web Vitals.Build and extend templates and blocks in the CMS component library using Next.js, TypeScript, and modern CSS.Make deliberate rendering decisions per page and component (static, ISR, SSR, clientside) based on content needs and performance budgets.Drive legacy migration at pace, moving pages from three legacy systems (WordPress, Java/Spring, Intercom) onto the new CMS without cutting corners on quality.Uphold Core Web Vitals, SEO, and accessibility standards on every page you ship.Own the quality of what goes live, not just the fact that it's live.Translate Figma designs accurately into web pages, with attention to typography, spacing, and visual polish that matches the design system.Partner daytoday with each brand's marketing team, turning campaign briefs into live pages without every request becoming an engineering ticket.Identify repeated patterns across brands and propose reusable components rather than oneoff builds.Train marketing teams to selfserve routine content updates, and document workflows and component usage so knowledge doesn't sit only with you.Use real pagebuilding experience to identify gaps in existing components and help drive the platform's evolution alongside the rest of the engineering team.Apply a bias toward shipping, balancing priorities with campaign calendars and moving quickly without sacrificing quality.Qualifications Must haveStrong HTML, CSS, and JavaScript fundamentals, with production experience building pages that other people rely on.Working knowledge of Next.js and/or Astro, including rendering strategy (static, ISR, SSR) and when each applies; comfortable moving between them or picking one up quickly.Comfortable with TypeScript and modern CSS (Flexbox, Grid, Tailwind or similar).Working understanding of caching fundamentals such as CDN caching, cache invalidation, and how content changes flow through to live pages.Working understanding of Core Web Vitals and how frontend decisions (bundle size, image handling, hydration cost) affect them.Fluent with reusable component systems, and instinct for when to compose existing components versus build new ones.Able to read Figma designs and translate them accurately, with attention to typography, spacing, and visual polish.Strong written and verbal communication; this role lives at the seam between engineering and marketing, and clear collaboration with nontechnical stakeholders is nonnegotiable.Ownership from brief to live, including SEO, performance, and accessibility as your responsibility rather than someone else's.Nice to HaveDirect experience with Payload CMS or another headless CMS (Contentful, Sanity, Strapi). CMSspecific training will be provided; direct experience is a strong plus.Familiarity with SEO fundamentals for content pages, including metadata, structured data, and schema.org.Working knowledge of CDN configuration and cache invalidation strategies (ISR, ondemand revalidation).Prior experience working closely with marketing or content teams, including exposure to campaign delivery cycles.Familiarity with monorepo tooling (Turborepo, Nx) or design token systems.Comfort with Git, pull request workflows, and code review culture.Why Join UsYou will work on a multibrand content platform, a headless CMS monorepo powered by Payload and Next.js, with Astro on the nearterm roadmap that is already beyond the proving stage. Seven to eight brand sites, a checkout flow, and thousands of pages moving off legacy systems onto a shared foundation. You will work alongside a dynamic engineering team focused on rapid delivery and quality. .
