In short
Senior backend engineer to own services, APIs, and data for a small Dutch product company, working fully remote on a 32-hour, 4-day week. Stack is Kotlin on the JVM with Postgres, AWS, and some Node/TypeScript; strong Java without Kotlin is acceptable, but fluent Dutch is mandatory.
About the role
Senior Backend Engineer · Kotlin/JVM · Remote NL · 4-day week
I'm working with a small Dutch product company. No VC. No hype. Just a product a lot of people use every day, and one that actually does some good.
Small team, 1.4 million ARR.
Their tech lead just moved on after a long stint, part of the furniture, so it's left a big whole; they miss him. They're not looking for a clone. They want a senior engineer to sit next to the team lead, own the backend, and help shape where it goes next.
The job;
- Own the backend: services, APIs, data, and keeping it all up
- Make the big technical calls, and write them down
- Be the team lead's technical sparring partner
- Help a couple of junior devs get better
- Grow into the architecture if you want it. No pressure, but the space is there.
Things will move here. Priorities shift, and stuff gets rebuilt when it needs to. If that sounds fun rather than stressful, read on.
Stack;
Kotlin on the JVM, Postgres, AWS. Some Node/TypeScript around the edges.
Strong in Java but no Kotlin yet? Still talk to me. JVM depth matters more than the language on your CV.
You;
- Senior backend engineer, with a good chunk of that on the JVM
- You've owned production. Kept it up, broken it, fixed it.
- Happy working remotely and on your own. You speak up early when something's off.
- Small team, opinions count, things change, and you like that
- Fluent Dutch. Non-negotiable, sorry.
The deal;
- 4-day week, 32 hours, and you plan your own week. Ideal if you're a working parent, or you just want proper flex in your life.
- Fully remote, proper kit, and budget to keep learning
- A team that actually gets together and enjoys it
- Three steps: an intro, a technical chat with the team lead about real problems (no puzzles), then terms and meeting the team
Curious? I'll tell you who it is when we talk.
Requirements
- Senior backend engineer with substantial JVM experience