Who we're hiring
Senior engineers who'd rather inherit a hard problem than start a clean one.
Roles in Munich and Berlin, hybrid. English is the working language; the domain is stubbornly German. We hire senior — the interview is a conversation between people who've both shipped things, and comp comes up on the first call. Two tracks: software engineering below, and a senior security engineering role.
01
You want to meet the people you build for.
Engineers here go on site visits and sit with construction managers. If you'd rather receive requirements than go find out, this will be frustrating.
02
You're comfortable from the data model to the screen.
All the way to where a construction manager reads the answer. Frontend and backend work.
03
You're fine being domain-junior for a while.
However senior you are technically, construction takes months to understand — and the engineers who do best treat that as the interesting part.
Second track
Senior Security Engineer
The same system of record, from the defender's side. Putting agents on it changes the threat model: prompt injection becomes an authorisation problem, and every retrieval path is a data boundary. We want someone who owns that end to end — threat modelling, identity and permissions, and the harnesses that attack our own agents before anyone else does.
Security here is engineering work, not a review queue: you ship the guardrails, the tooling and the tests, and you sit with the teams whose code you're hardening.
Security engineering at Capmo →