Senior Frontend Engineer  

We are bringing our storefront in-house. You are the engineer who will own it.

Kitchen Warehouse is one of Australia’s largest specialty kitchenware retailers. We are building our engineering function in Manila and taking full ownership of our eCommerce platform. This is a foundational hire.

Our storefront runs on Nextjs with the Frontastic commerce frontend framework, sitting on CommerceTools. It is a large, live, revenue-carrying codebase with a substantial component library. What it has never had is a single owner. You will define the component patterns, lead the type safety work, and set the frontend standards the team works to. There is no management layer between you and the person accountable for the platform.

You are not inheriting someone else’s rules. You are writing them.

What you will own:

• The frontend architecture. The Nextjs application, the Frontastic component registry, and the Builder io and Strapi integrations. Component patterns, data fetching, state and dynamic import strategy are yours to define.
• Type safety. You will lead our TypeScript strict mode migration on an existing codebase and hold the line on it through review, without stalling feature delivery.
• Performance and technical debt. Bundle size, Core Web Vitals, dependency consolidation, and a performance budget in CI so the improvements stick.
• The standards. You write what our AI code review agents enforce on every pull request, including the ones our external development partner raises.

• 5+ years frontend engineering, with 2+ years in Next.js. Pages Router experience is essential.
• Strong TypeScript in production, comfortable in strict mode. Having led a strict mode migration on an existing codebase is what we are really looking for.
• Strong React: composition patterns, hooks, context, and performance work you measured rather than assumed.
• Code you have written yourself in a TypeScript BFF or API layer. This is a requirement, not a bonus.
• Utility-first CSS at scale, Tailwind preferred.
• A component library you standardised, so that new work followed the pattern by default rather than by review.
• Standards you set and got into CI: ESLint, Prettier, TypeScript configuration, styling conventions.
• Demonstrated experience raising a team’s standard through code review, including people you did not manage.
• Strong opinions on component design and architecture, and the ability to defend them without being difficult about it.
• Written English strong enough to author the standards document everyone else works to.
• Comfortable reviewing AI-generated code, and confident enough to overrule it.
• Able to work onsite in Ortigas, Pasig City, Metro Manila
  

One question with your application.

Tell us about a time you enforced quality on a messy codebase, for example enabling TypeScript strict mode or introducing standards to a team that had none. How did you do it without grinding delivery to a halt, and how did you bring other developers along with you? We are more interested in this than in your years of experience.