01
You own prod
The team that writes a service runs it: deploys, SLOs, dashboards, the whole lifecycle. There is no ops group to hand it to, and no change board between you and a release.
Culture
How we work
Four rules, no rituals. Each one has a consequence you can feel in a normal working week.
02
Proven tech, global scale
We standardise on a small, well-understood stack and run it in every market we operate in. That is what makes moving between teams cheap and the toolchain forgettable. New technology gets in through a written case, a pilot team and an exit plan.
03
Small teams, real mandates
Teams are small enough to fit round one table, and each has a system it owns and a roadmap it shapes with its product partner. We would rather have a team decide imperfectly than escalate perfectly.
04
Ship to reality
Engineers spend time at branches and airports, on shift with the people using what we build. It is the fastest way to find out that your loading spinner is someone’s queue.
How we ship
What owning prod looks like
Ownership only works if the path to production is short. This is what that looks like day to day — and what is worth pushing on in an interview.
- deploys, SLOs, dashboards, on-call
- You own prod
- between your merge and a release
- No handoff
- per team, with the mandate to match
- One system
How we hire
Four conversations, no take-home
- 01
Intro call
A first call with our tech recruiters. What you want to own, what we need owned.
- 02
Technical interview
One of our engineers, and an agentic coding task. Prove your technical skills on real work, not trees.
- 03
Bar raiser
We are looking for A players. System design and deep architecture with one of our best engineers.
- 04
Hiring manager and cultural fit
Meet your future manager. We are not just looking for technical expertise — we look for people with the right mindset.