We're hiring for a company at a genuinely interesting inflection point.
A well-funded, operationally mature business running a multi-country platform across six European markets is building its engineering function in-house for the first time.
The platform sits at the centre of a high-volume, multi-sided marketplace: leasing companies, dealers, employers and employees all interact through it. It works. But it's grown fast, it's tangled, and the roadmap is to consolidate several regional legacy systems into one clean, modular architecture without breaking a live operation in the process.
What you'll actually be doing
You'll work closely with the lead architect as a genuine thought partner, not as a ticket-executor. Early focus will be on the Java monolith: understanding how it's built, separating tightly coupled integrations (HubSpot, third-party leasing systems, AI-assisted customer services) into clean modules, and laying the groundwork for other regional platforms to eventually migrate across.
You'll be expected to dig into the codebase, hold your own on solution design, and communicate clearly with product and business stakeholders when needed. The architecture lead will handle the wider business context.
The stack
Java · Spring Boot · PostgreSQL · REST APIs · Docker · AWS
AI-assisted development is part of the day-to-day here. You should be comfortable using it pragmatically, not reliant on it.
Who this is for
You've worked on codebases that actually have history. You're not scared of legacy and if anything, you find the puzzle interesting. You've probably dealt with multi-country or multi-entity complexity before and you understand why "it works in one market" isn't the same as "it works everywhere."
German language skills are a genuine plus. Existing documentation and parts of the codebase are in German.
You want to own your work, not just deliver it. The team is small, the mandate is real, and the person you'll be working with is the kind of engineer who'll give you a problem and trust you to come back with a solution.
The shape of the role
Fully remote. Central European timezone preferred. Strong preference for candidates based in Germany, Austria, Switzerland or the Nordics given the nature of the codebase and the team structure.