Backend Engineer, Connect; API Platform

Small businesses represent 99.9% of all companies, yet they're still forced to choose between clunky, outdated enterprise phone systems or their personal phones. This multi-billion dollar market has been overlooked for decades, left to cobble together solutions that slow them down instead of helping them grow.

Quo is changing that. We bring calls, texts, and customer information together into one easy-to-use, AI-powered platform. We’re not just building a phone system. We’re setting a new standard for how businesses connect with their customers.

Driven by our values, we move fast, build with determination, and obsess over delivering value to the businesses that have been underserved for far too long.

Today, Quo is trusted by more than 120,000 companies and rated #1 in customer satisfaction on G2. We’re backed by Y Combinator, Tiger Global, Craft Ventures, Slow Ventures, and other top-tier investors. It’s safe to say we’re onto something big.

Quo is the phone system for modern businesses, and the Connect team is the front door for everything that talks to Quo without a human clicking in the app: the public API, MCP, OAuth, webhooks and integrations with tools like Hub Spot, Jobber and Clio.

It's the fastest growing part of the company. The platform handles close to a billion API requests a day, roughly a quarter of all Quo traffic, and a growing number of customers use the API without ever opening the app. In the last 60 days alone, over 16,000 MCP connections have been set up against it.

This is the first true staff role on the team. You'll be the technical voice for Connect: the person who sets the architecture, fields the questions from product, partnerships and leadership, and makes it easy for every other team at Quo to ship through the API.

• Build the system, and the relationships, that let any team at Quo add their feature to the public API in a day or two, then get the rest of engineering to actually use it
• Own the long-term architecture for the API platform. Python and Type Script SDKs are on the roadmap for Q4, and the longer-term model is Stripe's: product teams describe their surface, the API and SDKs are generated from it, and an ecosystem grows around it
• Be the technical point of contact for partnerships, product and leadership on what the API and integrations can do, set expectations, and protect the roadmap when a request would derail it
• Mentor the senior engineers on the team through design reviews, PR reviews and coaching. You'll write less code than a senior, on purpose
• Keep the platform fast, reliable and observable as traffic keeps climbing

Connect owns its own infrastructure end to end: its own cluster, databases, Redis and queues. The team ships without waiting on anyone. It's small, technically strong, and heading towards two sub-teams as the surface area grows.

• Node and Type Script on the backend
• Event-driven microservices with Temporal and RabbitMQ at the centre
• Kubernetes on AWS
• Postgres, MongoDB, Elasticsearch and Redis
• 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.

• 10+ years in engineering with real time at staff level. You've done this job before, at least once, and you want to be a technical leader rather than a manager
• You've built or owned a public API, developer platform, SDKs or webhooks for a product people pay for. Dev tooling backgrounds count
• You've driven a big cross-team change at a company with 80+ engineers, by getting the right people in each team on board rather than…