€60,000 - €80,000 + Equity (tbc)
A Backend role that asks you to decide what gets built in the first place.
You'd be joining an engineering team building at the intersection of AI and financial technology — new products, not a legacy platform someone else already designed. The systems need to be reliable and secure, but they're still being shaped, which means the architecture decisions on the table are real ones: how services talk to each other, how data moves through the platform, what happens when something breaks at scale. You'd be involved in those conversations.
Day to day you'll design and build backend services and APIs, work with distributed and event-driven systems, and get properly involved in data modelling rather than just querying someone else's schema.
You'll work closely with Product, Frontend, Mobile and AI engineers, so your decisions get tested against real product needs quickly.
There's no fixed stack — Python, Java, Go, Node/TypeScript, Kotlin are all valid starting points - what matters more is whether you've actually shipped and owned something.
You'll need:
- Strong professional backend engineering experience with real production ownership
- Solid grasp of APIs, backend architecture and database design
- Exposure to distributed systems, microservices or event-driven architecture
- Comfort making technical decisions and defending them
- Experience working somewhere where requirements shift fast.
If your current role has you maintaining a slice of something bigger with limited say, this will feel different. If you've been a founding or early engineer somewhere, or had genuine ownership at a start-up or scale-up, you'll recognise the shape of this straight away.
Fully remote, but you'll need to be based in and have the right to work in Germany.
If that sounds like your kind of problem, get in touch and we can talk through where it might go.
