<div class="show-more-less-html__markup show-more-less-html__markup--clamp-after-5 relative overflow-hidden"> <p>Staff Frontend Software Engineer (TypeScript)</p><p><br/></p><p>About the Role</p><p>This is not a conventional engineering role. Our client is an AI-first company rewriting the rules of their segment — building products that put them in direct competition with the likes of Anthropic, Alphabet, and OpenAI. They are not catching up; they are setting the pace.</p><p>The engineering culture here is genuinely different. Over 90% of code is written by agentic AI systems. The Staff Frontend Engineer they need isn't someone who needs to warm up to that reality — they need someone who hits the ground running inside it, shaping how those systems work, where they fall short, and what comes next.</p><p>This is a role for someone who thinks in systems, takes real ownership, and is energised by working at the frontier of what AI-native engineering looks like in practice — and who happens to live closest to the surface where users actually meet the product.</p><p><br/></p><p>What You'll Do</p><p><br/></p><ul><li>Own frontend technical strategy within your domain — setting the direction for architecture, component design, and the patterns that hold up as the product and team scale</li><li>Work inside an AI-native engineering environment where agentic systems write the majority of code; your role is to direct, review, extend, and improve the interfaces they produce</li><li>Design and build complex, high-performance user-facing systems where responsiveness, reliability, and polish are non-negotiable — including the demanding, real-time, AI-driven interfaces this product depends on</li><li>Set the bar for frontend quality: state management, rendering performance, accessibility, and a coherent design-system foundation others build on</li><li>Bridge engineering and product — bringing a product-minded perspective to technical decisions and translating complexity into outcomes that matter to the business and to users</li><li>Coordinate across engineering, product, design, and leadership stakeholders; this is not a heads-down IC role — influence and communication are core to how you'll operate</li><li>Take full operational ownership: no separate IT or ops function, your team monitors, responds, and fixes — including out-of-hours on-call rotation</li><li>Run and rotate the scrum champion role within an agile team operating on two-week sprints</li></ul><p><br/></p><p>What We're Looking For</p><p>Must-haves</p><p><br/></p><ul><li>Deep, hands-on mastery of TypeScript and the modern frontend ecosystem — you know what breaks in large, long-lived codebases and why, and you build to prevent it</li><li>Strong command of frontend architecture at scale: component design, state management, performance and rendering, and the trade-offs between them</li><li>Comfortable with Python at a working level — enough to move confidently across the stack and collaborate closely with backend systems</li><li>Mastery of design patterns, architectural principles, and systems thinking — this is a role that requires both breadth and depth</li><li>Proven stakeholder management across engineering, product, and design; you see technical problems as product problems and communicate accordingly</li><li>A genuine ownership mindset in a fast-paced environment — you move quickly, take responsibility, and don't wait for permission</li><li>Operational readiness: comfortable being first responder, diagnosing root causes, mitigating and fixing issues, including out-of-hours when it counts</li><li>Experience working in agile environments; confident rotating the scrum champion role and keeping a team accountable to process without being rigid about it</li></ul><p><br/></p><p>Nice-to-haves</p><p><br/></p><ul><li>Hands-on experience building interfaces for LLM, ML, or AI products — you understand how these systems behave, not just what they claim to do, and you know how to design UX around their quirks</li><li>Experience owning or establishing a design system or shared component library at scale</li><li>Prior exposure to AI-native engineering environments where automation and agentic systems are central to how the team works</li><li>A track record in high-growth or frontier technology companies where the technical bar is set by the best in the world</li></ul><p><br/></p><p>Your Mindset</p><p><br/></p><ul><li>AI-native, not AI-curious. You don't need convincing that agentic systems are the future — you're already operating in that reality and know how to get the best out of them.</li><li>Ownership without prompting. You don't wait for someone to define the problem. You find it, frame it, and move on it.</li><li>Product-minded engineer. You understand that the interface you build exists to solve a user or business problem, not to be elegant for its own sake.</li><li>Calm under operational pressure. When things break at 2am, you're the person your team wants on the other end of the call.</li><li>Collaborative, not siloed. You operate across boundaries — engineering, product, design, leadership — and bring people with you, not just information at them.</li></ul><p><br/></p><p>Who You Might Have Been</p><p><br/></p><ul><li>A Senior or Staff Frontend Engineer at a developer tooling, AI product, or data platform company — someone who has lived the hard frontend problems at scale, not just read about them</li><li>An engineer who moved from pure IC work into technical strategy and stakeholder influence, without losing the ability to go deep into the code</li><li>An early engineer or frontend tech lead at a fast-growth scale-up, where ownership was a necessity and process was something you built, not inherited</li><li>Someone who has worked in or alongside AI/ML teams and understands how models, pipelines, and the interfaces on top of them fit together</li></ul> </div>