Backend Engineer

Our API serves 90 million requests a day and the p99 is not where we want it.

What you will do

• Own two services in our Go estate, including their on-call.
• Take the p99 on our busiest endpoint from 840ms to under 200ms. We know roughly where the time goes.
• Improve the migration path off the Postgres instance that has become a single point of failure.
• Review generously. Code review is a teaching surface here.

What we are looking for

• Three or more years building backend services that carry real traffic.
• Go, or a strong case for why your language experience transfers.
• Real operational instincts: you have been paged, and you fixed the cause.

The setup

Two days a week in the Edinburgh office. On-call is one week in six, compensated, and we run a blameless postmortem for every incident.