Frontend Engineer

About Shiftbase

We build workforce software that helps people get work done. More than 10,000 companies use our platform every month to plan shifts and track time, with less admin in the way.

We work from our Zoetermeer office with over 80 people and we grow every year. The culture is open and informal. You can push back on an idea regardless of title, and we change how we work when someone makes the case in retro.

About the role

You build frontend features that customers use the day you release them. You sit in a product team with backend, QA, design and product, and you take a feature from a rough product idea to a screen a planner can use without a manual.

Your time is a balance between working on features, bugs and resolving technical debt.

Claude Code is how our engineers write software. Everyone here uses it daily, and whole features now go out with an agent doing most of the coding. You still own what you merge, so 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.

You ask what a planner is trying to do before you read what the ticket says. You automate the parts of your own process that don't need a human.

Year one, in order

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 covers how AI fits your area, which patterns you document for the agent and which calls you keep for yourself.

Along the way, make what you build safe to change. Restructure and test the paths you build on while you build on them. Extend test coverage where it's lacking. We move fast and keep 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 do

• Design and build frontend features starting from rough product ideas

• Deliver features with Claude Code, from the prompt through to the pull request, and review the output as closely as a colleague's

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

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

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

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

• Write and maintain automated tests in Jest and Playwright

• Ship in short cycles with your product team

• Pair, review, and teach what you know

How we work

Frontend in Angular, backend in PHP, a web app and a mobile app in React Native. Tests in Jest and Playwright. We develop AI-assisted with Claude Code as the primary tool, and a growing share of our code starts there. Human review and engineers owning what they ship keep it safe. We ship in short cycles in product teams with mixed specialisations. We 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 we run hackathons.

Must-haves

3+ 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.

You ship. You've delivered features to real users at a steady pace, and you can tell us what you cut to get them out.

You've shipped production code with an AI agent. Claude Code, Cursor, Copilot or similar. Tell us where you let it run, where you took the keyboard back, and what you changed about your own workflow after a month of it.

You automate your tests. Jest and Playwright, or equivalents, and you have an opinion about what deserves a test.

You simplify. Hand you a tangled domain problem and you produce a screen that hides the tangle.

You explain your choices. In review, in a design discussion, 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-haves

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

• TypeScript at depth

• Storybook or component library ownership

• React

• TDD

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

• Familiarity with a complex, regulated domain (ours covers scheduling, time tracking, leave, and labour law across countries)

This might be your dream job if…

✅ You want your work in front of customers within days

✅ You'd rather own a feature end to end than take a finished spec

✅ You want a say in how a team writes frontend code with agents while the answer is still open

✅ You improve the code you touch without being asked, and you stop before it turns into a six-week rewrite

✅ You like a domain that takes months to learn

This probably isn't your dream job if…

⛔️ You want the technical approach decided before the ticket reaches you

⛔️ You want a job where AI stays out of your editor

⛔️ You'd merge agent output you can't explain in review

⛔️ You'd stop shipping to finish a refactor

⛔️ You prefer pixel work and would rather leave tests and architecture to someone else

⛔️ You'd rather work alone than pair and review

What we offer

• A laptop on Mac, Windows, or Linux

• 32 or 40 hours workweek

• Hybrid, from home or the Zoetermeer office

• 25 vacation days based on a 40-hour contract

• Pension plan

• NS business card or travel expenses reimbursed.

• Training budget for personal development