The opportunityYou'll own the design system at Ambrook, from the components down to the frontend infrastructure underneath them. You're an engineer first: you write clean, fast TypeScript and React, you care about the architecture behind a component as much as how it looks, and you treat coding agents as part of how you work. The role sits where the design system meets the product that ranchers and farmers use every day. You'll keep both healthy as we grow. We care about your engineering judgment, your bar for craft, and your willingness to try things.
Frontend and design systems have changed dramatically over the last year, and we've changed with them. We've retooled ourselves around AI to clear out the busy work, including migrations, adoption, and the long tail of upkeep that used to eat a team's time, so engineers can spend their time on the work that actually moves the product. We're looking for someone to build alongside our tight, talented design and engineering teams, staying flexible as the macro shifts while raising the technical floor of everything we ship.
What you'll own- The design system: Build and evolve our component library, interaction patterns, and design tokens as production frontend infrastructure that holds up across web and mobile
- Migrations and adoption: Drive the system into the product. Land breaking changes, deprecate old patterns, and do the human work of getting the whole team to actually build on it
- Frontend performance: Treat bundle size, render performance, and accessibility as features, and own the tooling and guardrails that keep them from regressing
- Agentic development with craft: Write the codemods, migration scripts, and agent workflows that let the whole team move onto the system faster, without sacrificing the quality of what ships
What we look for- You bring deep frontend engineering chops: clean, performant TypeScript and React, with a solid grasp of data structures, async programming, and modern build and tooling workflows
- You've owned a design system or shared component library in production, and you know the hard parts: versioning, breaking changes, migrations at scale, and convincing other engineers to build on your work
- You treat frontend performance and accessibility as engineering problems. You can profile a slow render, cut a bundle down, and put guardrails in place to keep the wins
- You use coding agents as part of how you work, pointing them at migrations and adoption to move faster across a large codebase
- You have strong enough design instincts to spot when something feels off in a UI and hold a high bar, even if you spend more time in the codebase than in Figma
- You're curious about and empathetic to the domain we operate in
- Your past work, whether shipped systems, tooling, open source, or a portfolio, tells a clear story of your engineering skills and your craft
