Technical Account Management (TAM) Leader

Supabase is the Postgres development platform, offering a complete backend in one place: database, auth, storage, edge functions, realtime and vector search. It was born remote and open-source-first, with no offices anywhere in the world.

The role

This position owns the health, direction and performance of Supabase's entire Technical Account Management function. Where an individual TAM looks after their own portfolio, the TAM Leader is accountable for the whole book — every account the team covers, every partner relationship with a technical dimension, and the people delivering against them.

Supabase describes it as a player-coach role. You carry direct accountability for coverage decisions, escalation outcomes and cross-functional alignment, while spending most of your time developing individual TAMs so the team's proactive, relationship-first approach scales rather than degrading into a reactive response channel.

The scope is concrete: roughly $33.1M ARR across 120 named accounts, capped at 20 accounts per TAM, plus partner-mapped accounts across Strategic AI, Growth and Other tiers.

Core responsibilities

• Hiring, onboarding and coaching TAMs, running 1:1s, setting development plans, and giving direct feedback on account plans, QBRs and escalation handling
• Owning the coverage model — who is assigned where, quarterly rebalancing as ARR shifts, closing gaps such as the current APAC coverage gap, and approving cap exceptions
• Ensuring every account has a clear technical owner, spot-checking documentation and risk tracking, and stepping in personally on the highest-risk accounts
• Auditing that post-sale architecture and deployment validation actually happens rather than being skipped
• Holding the team to a regular cadence of environment reviews covering scalability, reliability, security and lifecycle planning
• Acting as the escalation layer above individual TAMs on complex, multi-stakeholder incidents, and owning the Named Account Escalation SLA sequence
• Representing aggregated customer patterns to engineering and product, rather than one-off feedback
• Partnering with Sales and Success leadership on portfolio-level account health and NRR

What the role deliberately excludes

Supabase is unusually explicit about boundaries, which is useful for judging the job honestly. The TAM Leader does not replace individual TAMs as day-to-day relationship owners, does not perform operational work for customers, does not own or negotiate commercial terms, does not act as professional services for custom implementations, and does not manage frontline support queues.

What they are looking for

• Technical depth at the same bar as an individual TAM: database internals, scalability, security posture and infrastructure tradeoffs, with the credibility to work a strategic account directly
• Proven people leadership — having hired, coached and grown a technical team before
• Portfolio-level judgment across 100+ accounts, knowing where coverage is thin and where to spend leadership discretion
• Escalation command as the senior voice in high-severity, multi-stakeholder incidents
• Cross-functional influence with engineering, product, sales and partnerships leadership
• Communication range: briefing an executive on portfolio health and coaching a TAM through a root cause analysis in the same day
• A background in engineering, SRE or technical consulting, plus a track record leading a technical customer-facing team

Tools the team uses include Admin Studio, Grafana, Hex, pgAdmin, HubSpot and Notion.

What Supabase offers

• Fully remote, hiring globally. There are no Supabase offices anywhere, and the company provides a WeWork membership or co-working allowance usable in any country
• ESOP equity for every team member
• Tech allowance for your working setup
• 100% health insurance for employees and 80% for dependents, wherever you are based
• Annual company off-site, a full week in a new city
• Asynchronous operation with genuine control over your own time
• Annual education allowance

About the team

~400 people across 60+ countries, 20+ languages spoken, over $1B raised including a $500M Series F, and 540,000+ community members.

Why this suits a location-independent candidate

Supabase has never had an office, so remote is not a policy bolted onto an office culture — it is the only way the company has operated. Health cover follows the person rather than the postcode, and the co-working allowance works anywhere.

That matters more than usual for a leadership role. Senior positions are typically the first to get pinned to a headquarters; this one explicitly is not. The role also mentions an open APAC coverage gap, which suggests candidates based outside the Americas and Europe may be genuinely well positioned rather than tolerated.

No salary figures are published on this listing.