PlanetScale is the serverless MySQL platform built on Vitess — the YouTube database technology. Founded by ex-YouTube database engineers. The interview emphasizes deep MySQL/Vitess engineering, large-scale sharding, and the unique product-engineering of git-style schema branching.
Process
Recruiter screen → 60-minute coding (Go preferred) → onsite virtual: 2 coding, 1 system design (distributed-systems-flavored), 1 craft deep-dive, 1 behavioral. Cycle: 3–5 weeks.
What they actually ask
- Design a sharded MySQL platform with consistent hashing
- Design a non-blocking online schema migration
- Design a git-style database branching workflow (branch, merge, deploy)
- Coding: medium-hard DSA, often with concurrency or systems framing
- Behavioral: ownership, deep technical taste, ex-YouTube/Vitess collaborative culture
Levels and comp (2026)
- SE: $180K–$245K total
- Senior SE: $255K–$345K total
- Staff: $360K–$485K total
- Principal: $500K–$670K total
Prep priorities
- Be fluent in Go (Vitess and most of PlanetScale) and SQL
- Understand Vitess internals (vtgate, vtablet, vschema, resharding)
- Brush up on MySQL internals (InnoDB, binlog, GTID, schema migrations)
Frequently Asked Questions
Is PlanetScale remote-friendly?
Distributed-first since founding. Engineers across US, EU, and APAC.
How does PlanetScale compare to Neon or Aurora?
PlanetScale is MySQL/Vitess-focused with strong sharding story. Neon is Postgres-focused with separated compute/storage. Aurora is the AWS-managed option for both. PlanetScale’s differentiator is git-style branching and the Vitess heritage. Comp competitive at senior+.
What is the engineering culture?
Senior-heavy, deeply technical, calm. Strong OSS contributor heritage (Vitess is CNCF). Written-first culture.