> Markdown version of [/jobs/ext/2667254-frontend-engineer](https://www.wearedevelopers.com/jobs/ext/2667254-frontend-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Frontend Engineer - **Company:** DifferentLab - **Location:** Zoetermeer, Netherlands - **Experience:** Experienced - **Salary:** €4,000.0 - €5,500.0 - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), PHP (Programming Language), Microsoft Windows, Application Programming Interfaces (APIs), Artificial Intelligence, Code Coverage, Cursor (Graphical User Interface Elements), Linux, Time Tracking Software, TypeScript, ReactJS, Technical Debt, Backend, Vue.js, AngularJS, Playwright, Production Code, Front End Software Development, Virtual Agents - **Published:** September 1, 2026 - **Apply:** https://www.nationalevacaturebank.nl/vacature/987de432-4cfe-45fc-86d1-fe5d4c1d652a/frontend-engineer ## About the Role 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 y own workflow after a month of it. You automate y 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. ## Description 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. Y time is a balance between working on features, bugs and resolving technical debt. Claude Code is how 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 yself, 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 y 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 y area, which patterns you document for the agent and which calls you keep for yself. 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, You explain y 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 yself + 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 (s covers scheduling, time tracking, leave, and lab law across countries) This might be y dream job if… You want y 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 y dream job if… You want the technical approach decided before the ticket reaches you You want a job where AI stays out of y editor 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 hs workweek + Hybrid, from home or the Zoetermeer office + 25 vacation days based on a 40-h contract + Pension plan + NS business card or travel expenses reimbursed. + Training budget for personal development ## Related Videos - [But, you're not Facebook](https://www.wearedevelopers.com/videos/378-but-you-re-not-facebook) - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Lessons learned from building a thriving Vue.js SaaS application](https://www.wearedevelopers.com/videos/1666-lessons-learned-from-building-a-thriving-vue-js-saas-application) - [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape) - [WeAreDevelopers LIVE – Frontend Inspirations, Web Standards and more](https://www.wearedevelopers.com/videos/1761-wearedevelopers-live-frontend-inspirations-web-standards-and-more) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 113 - Debugging above the cloud](https://www.wearedevelopers.com/magazine/422-dev-digest-113-debugging-above-the-cloud) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 133 - Back to Front](https://www.wearedevelopers.com/magazine/474-dev-digest-133-back-to-front) - [The Best 7 Frontend Frameworks for Developers in 2025](https://www.wearedevelopers.com/magazine/400-the-best-7-frontend-frameworks-for-developers-in-2025) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss)