SDE 2 - Backend Platforms

About the role

Identity, payments, and notifications as real platforms — designed once, run centrally, adopted by every product in the group. You’d own one of them end to end. The direction is set. The design is wide open — how tenancy works, where the boundaries sit, what each product adopts and when. You’d be shaping those, not inheriting them.

What you'll do

• The multi-tenancy and isolation decisions every consumer inherits
• Public API contracts, and evolving them without breaking the teams that depend on them
• How the service gets consumed — by other services, by developers integrating it, and increasingly by agents
• The self-serve surface for your service — consoles and tooling, built with the frontend and design folks on the team — so a product team can adopt it without you in the…
• SLOs, on-call, and incident response for what you build

What you need

• Python
• Data modelling
• Django
• Kubernetes
• Incident response
• Any graduate

Good to have

• Data privacy