Frontend Engineer

<h2><strong><span style="color:#121317">About Shiftbase</span></strong></h2><p><span style="color:#121317">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.</span></p><p><span style="color:#121317">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.</span></p><h2><strong><span style="color:#121317">About the role</span></strong></h2><p><span style="color:#121317">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.</span></p><p><span style="color:#121317">Your time is a balance between working on features, bugs and resolving technical debt.</span></p><p><span style="color:#121317">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.</span></p><p><span style="color:#121317">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.</span></p><h2><strong><span style="color:#121317">Year one, in order</span></strong></h2><p><strong><span style="color:#121317">First, ship.</span></strong><span style="color:#121317"> Deliver features in scheduling and time tracking. Start small, then take one full feature from the product conversation through to release.</span></p><p><strong><span style="color:#121317">Then, own an area.</span></strong><span style="color:#121317"> 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.</span></p><p><strong><span style="color:#121317">Along the way, make what you build safe to change.</span></strong><span style="color:#121317"> 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.</span></p><h2><strong><span style="color:#121317">What you'll do</span></strong></h2><ul><li><p><span style="color:#121317">Design and build frontend features starting from rough product ideas</span></p></li><li><p><span style="color:#121317">Deliver features with Claude Code, from the prompt through to the pull request, and review the output as closely as a colleague's</span></p></li><li><p><span style="color:#121317">Write the patterns, conventions and project context our agents work from, so generated frontend code lands in the right shape&l