Quo - Staff Backend Engineer, Foundations

• Node and TypeScript on the backend • Event-driven microservices with Temporal and RabbitMQ at the centre • Kubernetes on AWS • Datadog for observability • Web (React), iOS and Android clients on the other side of the API • Language is not a filter. If you've built the right things in Go, Python, Java or anything else, we'd rather talk to you than to someone who knows Node but hasn't. • You write TypeScript every day and know it deeply. You're comfortable with its type system and the patterns that keep a large codebase healthy. • You've built and run GraphQL APIs in production, and ideally you've helped move a codebase from REST to GraphQL or led a similar API modernisation. • You're a strong backend engineer with a solid grasp of systems design, reliability and infrastructure, and you've built systems that scale. • You enjoy building things other engineers depend on, like shared libraries, patterns and platform capabilities, and you care about making them easy to use. • You can influence technical direction across teams, explain trade-offs clearly and get people on board without needing authority over them. • You like ownership and some ambiguity. You've worked somewhere with real users and real structure, whether that's a larger tech company or a scaling startup, and you want to make a visible difference here. • You're happiest writing code. This is a hands-on role, not a DevOps, SRE or developer productivity programme role. • Have worked on authentication and authorization, search or graph architecture. • Have production and/or operational experience with GraphQL federation. • Have worked across web, mobile and backend, even though this role is backend first.