远程工作雷达

支持工程经理(亚太区)

Support Engineering Manager (APAC)

其他亚太区可投
公司Supabase
薪资未公开
工作地点APAC
地域资格亚太区可投
时区要求无特别要求
用工类型Full-Time
发布时间今天
数据来源Jobicy
前往 Jobicy 查看并投递 →

关于 Supabase
Supabase 是 Postgres 开发平台:数据库、认证、存储、边缘函数、实时功能和向量,深度集成,专为需要后端随着他们一起成长的团队而设计。我们是开源的,我们行动迅速,我们的用户是那些会注意到问题的开发者。

关于这个职位
我们正在全球支持领导团队中招聘一名支持经理,以帮助亚太区支持工程师的工作。

在这里,支持意味着什么,因为这将塑造这个职位的方方面面。我们不认为支持只是一个带有经理的工单队列。我们认为它是公司中最具杠杆效应的反馈循环之一。这是我们的产品实际形态与用户工作实际形态交汇的地方。如果做得好,它是一种工程上的超级能力:它让我们了解产品实际上在哪些地方被弯曲,是谁在弯曲它,以及我们应该接下来构建什么。

你将加入现有的支持领导团队,并在亚太地区工作时间担任负责人,与欧洲、中东和非洲(EMEA)以及美洲(AMER)的同事分享上下文、工单、升级流程和标准。一个团队,全球可用。

合适的人选需要在技术方面足够敏锐,能够真正为他们的支持工程师提供帮助,并能预判他们的需求,保持道路畅通。支持工程师是执行重要工作的人员,而你的职责是帮助他们成为最好的自己,无论是帮助他们职业成长,处理困难的客户情况以便他们专注于技术问题,还是仅仅作为一个好的倾听者。

如果你曾经觉得支持部门被当作成本中心,想要把它重新带回作为一门技艺,那么我们认为你会很适合这里。

你会做什么
· 代表亚太区与全球团队沟通。在亚太地区工作时间担任领导角色。你将作为更大的团队之一进行领导:共享标准、共享门槛、共享操作手册。

  • 去现场查看:这不是一个停止阅读工单的角色。你将定期亲自处理工单,部分是为了保持敏锐度,部分是因为你无法管理你没有看到的东西。
  • 在时区之间保持团队统一。与你的 EMEA 和 AMER 对应人员合作,确保覆盖范围、升级流程和交接顺畅。目标是客户无法分辨是哪个地区接到了他们的工单,因为整个团队感觉像一个整体。
  • 将信号转化为产品。作为同行直接与工程和产品团队合作,发现模式,提交正确的错误报告,为用户发声。
查看英文原文

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. 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 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:
· Apply – Our team will review your application.

  • Intro Call – A short video chat to get to know each other.
  • 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
  • Decision – We may follow up with a final question or go straight to offer.

All communication is remote and we aim to move fast.

本页面信息整理自 Jobicy,版权归原发布方所有。职位可能随时关闭,投递请以原始页面为准。 本站只做信息聚合展示,不参与招聘流程,也不向求职者收取任何费用。

该公司其他在招职位

← 返回全部职位