技术客户经理（TAM）负责人

ABOUT SUPABASE

Supabase is the Postgres development platform, built by developers for developers. We provide a complete backend solution including Database, Auth, Storage, Edge Functions, Realtime, and Vector Search. All services are deeply integrated and designed for growth.

ABOUT THE ROLE

The Technical Account Manager (TAM) Leader owns the health, direction, and performance of the Technical Account Management function. Where an individual TAM is the primary technical partner for their own portfolio of accounts, the TAM Leader is accountable for the entire TAM book — every account covered by the team, every partner relationship with a technical dimension, and the people who deliver against them.

The TAM Leader is both a player and a coach: they carry direct accountability for coverage decisions, escalation outcomes, and cross-functional alignment, while spending the majority of their time developing the individual TAMs so the team's proactive, relationship-first approach scales without becoming a response channel.

CORE RESPONSIBILITIES

PEOPLE LEADERSHIP & TEAM DEVELOPMENT

The TAM Leader hires, coaches, and grows the TAM team so each member operates as a credible, proactive technical partner to their accounts. This includes:

- Hiring and onboarding new TAMs, including running them through the TAM Path ramp

- Running regular 1:1s, setting individual development plans, and giving direct feedback on account plans, QBRs, and escalation handling

- Building and maintaining repeatable playbooks (upgrade runbooks, optimization playbooks, escalation patterns) so quality doesn't depend on tenure

- Setting and holding the team to a consistent bar for technical depth, proactivity, and communication

PORTFOLIO & COVERAGE OWNERSHIP

The TAM Leader owns the coverage model for the entire function — deciding, tracking, and refreshing who is assigned where, and closing gaps as they surface. This includes the two account universes the role is accountable for:

- Named accounts — the full book maintained in the Draft TAM Accounts doc https://app.notion.com/p/3b35004b775f805ab27ed2cfede681c1?pvs=21, currently ~$33.1M ARR across 120 accounts split across the team, capped at 20 accounts per TAM

- Partner-mapped accounts — every partner with a named Technical Account Manager in the Partner Mappings https://app.notion.com/p/9715782ec0d645368d2bea677ae90759?pvs=21, spanning Strategic AI, Growth, and Other tiers

- Running the quarterly review/refresh of assigned accounts, rebalancing books as ARR and strategic relationships shift

- Resolving open coverage gaps (e.g. regions or account types with no TAM alignment) and deciding when a controlled exception, a new hire, or a change in tier definition is the right fix

- Approving leadership-discretion assignments and cap exceptions, and making the trim/reassign calls when an account is dropped for capacity

CUSTOMER TECHNICAL OWNERSHIP (OVERSIGHT)

The TAM Leader ensures every assigned account — named or partner-mapped — has a clear, accountable technical owner. They spot-check account documentation, architecture understanding, and risk tracking across the book, and step in directly on the most strategic or highest-risk accounts.

ONBOARDING AND ADOPTION (OVERSIGHT)

The TAM Leader ensures the team consistently shortens time to value for new accounts by:

- Auditing that architecture and deployment validation is happening post-sale, not skipped

- Coaching TAMs on configuration guidance and best-practice delivery

- Tracking early success milestones across the portfolio, not just account by account

PROACTIVE TECHNICAL GUIDANCE (OVERSIGHT)

The TAM Leader ensures environment reviews and risk/optimization surfacing happen on a regular cadence across the whole book, covering scalability, reliability, security, and lifecycle planning — and holds the team accountable when reviews lapse.

ISSUE MANAGEMENT AND ESCALATION

The TAM Leader is the escalation layer above the individual TAM — brought in on complex, high-impact, or multi-stakeholder issues rather than replacing the TAM as primary contact. This includes:

- Coordinating across support, engineering, and success during major incidents

- Owning execution of the Named Account Escalation SLA sequence when it's triggered

- Ensuring root cause analysis and preventative action actually close out, not just the immediate fire

- Isolating TAMs from technical repair work so they can stay focused on the relationship while the right team handles the fix

STRATEGIC TECHNICAL PLANNING (OVERSIGHT)

The TAM Leader ensures account plans across the book stay aligned to customer roadmaps, and personally engages on capacity, architecture, or growth planning for the largest or most strategic accounts and partners.

INTERNAL COLLABORATION

ENGINEERING AND PRODUCT

The TAM Leader represents the aggregated voice of the customer — patterns across accounts, not just one-off feedback — to engineering and product, and prioritizes which recurring pain points or gaps get pushed for a fix versus handled as one-offs.

SUPPORT

The TAM Leader maintains the operating agreement between TAM and Support (TAMs are not frontline support) and is the point of escalation when that boundary needs adjudicating on a specific account.

SALES AND CUSTOMER SUCCESS

The TAM Leader partners with Sales and Success leadership on account health and retention at the portfolio level — surfacing which accounts or partners are trending at risk, and where TAM coverage itself needs to change to protect NRR.

PARTNERSHIPS

Because the TAM Leader owns the Technical Account Manager assignments inside the Partner Mappings, they work directly with each partner's Account Quarterback, Partner Manager, and Solutions Architect to make sure the technical relationship keeps pace with partner stage (Prospecting through Scaling) and tier (Strategic AI, Growth, Other) — while staying out of commercial terms, which live with the Partner Manager.

SUCCESS METRICS

Common indicators of TAM Leader effectiveness include:

- Coverage: % of the $33.1M+ named-account book and partner-mapped accounts with an assigned, active TAM

- Team health: ramp time to productivity for new TAMs, retention of the TAM team itself

- Customer adoption and usage depth across the book

- Reduction in critical incidents and time to resolution for escalated issues, portfolio-wide

- Customer satisfaction and retention (NRR) across named and partner-mapped accounts

- Consistency: QBR completion rate and account plan quality across the team, not just top performers

TOOLS USED BY THE TAM TEAM

This section documents the tools and systems used by the Technical Account Management team. It is intended to be kept up to date as tooling evolves.

- Admin Studio

- Grafana

- Hex

- pgAdmin

- HubSpot (account ARR, tier, and health data)

- Notion — Draft TAM Accounts doc and Partner Mappings database

SCOPE OF COVERAGE

The TAM Leader is accountable for the full combined book the function covers, not a single portfolio:

1. Named accounts in the Draft TAM Accounts doc https://app.notion.com/p/3b35004b775f805ab27ed2cfede681c1?pvs=21 — every account already assigned to one of the individual TAMs, plus resolution of open decisions such as the current APAC coverage gap

2. Partner-mapped accounts in the Partner Mappings https://app.notion.com/p/9715782ec0d645368d2bea677ae90759?pvs=21 — ensuring every partner that warrants a technical relationship has a named TAM against it, and that the mapping stays current as partners move through Stage and Tier

ACCOUNT MAPPING

TAM Standard (Pooled)

1. Spend — For customers at $100K ARR, access to pooled TAM resources for a set (time TBD) hours per month

2. Pooled TAM SKU — Customers of any scale can purchase pooled access to the TAM team (requires Enterprise Support SKU)

3. Leadership Discretion for Customer Needs

TAM Premium (Dedicated)

1. Spend — For customers at $250K ARR, access to a dedicated TAM resource for a set (time TBD) hours per month

2. Dedicated TAM SKU — Customers of any scale can purchase an assigned TAM (requires Enterprise Support SKU)

3. Leadership Discretion for Customer Needs

The TAM Leader owns tier decisions, the quarterly refresh of this mapping, and any leadership-discretion exceptions.

WHAT TAM LEADERS DO NOT DO

To keep the function focused and scaling, the TAM Leader does not:

- Replace the individual TAM as an account's day-to-day technical relationship owner — accounts scale by layering support on, not by handing off

- Perform day-to-day operational work for customers

- Own or negotiate commercial terms for either named accounts or partner deals — that stays with the AE or Partner Manager

- Act as professional services for custom implementations

- Manage frontline support case queues

IDEAL INDIVIDUAL

A world-class Technical Account Manager Leader at Supabase has done the individual TAM job well and now wants to multiply it across a team.

- Technical depth — Same bar as an individual TAM: can go deep on database internals, scalability, security posture, and infrastructure tradeoffs, and can still credibly work a strategic account directly when needed

- People leadership — Has hired, coached, and grown a technical team before; gives direct, specific feedback and knows how to develop someone from good to great

- Portfolio-level judgment — Can look across 100+ accounts and a partner book and tell where coverage is thin, where an account should move tiers, and where to spend leadership discretion

- Escalation command — Comfortable being the senior voice in a high-severity, multi-stakeholder incident, coordinating support, engineering, and success without adding noise

- Cross-functional influence at altitude — Represents patterns across the whole book to engineering, product, sales, and partnerships leadership — not just one account's feedback

- Communication clarity — Can brief an executive on portfolio health and coach a TAM through a root cause analysis in the same day

- Retention and expansion awareness — Understands that TAM Leader performance shows up in aggregate NRR across the book; proactively rebalances coverage toward the accounts and partners most at risk

- Experience — Background in engineering, SRE, or technical consulting, plus a track record of leading a technical customer-facing team

SUMMARY

The Technical Account Manager Leader exists to make sure every account and partner relationship the TAM function is accountable for — the full Draft TAM Accounts book and the entire Partner Mappings coverage — has a technical owner, and that the team delivering against it keeps getting better.

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.

- ~400 team members

- 60+ countries

- 20+ languages spoken

- Over $1B raised (including our $500M Series F)

- 540,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.