Jobs · Full-time

Support Manager at Supabase - Remote APAC Role — Columbus

LocationColumbus
CompanySupabase
Sourcejobicy
Posted2026-08-15 04:25:03

Traveler-Friendly Insight

Location Flexibility: This role is fully remote with no physical Supabase offices — you can work from anywhere in an APAC timezone (roughly UTC+5 to UTC+12). That covers a huge swath of nomad-friendly destinations: Bali, Chiang Mai, Ho Chi Minh City, Medellín (if you're on an extended APAC-aligned schedule), and dozens of others.

Schedule & Async Culture: Supabase explicitly operates asynchronously. Monday–Friday core hours in APAC timezones are required, but the async-first culture means you have meaningful flexibility within that window. There is a weekend on-call rotation for support leads, so full digital-nomad spontaneity has minor guardrails.

Nomad-Ready Perks:

  • WeWork/Co-working allowance — usable worldwide, ideal for nomads who prefer structured workspaces in new cities.
  • Tech allowance — covers gear, so you're not lugging a full setup.
  • Annual company offsite — paid travel to a new city each year, a real perk for travel enthusiasts.

Cost of Living Snapshot: Without a published salary, comparisons are limited — but APAC-based tech manager roles at well-funded startups ($500M raised) typically range $80K–$140K USD. In Chiang Mai (~$1,200/mo comfortable living) or Bali (~$1,500/mo), that's exceptional purchasing power. Singapore or Tokyo would consume more, but co-working is world-class there.

About Supabase

Supabase is the Postgres development platform: Database, Auth, Storage, Edge Functions, Realtime, and Vector, deeply integrated and built for teams that need their backend to grow with them. We're open source, we move fast, and our users are developers who notice when things are off.

About This Role

We're hiring a Support Manager on our global Support leadership team to clear the way for our APAC Support Engineers.

A quick word on what Support means here, because it shapes everything about this role. We don't think of Support as a ticket queue with a manager attached to it. We think of it as one of the highest-leverage feedback loops in the company. It's the place where the real shape of our product meets the real shape of our users' work. Done well, it's an engineering superpower: it's how we learn where the product actually bends, who's bending it, and what we should build next.

You'd join the existing Support leadership group and be the person on during APAC hours, sharing context, queue, escalations, and standards with your peers in EMEA and AMER. One team, globally available.

The right person needs to be both sharp enough on the technology to be genuinely useful to their support engineers and able to anticipate their needs and keep the way clear. The support engineers are the ones doing the work that matters, and you're there to help them be the best they can be — whether that's helping with professional growth, taking on a difficult customer situation so they can focus on the technical problems, or simply being a good rubber duck.

If you've ever felt like a support org was being run as a cost center and wanted to drag it back toward being a craft, we think you'll fit right in.

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. 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 We'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.

Bonus Points

  • Familiarity with JavaScript / TypeScript and one of the major frontend frameworks (React, Vue, Svelte), plus some Node.

  • Experience supporting a developer-facing product, an open-source project, or a platform with a public GitHub presence (Issues, Discussions).

  • You've been on the other side of the table (written software, run infra, been the person paged at 3am) and that shapes how you partner with the engineers you'll work alongside.

Timezones & Logistics

  • Full-time, remote, based in an APAC timezone.

  • Monday to Friday. We have 24x7 weekend support engineering coverage, but only a support leads on-call rotation of which you will be a member.

  • You'll partner closely with the global Support leadership team and report into the Head of Support.

What We Offer

  • Fully Remote

    We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.

  • ESOP

    Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we're building together.

  • Tech Allowance

    Use this budget to set up your ideal work environment — laptop, monitor, headphones, or whatever helps you do your best work.

  • Health Benefits

    Supabase covers 100% of health insurance for employees and 80% for dependents, wherever you are. Your wellbeing and your family's health are important to us.

  • Annual Off-Sites

    Once a year, the entire company gathers in a new city for a week of connection, collaboration, and fun. It's a highlight of our year.

  • Flexible Work

    We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.

  • Professional Development

    Every team member receives an annual education allowance to spend on learning — courses, books, conferences, or anything that supports your growth.

About the Team

Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.

  • 280+ team members

  • 55+ countries

  • 20+ languages spoken

  • $500M raised

  • 500,000+ community members

We move fast, build in public, and use what we ship. If it's in your project, we probably use it in ours too. We believe deeply in the open-source ecosystem and strive to support — not replace — existing tools and communities.

Hiring Process

We keep things simple, async-friendly, and respectful of your time:

  1. Apply – Our team will review your application.

  2. Intro Call – A short video chat to get to know each other.

  3. Interviews – Up to four calls with:

    • Team Leads

    • Future teammates

    • Someone cross-functional from product, growth, or engineering (depending on the role)

    • Someone from our leadership/founding team

  4. Decision – We may follow up with a final question or go straight to offer.

All communication is remote and we aim to move fast.

Frequently Asked Questions

Is this role truly location-independent or does it require a specific country?
The role is fully remote with no Supabase offices. The only requirement is that you are based in an APAC timezone (roughly UTC+5 to UTC+12), so you can work from any country within that range.
What are the working hours and is there weekend work involved?
Core hours are Monday to Friday aligned to APAC timezones. However, you will be part of a support leads on-call rotation that covers weekend escalations — the full engineering team handles 24x7 weekend coverage, but leads rotate on-call duty.
Does Supabase provide a salary range for this position?
No salary range is published in this job posting. Supabase has raised $500M and offers ESOP equity to all team members alongside health insurance, a tech allowance, and a co-working budget.
Do I need direct Supabase experience to apply?
No — Supabase states that if you haven't used Supabase before, that's fine, as long as you're the type of person who would set it up and explore it independently over a weekend. Relevant Postgres, backend, or platform engineering experience is what matters.
How technical does this Support Manager role need to be?
The role requires a genuine technical foundation — Postgres/SQL, Linux, backend or DevOps experience — and the expectation that you regularly read tickets and stay current. You don't need to be actively coding, but you must be able to read query plans and stack traces credibly.
Job4Travelers
Curated By

Job4Travelers

Helping travelers find remote work and build location-independent careers around the world.

Similar Opportunities