Backend Engineer

The role

You will lead the design and delivery of backend systems for a consumer sports app used by real customers with real money on the line. You will own significant parts of the backend end to end.

This is a senior role. We expect you to take ambiguous problems and turn them into well-designed, well-tested systems with little direction, to make sound technical decisions and explain the tradeoffs behind them, and to raise the bar for the engineers around you.

What you will do

• Lead the technical design of new backend systems and major features.
• Own critical parts of the backend, including the paths where money moves, and be accountable for their correctness, performance and reliability.
• Design and evolve the APIs our mobile and web clients depend on, keeping them consistent and backward compatible as the product changes.
• Make data-modelling decisions, and write schema changes and queries that stay correct and fast under production load.
• Build background and scheduled processing that is reliable, retries safely and never does the same work twice.
• Build and scale realtime features that push live updates to clients.
• Integrate with third-party services and data providers, and design for their failures.
• Lead the response to production incidents, find the root cause, and make sure the same failure cannot happen again.
• Set the standard for testing and code quality. Review code and designs thoroughly.
• Work directly with product, mobile and web to shape what we build, not only how.

Who we are looking for

6 or more years of professional backend engineering, with deep production experience in all of the following:

• TypeScript and Node.js
• NestJS
• gRPC and Protocol Buffers
• Go
• PostgreSQL and TypeORM
• MongoDB
• Redis and BullMQ
• WebSockets with Socket.IO
• Docker and Kubernetes
• Google Cloud
• Jest, and a track record of building well-tested systems

You have designed and run distributed backend systems in production and have owned them through growth, incidents and change. You reason confidently about transactions, concurrency, idempotency and failure modes, and you can diagnose a slow query, a stuck queue or a failing rollout under pressure. You have worked on systems where correctness is not optional, such as payments, ledgers or other financial flows. You write clearly, make decisions you can defend, and make the engineers around you better.