The opportunity
Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.
What you'll do
Represent APAC for the global team. Be the leadership presence on during APAC: hours. You’ll lead as one of the larger team: shared standards, shared bar, shared playbooks.
Genchi genbutsu: go and see. This isn't a role where you stop reading tickets. You'll regularly sit with tickets yourself, partly to stay sharp, partly because you can't manage what you don't see.
Keep the team singular across timezones. Partner with your EMEA and AMER: counterparts on coverage, escalations, and handoffs. The goal is that a customer can't tell which region picked up their ticket, because the team feels like one team.
Turn signal into product. Work directly with Engineering and Product as a: peer to surface patterns, file the right bugs, advocate for the right fixes, and make sure the loop from "user hit something weird" to "we shipped something better" is short. This is a collaboration, not a handoff.
Raise the technical bar on the team. Support and provide support engineers a: path to improve on Postgres, on our platform, and on how to actually debug a system rather than guess at it. Help build the playbooks, the runbooks, and the habits that scale.
Care about the whole experience. A user's problem is rarely just the thing: they typed in the ticket. It's the network, the schema, the expectation, the docs they couldn't find. We want managers who treat support as a dialogue with the whole system, not a lookup against a single symptom.
What they're looking for
- A technical foundation, kept current. A real background in Postgres / SQL,: Linux, sysadmin, backend or platform engineering, DevOps, or database work. You may be a few years out of deep hands-on work, and that’s okay as long as you've done something deliberate to keep your edge (side project, homelab, pairing on cases, OSS) so you can still read a stack trace and a query plan without bluffing.
- Supabase-adjacent fluency. Comfortable reasoning about auth flows, storage,: serverless functions, realtime systems, or vector workloads. If you haven't used Supabase, that's fine. You should be the kind of person who'll have it running locally in a weekend.
- Management experience. You've led a technical team before: support, SRE, platform, engineering, doesn't matter which. You know how to give feedback that lands, how to run a 1:1 that isn't a status update, and how to hire well.
- Operational instincts. You're comfortable with metrics (FRT, MTR, CSAT) but: you don't let them run the team. You know when a number is telling you the truth and when it's hiding the real story.
- Writing. You can write clearly in English under pressure: to a customer, to an engineer, to a CEO. Most of what support produces is prose; we take it seriously.
- Customer instinct. You like users. You're curious about what they're trying: to do, not just what they're stuck on. You believe good support works itself toward making itself smaller, by making users more capable.
