Do you work with Dutch clients outside the Randstad?
Yes. Eindhoven, Groningen, Maastricht, anywhere. Same-day train coverage if you need an on-site session. Otherwise remote default.
Available for Dutch teams from Eindhoven to Groningen. Backend work in PHP and Python, AI features into production, legacy rescues. Remote by default, on-site by arrangement, EU timezone year-round.
Remote across the Netherlands. Same-day train to anywhere in the country if your project needs an on-site session. Standard Dutch freelance setup, EU-compliant invoicing.
The Dutch tech market is small and dense — once you've shipped at one Utrecht or Amsterdam company you'll often run into the same people at the next one. I take that seriously. Work is small-talk in person, then code by Slack, and I try not to embarrass anyone who recommended me.
Remote isn't a discount on senior engineering. It's a default that makes blocks of deep work possible. I document, ship pull requests with context, and write standup notes the team can actually read async.
EU timezone, English-language work, Dutch-friendly invoicing. Fine with on-site days when the project needs them. Equally fine with three months of pure remote when it doesn't.
Yes. Eindhoven, Groningen, Maastricht, anywhere. Same-day train coverage if you need an on-site session. Otherwise remote default.
Hourly or fixed-scope, monthly invoicing, standard Dutch freelance terms. I can adapt to your preferred template — if you have a procurement process, send me the contract and I'll work through it.
Sometimes. I do exactly that at Zoovo. If you have a small team, an early product, and want a senior technical voice without paying for a full-time CTO, we should talk. If you have 20 engineers and need a leadership hire, hire that person.
No. Standard practice. The projects I take on are GDPR-compliant by default and I'll happily work under your team's data-handling rules.