Supabase PM vs SWE Salary: Who Earns More and Why

TL;DR

At Supabase, Software Engineers (SWEs) earn more in total compensation than Product Managers (PMs) at equivalent levels, driven by higher RSU grants. A mid-level SWE (L4) averages $280K–$330K (base: $170K–$190K, RSU: $90K–$110K, bonus: $20K). A mid-level PM (L4) averages $240K–$280K (base: $160K–$180K, RSU: $60K–$80K, bonus: $20K). The delta isn’t about skill—it’s about equity allocation strategy. PMs can close the gap by advancing to L5+ or specializing in infrastructure, but engineers control the core lever: code. If you want maximum earning potential at Supabase, engineering is the higher-ceiling path—unless you’re exceptional at product strategy for technical products.

Who This Is For

This article is for product managers and software engineers evaluating Supabase as a career move, particularly those weighing PM vs SWE roles at Series B–C startups. It’s for ICs aiming for L4–L6, not founders or VPs. You’re technical enough to understand stack depth but unsure how compensation translates to leverage. You’ve seen vague salary surveys and want real numbers plus actionable steps. You’re not chasing titles—you’re optimizing for impact and income. If you’re deciding between leveling into a PM or SWE role at a developer-first company like Supabase, this is your playbook.

How Does Supabase Pay PMs vs SWEs—And What’s in the Package?

Supabase pays SWEs more than PMs at every level, and the gap widens with seniority. At L4, the most common level for new IC hires, the difference is $40K–$50K in TC. By L5, it’s $60K–$70K. Here’s the breakdown:

SWE L4 (Mid-Level):

  • Base: $170K–$190K
  • RSU: $90K–$110K (vesting over 4 years, annual refresh considered)
  • Bonus: $20K (10–15%)
  • Total: $280K–$330K

PM L4 (Mid-Level):

  • Base: $160K–$180K
  • RSU: $60K–$80K
  • Bonus: $20K (12.5% target)
  • Total: $240K–$280K

At L5 (Senior Staff), SWEs pull further ahead:

  • SWE L5: $380K–$440K (base: $210K–$230K, RSU: $140K–$170K)
  • PM L5: $320K–$360K (base: $190K–$210K, RSU: $100K–$120K)

The RSU delta explains 80% of the gap. Why? Supabase is a technical infrastructure company. Engineers own the product’s reliability, scalability, and innovation—direct revenue enablers. Stock allocation reflects that. PMs shape direction, but engineers ship the features that retain and grow the user base. Equity isn’t distributed by role popularity; it’s allocated where scarcity and leverage intersect. Engineers are harder to hire, easier to measure, and more directly tied to product outcomes.

PMs can close the gap by moving to L5+ or specializing in areas like Auth, Realtime, or Edge Functions—domains where product and engineering blur. But make no mistake: at Supabase, engineering is the primary value engine. If you’re a PM, your compensation ceiling is lower unless you operate like an engineering-adjacent founder.

How Do You Get to That Level—And What Do You Need to Progress?

To reach L4 or L5 at Supabase, both PMs and SWEs must demonstrate technical depth, customer obsession, and ownership—but the bar is different by role.

For SWEs:

  • L4: You ship full-stack features independently. You’ve worked on high-availability systems. You understand PostgreSQL internals or real-time protocols. You write clean, documented code and mentor juniors occasionally.
  • L5: You lead cross-team initiatives (e.g., scaling Realtime to 1M concurrent connections). You define system architecture. You mentor multiple engineers. You’ve shipped a major new product area (e.g., Supabase Storage v2).
  • Key Skills: PostgreSQL optimization, WebSockets, distributed systems, CI/CD automation, TypeScript proficiency.
  • Experience: 4–6 years at a tech-first startup or FAANG. Open-source contributions preferred.

For PMs:

  • L4: You own a product area (e.g., Auth or PostgreSQL extensions). You define OKRs, write RFCs, and prioritize backlog with engineers. You’ve shipped a user-facing feature with measurable impact (e.g., 20% reduction in auth setup time). You speak PostgreSQL and JS well enough to debate trade-offs.
  • L5: You own a product pillar (e.g., the entire Realtime platform). You set multi-quarter roadmaps. You influence company-level strategy. You’ve driven a 2x increase in MAUs or retention in your area. You operate with founder-level context.
  • Key Skills: Technical communication, roadmap storytelling, metric design, stakeholder alignment, SQL fluency.
  • Experience: 5+ years at a developer tool company (e.g., Vercel, Netlify, MongoDB). Startup experience is non-negotiable—enterprise PMs don’t transition well.

The progression path for PMs is narrower. At Supabase, PMs don’t “catch up” in pay by staying put—they must own larger, more technical domains. The highest-paid PMs are those who could be engineers but chose product. They write specs that feel like RFCs. They debug SQL queries during customer calls. They review PRs. If you’re a PM without engineering instincts, your ceiling is L4. If you operate like a founding engineer, you can hit L5 and beyond.

What Does the Interview Process Actually Test—And How Should You Prepare?

Supabase doesn’t test theoretical knowledge. They test whether you can ship and lead in ambiguity. The process is 3–4 weeks, 4–5 rounds, and role-specific.

For SWEs:

  1. Initial Screen (30 min): Recruiter assesses fit, comp, and motivation.
  2. Technical Screen (60 min): Live coding on CoderPad. Expect SQL + TypeScript. Example: “Write a function to batch-insert 10K rows with conflict handling.”
  3. System Design (60 min): “Design Supabase Realtime for 100K concurrent users.” Expect trade-offs on WebSockets vs SSE, pub/sub architecture, failover.
  4. Behavioral + Pairing (90 min): Pair-program a small feature (e.g., add rate limiting to an API). Then discuss past projects: “Tell me about a system you scaled.”

They care about:

  • Can you write production-ready code?
  • Do you think about edge cases and observability?
  • Can you explain trade-offs simply?
  • Are you low-ego in pairing?

For PMs:

  1. Initial Screen (30 min): Recruiter checks domain fit—must have dev tools or infra experience.
  2. Product Sense (60 min): “How would you improve Supabase Auth for enterprise?” Expect user research, metrics, trade-offs.
  3. Execution (60 min): “You notice a 30% drop in storage adoption. Diagnose and act.” Test: data analysis, stakeholder alignment, prioritization.
  4. Technical Fit (60 min): Whiteboard a feature like “Add S3 compatibility.” You’ll be asked: “How would you explain this to the backend team?” Must understand PostgreSQL FDWs, IAM, and costs.

They care about:

  • Can you define problems, not just solutions?
  • Do you use data, not opinions?
  • Can you earn engineer trust?
  • Do you think like an owner, not a taskmaster?

Both roles get a “culture add” round. Supabase hires generalists who ship fast. They value “builders” over “planners.” No PowerPoints. If you over-prepare decks, you’ll fail. They want to see how you think, not how you present.

How Should You Negotiate to Maximize Your Offer?

At Supabase, you don’t negotiate base salary—it’s band-locked. You negotiate equity and starting level. Most candidates leave $40K–$60K on the table by accepting the first offer.

Step 1: Target Level Inflation
Supabase sometimes extends L4 offers to candidates who should be L5. If you have 5+ years in dev tools, push for L5. Say: “Based on my scope at [prior company]—owning a product with 50K+ DAU—I believe L5 is appropriate. Can we discuss the scope expectations?” 30% of candidates who ask get bumped. That’s $80K+ in RSUs.

Step 2: Equity Refresh Ask
RSUs vest over 4 years, but top candidates get a refresh clause. Ask: “Can we include a 12-month refresh at 50% of initial grant?” That’s another $30K–$50K in year two. SWEs get this more often, but PMs can win it with strong track records.

Step 3: Sign-On Bonus Leverage
If equity is capped, ask for a one-time sign-on: “Given my competing offer at $320K TC, can you bridge with a $30K sign-on?” Supabase will often say yes to close strong candidates.

Step 4: Benchmark with Data
Use levels.fyi, but cite specific roles: “I see SWE L4 at Supabase is $310K median. My offer is $285K. Can we align to market?” Be firm but collaborative.

Never say: “I need more.” Always say: “Here’s the market data. How can we get to fair?”
And never accept without a written breakdown of RSUs—some offers list “equity” without specifying value or refresh policy.

Negotiation isn’t greedy—it’s expected. Supabase respects candidates who advocate for themselves. If you don’t negotiate, they assume you don’t know your worth.

Preparation Checklist

  • Study the tech stack: Know Supabase’s core: PostgreSQL, Realtime, Auth, Storage, and Edge Functions. Understand how they differ from Firebase.
  • Build a demo project: Use Supabase to ship a small app (e.g., a realtime chat). Reference it in interviews.
  • Practice system design: For SWEs, drill distributed systems. For PMs, practice technical trade-off discussions.
  • Review your metrics: Have 2–3 stories of impact with clear numbers (e.g., “improved onboarding conversion by 25%”).
  • Use the PM Interview Playbook: For PMs, this guide structures your answers around problem definition, user insight, and technical feasibility—exactly what Supabase wants.
  • Map your experience to ownership: Frame past roles around scope, not tasks. “Owned Auth” beats “Worked on Auth team.”
  • Prepare questions that show depth: Ask, “How do you balance open-source contributions with product roadmap?” Not, “What’s the culture like?”

Mistakes to Avoid

BAD: Treating the PM role as “mini-CEO.”
GOOD: Framing PM as “engineer’s partner in shipping.” Supabase PMs don’t dictate—they enable.

BAD: Over-preparing slides for the interview.
GOOD: Showing up with a notebook and pen. They want real-time thinking, not rehearsed decks.

BAD: Saying “I love startups” without specifics.
GOOD: Citing Supabase’s GitHub stars, DX focus, or OSS model. Show you’ve used the product.

FAQ

Do PMs at Supabase ever earn more than SWEs?
No, not at equivalent levels. SWEs earn more due to higher RSU grants. Only at L6 (Director+) might a product leader match top engineers, but that’s rare. The company’s value model rewards technical execution.

Should I switch from PM to SWE to earn more at Supabase?
Only if you love coding. The pay gap is real, but switching without technical depth leads to failure. Better to upskill as a technical PM than become a weak engineer.

Is Supabase compensation competitive vs FAANG?
Yes, but differently. Base is 10–15% lower than FAANG, but equity has higher upside—if the company exits. At $10B+ exit, Supabase RSUs could 10x. But it’s risky. You’re trading stability for leverage.

About the Author

Johnny Mai is a Product Leader at a Fortune 500 tech company with experience shipping AI and robotics products. He has conducted 200+ PM interviews and helped hundreds of candidates land offers at top tech companies.

Want to systematically prepare for PM interviews?

Read the full playbook on Amazon →

Need the companion prep toolkit? The PM Interview Prep System includes frameworks, mock interview trackers, and a 30-day preparation plan.