Senior Backend Engineer

About the role

Much of our backend work is on systems where being wrong costs money or trust: payments that must reconcile, messaging at volume, and records where the audit log matters as much as the feature. The interesting problems appear under load, on the worst day, when a third party is misbehaving.

What you will do

• Design and build services that stay correct under retries, network partitions and duplicate delivery.
• Own a system in production, including the alerting, the runbook and a clear definition of what is worth waking someone up for.
• Work on legacy modernisation: characterise what exists, cover it with tests, then replace it in slices.
• Take part in red-team week, trying to break something a colleague built.
• Mentor, review and be reviewed.

What we need from you

• Several years of production backend work in a typed or disciplined language, and comfort in SQL.
• You can explain idempotency to a client without using the word until the second sentence.
• Experience with a system that had real consequences when it failed.
• You write tests first on the parts that matter, and can say why those parts.

Useful but not required

• Payments, telecoms or clinical systems experience.
• You have run a migration that could not have downtime.
• Familiarity with event-driven architectures and their failure modes.