Lead Technical Account Manager (TAM) at Supabase

About Supabase

Supabase provides a comprehensive Postgres development platform designed by developers for developers. It offers a full backend solution, including Database, Auth, Storage, Edge Functions, Realtime, and Vector Search, all deeply integrated and built for scalable growth.

About the Role

The Technical Account Manager (TAM) Leader is responsible for the overall health, strategic direction, and performance of the Technical Account Management function. While individual TAMs manage their own client portfolios, the TAM Leader oversees the entire TAM book of business, encompassing all covered accounts, technical partner relationships, and the team members delivering these services. This role is both a player and a coach, directly accountable for coverage decisions, escalation outcomes, and cross functional alignment, while primarily focusing on developing individual TAMs to ensure a proactive, relationship first approach that scales efficiently.

Core Responsibilities

People Leadership & Team Development

The TAM Leader is tasked with hiring, coaching, and developing the TAM team to ensure each member acts as a credible, proactive technical partner to their accounts. This includes:

• Hiring and onboarding new TAMs, guiding them through the TAM Path ramp program.
• Conducting regular one on one meetings, establishing individual development plans, and providing direct feedback on account strategies, quarterly business reviews (QBRs), and escalation management.
• Creating and maintaining repeatable playbooks for tasks such as upgrade runbooks, optimization strategies, and escalation patterns, ensuring consistent quality.
• Setting and upholding high standards for the team's technical expertise, proactivity, and communication skills.

Portfolio & Coverage Ownership

This role owns the coverage model for the entire function, involving the assignment, tracking, and periodic refreshing of account allocations, and addressing any emerging gaps. This covers two main account universes:

• Named accounts: The full portfolio, currently valued at over $33.1M ARR across 120 accounts, distributed among the team, with a cap of 20 accounts per TAM.
• Partner mapped accounts: All partners with a dedicated Technical Account Manager, spanning Strategic AI, Growth, and Other tiers.
• Executing quarterly reviews and refreshes of assigned accounts, rebalancing portfolios as ARR and strategic relationships evolve.
• Resolving open coverage issues (e.g., regions or account types lacking TAM alignment) and determining the appropriate solution, whether a controlled exception, a new hire, or a change in tier definition.
• Approving leadership discretion assignments and cap exceptions, and making decisions to trim or reassign accounts due to capacity limitations.

Customer Technical Ownership (Oversight)

The TAM Leader ensures that every assigned account, whether named or partner mapped, has a clear, accountable technical owner. They routinely review account documentation, architectural understanding, and risk tracking across the entire book, and directly intervene in the most strategic or high risk accounts.

Onboarding and Adoption (Oversight)

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

• Auditing that architecture and deployment validation occurs post sale, rather than being overlooked.
• Coaching TAMs on configuration guidance and the delivery of best practices.
• Tracking early success milestones across the entire portfolio, not just on an account by account basis.

Proactive Technical Guidance (Oversight)

The TAM Leader ensures environment reviews and the identification of risks and optimization opportunities occur regularly across the entire portfolio. This includes addressing scalability, reliability, security, and lifecycle planning, and holding the team accountable for any lapses in these reviews.

Issue Management and Escalation

The TAM Leader serves as the escalation point above individual TAMs, becoming involved in complex, high impact, or multi stakeholder issues, rather than replacing the TAM as the primary contact. This includes:

• Coordinating efforts across support, engineering, and success teams during significant incidents.
• Owning the execution of the Named Account Escalation SLA sequence when activated.
• Ensuring that root cause analysis and preventative actions are fully completed, not just the immediate resolution.
• Shielding TAMs from technical repair work, allowing them to maintain focus on client relationships while the appropriate team addresses the fix.

Strategic Technical Planning (Oversight)

The TAM Leader ensures that account plans across the portfolio align with customer roadmaps, and personally engages in capacity, architecture, or growth planning for the largest or most strategic accounts and partners.

Internal Collaboration

Engineering and Product

The TAM Leader articulates the collective voice of the customer, representing patterns observed across multiple accounts, rather than isolated feedback, to engineering and product teams. They prioritize recurring pain points or gaps for resolution versus those handled as one off issues.

Support

The TAM Leader upholds the operational agreement between TAM and Support (TAMs are not frontline support) and acts as the escalation point when this boundary needs clarification for a specific account.

Sales and Customer Success

The TAM Leader collaborates with Sales and Success leadership to monitor account health and retention at the portfolio level, identifying accounts or partners trending at risk, and where TAM coverage may need adjustment to protect Net Revenue Retention (NRR).

Partnerships

Due to owning Technical Account Manager assignments within Partner Mappings, the TAM Leader works directly with each partner's Account Quarterback, Partner Manager, and Solutions Architect. This ensures the technical relationship evolves with the partner's stage (Prospecting through Scaling) and tier (Strategic AI, Growth, Other), while steering clear of commercial terms, which remain with the Partner Manager.

Success Metrics

Key indicators of TAM Leader effectiveness include:

• Coverage: Percentage of the over $33.1M named account portfolio and partner mapped accounts with an assigned, active TAM.
• Team Health: Onboarding time to productivity for new TAMs and retention rates of the TAM team.
• Customer Adoption and Usage Depth: Across the entire portfolio.
• Reduction in Critical Incidents: And faster time to resolution for escalated issues across the portfolio.
• Customer Satisfaction and Retention (NRR): Across named and partner mapped accounts.
• Consistency: QBR completion rates and quality of account plans across the team, not just top performers.

Tools Used by the TAM Team

This section outlines the tools and systems utilized by the Technical Account Management team and is updated as tooling evolves.

• Admin Studio
• Grafana
• Hex
• pgAdmin
• HubSpot (for account ARR, tier, and health data)
• Notion (for Draft TAM Accounts doc and Partner Mappings database)

Scope of Coverage

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

1. Named accounts in the Draft TAM Accounts doc, including all accounts assigned to individual TAMs and resolution of pending decisions like the current APAC coverage gap.
2. Partner mapped accounts in the Partner Mappings, ensuring every partner requiring a technical relationship has a named TAM, and that this mapping remains current as partners advance through Stage and Tier.

Account Mapping

TAM Standard (Pooled)

1. Spend: Customers with $100K ARR gain access to pooled TAM resources for a predetermined number of hours per month.
2. Pooled TAM SKU: Customers of any size can purchase pooled access to the TAM team (requires an Enterprise Support SKU).
3. Leadership Discretion: For specific customer needs.

TAM Premium (Dedicated)

1. Spend: Customers with $250K ARR receive access to a dedicated TAM resource for a predetermined number of hours per month.
2. Dedicated TAM SKU: Customers of any size can purchase an assigned TAM (requires an Enterprise Support SKU).
3. Leadership Discretion: For specific customer needs.

The TAM Leader is responsible for tier decisions, quarterly mapping refreshes, and any exceptions made at leadership's discretion.

What TAM Leaders Do Not Do

To maintain focus and scalability, the TAM Leader does not:

• Replace the individual TAM as an account's day to day technical relationship owner; accounts scale by adding support, not by transferring ownership.
• Perform daily operational work for customers.
• Own or negotiate commercial terms for named accounts or partner deals; this remains with the Account Executive 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 successfully performed the individual TAM role and now seeks to amplify that impact across a team.

• Technical Depth: Meets the same high technical standards as an individual TAM, capable of diving deep into database internals, scalability, security posture, and infrastructure tradeoffs, and can credibly manage a strategic account directly when necessary.
• People Leadership: Has prior experience hiring, coaching, and developing a technical team; provides direct, specific feedback and excels at helping individuals grow from good to great.
• Portfolio Level Judgment: Can assess a portfolio of over 100 accounts and a partner book to identify coverage gaps, determine appropriate tier movements for accounts, and effectively apply leadership discretion.
• Escalation Command: Is confident as the senior voice during high severity, multi stakeholder incidents, coordinating support, engineering, and success without creating additional noise.
• Cross Functional Influence at Altitude: Represents aggregated customer patterns to leadership in engineering, product, sales, and partnerships, rather than just relaying feedback from a single account.
• Communication Clarity: Can brief an executive on portfolio health and coach a TAM through a root cause analysis on the same day.
• Retention and Expansion Awareness: Understands that TAM Leader performance is reflected in aggregate NRR across the portfolio; proactively adjusts coverage to prioritize accounts and partners most at risk.
• Experience: Possesses a background in engineering, Site Reliability Engineering (SRE), or technical consulting, coupled with a proven track record of leading a technical customer facing team.

Summary

The Technical Account Manager Leader ensures that every account and partner relationship within the TAM function's responsibility, encompassing the full Draft TAM Accounts book and the entire Partner Mappings coverage, has a dedicated technical owner, and that the team delivering these services continuously improves.

What We Offer

• Fully Remote: Supabase hires globally, believing that individuals perform their best work from any location. There are no Supabase offices, but a WeWork membership or co working allowance is provided worldwide.
• ESOP (Equity Ownership): Every team member receives equity ownership in the company, ensuring everyone shares in the collective success.
• Tech Allowance: A budget is provided to set up an ideal work environment, including a laptop, monitor, headphones, or any tools that enhance productivity.
• Health Benefits: Supabase covers 100% of health insurance for employees and 80% for dependents, regardless of location, prioritizing the well being of employees and their families.
• Annual Off Sites: The entire company gathers once a year in a new city for a week of connection, collaboration, and recreation.
• Flexible Work: The company operates asynchronously, trusting employees to manage their time effectively and prioritize tasks.
• Professional Development: Each team member receives an annual education allowance for learning opportunities, such as courses, books, conferences, or other growth supporting activities.

About the Team

Supabase was founded as a remote first, open source first company. Its globally distributed team is considered a key strength in developing tools that developers love.

• Approximately 400 team members.
• Representing over 60 countries.
• Speaking more than 20 languages.
• Over $1B raised (including a $500M Series F round).
• A community exceeding 540,000 members.

The company operates quickly, builds in public, and utilizes its own products. If it is in your project, it is likely used internally at Supabase. There is a deep commitment to the open source ecosystem.