39 - Frontend Engineer (AI-Assisted Development)

About the role

You'll sit in a product team with backend, QA, design and product, and take features from a rough product idea to a screen a planner can use without a manual. Your time is a balance between building features, fixing bugs and resolving technical debt. You ask what a planner is trying to do before you read what the ticket says, and you automate the parts of your own process that don't need a human.

How AI fits the work

Claude Code is how their engineers write software. Everyone uses it daily, and whole features now go out with an agent doing most of the coding. You still own what you merge: you read the diff, you know why it works, and you can defend it in review. The interesting part of the job is deciding what to hand to an agent, what to write yourself, and what context the agent needs to get it right the first time.

Your first year

• First, ship. Deliver features in scheduling and time tracking. Start small, then take one full feature from the product conversation through to release.

• Then, own an area. Pick up a product surface end to end and become the person the team asks about it, including what it should do next. That includes how AI fits your area: which patterns you document for the agent and which calls you keep for yourself.

• Along the way, make it safe to change. Restructure and test the paths you build on while you build on them, and extend test coverage where it's lacking. The team moves fast and keeps quality up by automating what a human doesn't need to do, including the checks that catch what an agent got wrong.

What you'll be doing

• Designing and building frontend features, starting from rough product ideas

• Delivering features with Claude Code, from the prompt through to the pull request, and reviewing the output as closely as you would a colleague's

• Writing the patterns, conventions and project context the agents work from, so generated frontend code lands in the right shape

• Turning tangled domain rules into screens people can use without a manual

• Fixing bugs in your own features and in code you've never seen before

• Improving the code you touch while you touch it, so the next feature in that area costs less

• Writing and maintaining automated tests in Jest and Playwright

• Shipping in short cycles with your product team

• Pairing, reviewing and teaching what you know

Tech stack and ways of working

Angular on the frontend, PHP on the backend, and a web app plus a React Native mobile app. Tests in Jest and Playwright. Development is AI-assisted with Claude Code as the primary tool, and a growing share of the code starts there; human review and engineers owning what they ship keep it safe. Teams are mixed-discipline, ship in short cycles and pair often, with each other and with an agent open. Every quarter you get time to build and ship one of your own ideas, and there are regular hackathons.

What you bring

• 5+ years of professional experience with an SPA framework, Angular preferred. Depth in React or Vue works if you can show you'll carry it over.

• A track record of shipping: you've delivered features to real users at a steady pace, and you know what you cut to get them out

• Production code shipped with an AI agent such as Claude Code, Cursor or Copilot, and a clear view of where you let it run and where you take the keyboard back

• Automated testing with Jest and Playwright (or equivalents), and an opinion about what deserves a test

• The ability to simplify: given a tangled domain problem, you produce a screen that hides the tangle

• You explain your choices clearly, in review, in design discussions, and to a product manager who doesn't read code

• You work as a peer: you pair, you review, and you make the people around you better without needing a title to be heard

Nice to have

• Claude Code specifically, or agent setups you've tuned for a team rather than just yourself

• TypeScript at depth

• Storybook or component library ownership

• React

• TDD

• PHP, or enough backend knowledge to reason about the API you're consuming

• Experience in a complex, regulated domain (this one covers scheduling, time tracking, leave and labour law across countries)