Our platform runs on .NET microservices behind a Next.js frontend, and we'd like you to own the path between them. Not a slice of it — the whole thing, from the data model up to the button someone clicks, and still yours once it's live.
You'll work closely with our software architects, product owners, and fellow developers: code reviews, pair programming, and the technical decisions that stick around.
- You own features from the database row to the interface that triggers it. No handover, no waiting for another team to pick up your half.
- You decide how data moves through the system: schemas in Postgres, caching in Redis where it pays off, messaging over RabbitMQ where services need to stay independent.
- You build the Next.js frontend on top of the services you wrote — which means you feel every backend decision in the UI, and you design accordingly.
- You take features to production and keep the CI/CD pipeline fast enough that nobody avoids it.
- You catch bottlenecks, security risks, and failure modes before users do, on both sides of the stack.
- You use coding agents as part of your daily workflow — directing their work, reviewing their output, and fixing what doesn't hold up. Writing code matters; knowing what good code looks like matters more.
- You've spent several years on both sides of the stack — C# and .NET on the backend, React and TypeScript on the frontend.
- You've built microservice architectures and run Postgres, Redis, and RabbitMQ in production.
- You're at home in a Next.js codebase with Tailwind, and in the Node.js layer (Express.js, Nest.js) that connects the UI to our services.
- You know your way around architecture principles, performance optimization, and secure scalability.
- You work well in agile teams (Scrum/Kanban), you write clearly, and you're comfortable in English and German.
- You have a degree in Computer Science, Software Engineering, or a related field — or the experience that makes one unnecessary.
- You've worked with AWS, Azure, or Google Cloud Platform. We're not in the cloud yet, so this is a plus, not a requirement.
We care as much about how you approach a problem as about which frameworks you know. You look past the edges of your own ticket: you notice when a fix really belongs in a different service, you question a process once it has stopped making sense, and you judge your work by whether the whole system got better — not by whether your part shipped. "Not my code" isn't a sentence we use much around here.
You're joining at a point where the engineering foundations themselves are being rebuilt around AI-native workflows — not retrofitted onto legacy decisions, but designed now, while the architecture is still being shaped. That means you don't inherit someone else's five-year-old choices: you help make the calls on how services are split, where AI agents fit into the workflow, and what "good" looks like technically around here. Few Senior roles hand you this much real influence over the foundation rather than the features on top of it.
On the practical side: 30 days of vacation, up to 50 workation days a year, a sabbatical option, Hansefit, pension contributions and an employee loan program, plus a range of travel-industry discounts on your own trips. Fully remote with no relocation required, a hiring process that's three steps end to end, and no bureaucratic layers slowing down a "yes." We're rated 4.7/5 on Trustpilot — what you build ships to real people, not into the void.
We're fully remote, so you work from wherever you do your best thinking. Agentic coding is part of our day-to-day, not a side experiment: we work with Claude Code across the team, and we'd want you to have an opinion about where it helps, where it doesn't, and how to review what it produces. If that's already your workflow, you'll feel at home. If it isn't yet, you'll pick it up here.
Three steps, no surprises:
- Online interview with HR
- Online interview with our Head of Engineering
- On-site interview with the team
Codeword: Travel