The Split That Defines the Company
A database infrastructure company born from YouTube's scaling crises now hires more people to talk to customers than to build the database. The pattern is deliberate.
Of the 13 current openings on PlanetScale's careers page, seven fall in marketing, sales, customer success, and developer education: Brand Designer, Sales Development Representative, Head of Events, Customer Support Engineer, Solutions Engineer, Developer Educator, Enterprise Support Engineer. The remaining six target core engineering: Software Engineers for Neki Orchestration, Insights, Sharded Postgres, PlanetScale Vitess, PlanetScale Postgres, and Internal Tools. First-party board data shows a consistent salary band of $120,000–$290,000 across the engineering roles with a $250,000 median.
The engineering roles cluster around two product lines. The Vitess track, PlanetScale's original MySQL sharding layer, seeks engineers fluent in Go, MySQL internals, and Kubernetes for the PlanetScale Vitess role (EMEA remote) and Internal Tools (San Francisco). The newer Postgres track, branded Neki, carries three distinct openings: Neki Orchestration, Sharded Postgres, and PlanetScale Postgres, all listed as San Francisco Bay Area or remote. A sixth engineering role, Insights, sits in the same geographic band. Sugu Sougoumarane, who co-created Vitess at YouTube before founding PlanetScale in 2018, said the Postgres push was an itch he couldn't ignore after a sabbatical: "when I saw postgres I just couldn't control myself."
The Bar in Concrete Terms
The company's own hiring documentation defines the bar unusually specifically. "P99 individuals" (their phrase for engineers who operate at the 99th percentile of autonomy) must bring five-plus years of backend experience, deep Go proficiency, and MySQL or relational database expertise. Kubernetes and containerized application knowledge is required, not preferred. The nice-to-have list reads like a distributed systems syllabus: database internals, query optimization, Raft consensus, open-source infrastructure contributions, major cloud platforms. Soft skills carry equal weight: written and verbal communication, self-motivation, autonomous execution, and a passion for mentoring juniors.
Recruiter-facing guidance highlights four common misreads. PostgreSQL experience does not transfer completely — PlanetScale's branching workflow differs fundamentally. Traditional DBA skills (backup, replication setup, failover) matter less because the platform handles operations; schema design and query optimization matter more. PlanetScale-specific experience is not required. Candidates who mistake this for a traditional DBA shop or a pure open-source play will not clear the screen.
Compensation: The Numbers and What They Mean
PlanetScale's compensation structure reflects a growth-stage infrastructure company that has raised over $100 million and operates in a $60 billion database market. On Zero G Talent's board, 11 salaried roles show a consistent band of $120,000–$290,000 with a median of $250,000, a figure that aligns with the company's need to attract senior engineering talent while managing burn rate at roughly 110 employees.
| Role | Salary Range (USD/year) | Location Notes |
|---|---|---|
| Software Engineer — Neki Orchestration | $120,000–$290,000 | San Francisco Bay Area or Remote |
| Software Engineer — Insights | $120,000–$290,000 | San Francisco Bay Area or Remote |
| Software Engineer — Sharded Postgres (Neki) | $120,000–$290,000 | San Francisco Bay Area or Remote |
| Software Engineer — PlanetScale Vitess | $120,000–$290,000 | EMEA Remote |
| Software Engineer — PlanetScale Postgres | $120,000–$290,000 | Remote |
| Head of Events | $180,000–$250,000 | San Francisco, CA |
The engineering band is notably wide — $170,000 between floor and ceiling, which suggests the company prices for experience level and domain depth rather than role title alone. A Vitess core contributor or someone who has operated sharded Postgres at scale will command the top of that range; a strong generalist backend engineer enters near the middle. The Head of Events role, the only non-engineering posting on the board, sits in a tighter $180,000–$250,000 band, reflecting a specialized marketing-leadership function rather than a broad IC ladder.
Equity is part of every offer. The company's careers page and BuiltIn listing both confirm company equity grants: 100% RSU with no cash bonus component, aligning long-term incentives with the company's growth-stage trajectory. The research does not specify the typical percentage allocation for a given level. Given the $100 million+ raised and a valuation that has not been publicly disclosed since the Series B, candidates should ask for the current 409A price and the fully diluted share count before signing (standard diligence at this stage).
Benefits are thorough on paper. BuiltIn lists health, dental, vision, and life insurance; generous PTO and paid holidays; paid sick days; generous parental leave; family medical leave; and a mobile phone discount. Glassdoor's aggregate of six anonymous reviews rates the benefits package 4.8 out of 5 stars. There is a conflict on retirement matching: Glassdoor reports "don't currently have 401K matching" while BuiltIn lists "Offers 401(K)" without mentioning a match. The safer reading is that a 401(k) plan exists but the company does not contribute, a common pattern at pre-profitability startups preserving runway. Candidates should confirm this directly with the recruiter.
The distributed, remote-forward model affects total compensation geography. The board shows identical $120,000–$290,000 bands for Bay Area and remote roles (including EMEA), signaling PlanetScale does not apply a location differential — a competitive advantage for candidates outside major hubs. However, the careers page notes that some roles may be "location specific" due to business requirements, and U.S. sanctions bar hiring from North Korea, Cuba, Iran, Syria, Sudan, the Crimean region of Ukraine, and Mainland China. PEO partnerships handle employment in countries where PlanetScale lacks a legal entity.
For a company of this size and funding level, the median $250,000 salaried compensation is aggressive, sitting above many Series B peers and signaling that PlanetScale's hiring bar is calibrated for engineers who can ship production-grade database infrastructure immediately.
How the Loop Runs
PlanetScale runs a compressed, three-to-five-week loop that typically spans three to four interviews. Glassdoor users report a 21-day average from application to decision across six submitted interviews; the company's own guide cites "3 rounds · ≈ 3-5 weeks" for software engineers, while the account-executive track describes "two to four weeks from the initial recruiter screen to the final decision." The process is coordinated through Greenhouse: applications land in the pipeline in arrival order, and recruiters review them sequentially, so early applicants get disproportionate attention.
The first gate is a 30-minute recruiter screen covering background, role fit, and logistics. Candidates who clear it move to technical evaluation. For software engineers, that means two technical rounds: one focused on systems programming and live coding, the other on distributed-systems design. The questions test core systems engineering capabilities: relational database behavior under load, concurrent code correctness, and the ability to break down multi-component challenges into structured, scalable solutions. You do not need to be a Vitess expert beforehand, but a strong foundation in MySQL or Postgres internals and distributed-systems concepts is expected. The final round is a leadership interview with a VP-level or senior engineering leader, assessing autonomy, execution, and collaboration mindset. PlanetScale describes its culture as "high trust, high autonomy, and asynchronous communication" built around "p99 individuals" who execute without micromanagement.
For customer-facing roles such as Account Executive, the technical rounds are replaced by a sales execution assessment and a cross-functional panel that includes engineers. Candidates must present a structured customer acquisition plan, demonstrate developer-focused marketing experience (technical content, open-source adoption, self-serve sign-ups), and avoid generic sales buzzwords — technical interviewers "will quickly tune out." A growth-mindset conversation about a lost deal or failed strategy is standard.
Recruiters screen for four pillars the company publishes explicitly: Role-Related Knowledge (backend systems, relational databases, distributed architectures), Distributed Systems Problem-Solving, Autonomy & Execution, and Collaboration & Open-Source Mindset. The last item reflects PlanetScale's Vitess roots; familiarity with the open-source project or comparable database tools is a differentiator. Candidates who over-engineer, proposing needlessly complex architectures where clean, pragmatic code would suffice, tend to stall. Communication clarity is weighed equally with technical depth because the distributed team operates asynchronously.
A strong application shows evidence of those pillars before the first call: a résumé that highlights open-source contributions, database internals work, or distributed-systems projects; a cover letter or portfolio that references PlanetScale's engineering blog or recent product launches (the Postgres launch, the Neki orchestration layer); and an application submitted within the first 48 hours of posting. Dataford found the offer rate across reported interviews sits at roughly 50 percent, and candidates consistently describe the experience as "positive, transparent, and average in difficulty."
Disqualifiers are practical rather than ceremonial: inability to articulate trade-offs in a distributed design, lack of hands-on relational database experience, reliance on sales jargon in technical conversations, or a track record that suggests dependence on heavy process and micromanagement. The company has no H-1B petition history on file, though its careers FAQ states it does sponsor visas. Candidates requiring sponsorship should raise it early.
Where the Work Actually Happens
PlanetScale has never operated like a traditional office-centric startup. The company was "always remote-friendly, but now it's doubling down on building a culture around asynchronous work," according to a Glassdoor review that captures the current operating model. That shift isn't recent window dressing — it traces back to the founding team's experience running Vitess at YouTube, where distributed systems engineering and distributed teams went hand in hand. By the time PlanetScale raised its Series B in June 2021, the company employed roughly 60 people and projected growth to 90 by year end, with hiring planned across sales, engineering, and support, all structured around location flexibility rather than a headquarters anchor.
The only named physical hub that appears consistently in current job postings is the San Francisco Bay Area. Multiple engineering roles, including Software Engineer for Neki Orchestration, Insights, Sharded Postgres, and PlanetScale Vitess, list "San Francisco Bay Area or Remote" as the location option. A Head of Events role posted more recently specifies "San Francisco, CA" without a remote alternative, suggesting that certain customer-facing or executive functions still gravitate toward a local presence. That pattern aligns with the company's hiring history: PlanetScale has poached at least 10 employees from GitHub since 2021, including former GitHub engineering VP Sam Lambert as chief product officer, and GitHub's own Bay Area footprint makes the region a natural recruiting ground. The company's DNA, as co-founder Jiten Vaidya said, "is from Google"; the Google/YouTube alumni network runs thick through the Bay Area.
Beyond the U.S., PlanetScale maintains an explicit EMEA remote track. A Software Engineer role for PlanetScale Vitess is tagged "EMEA - Remote," confirming that the company treats Europe, the Middle East, and Africa as a first-class hiring region rather than an afterthought. This isn't a token international hire; the role carries the same $120,000–$290,000 salary band as its U.S. counterparts, and the asynchronous culture note from Glassdoor suggests the time-zone spread is a design feature, not a compromise. Candidates in Berlin, London, or Lagos can expect the same onboarding, tooling, and promotion path as someone in Oakland — provided they can operate on written communication and documented decisions rather than hallway conversations.
What those distributed employees actually use day to day is less about physical facilities and more about the infrastructure that replaces them. The company builds a managed cloud service for Vitess that runs on AWS, Azure, and Google Cloud, and its own engineers dogfood that platform. There's no mention in any review or posting of a dedicated office lease, coworking stipend, or regional offsite cadence — the "facilities" are the CI/CD pipelines, the observability stack, and the shared documentation culture. One Glassdoor reviewer noted "the team values respect over raw performance. No one is allowed to be a jerk, no matter what they contribute technically," which in a fully async environment translates to rigorous code review standards and written RFC processes that substitute for in-person architectural debates.
The trade-off is visible in the employee sentiment data. Blind ratings as of June 2023 show a 2.0 out of 5 overall score, with Management at 1.0 — the lowest category, while Compensation and Benefits sits at 3.0. A separate Glassdoor benefits rating of 4.8 out of 5 (based on six reviews) highlights extensive benefits and unlimited PTO, though 401(k) matching is absent. The "hire and fire culture" flag on Blind and the advice to "check LinkedIn for company alumni" suggest turnover is non-trivial, and a distributed model can amplify onboarding gaps when documentation lags behind headcount growth. For a candidate evaluating where the work happens, the honest answer is: it happens in your home office, your coworking space, or your kitchen table — supported by a toolchain built for planetary-scale databases and a culture that treats synchronous meetings as a last resort. If you need a physical anchor, the Bay Area exists. If you don't, the rest of the map is open.
FAQ
PlanetScale Software Engineer interview FAQ
Answered from real candidate and compensation data
How many interview rounds does PlanetScale have for a Software Engineer, and what are they?
PlanetScale reports 4 interviews total for the Software Engineer experience. The process includes a Recruiter Screen, Technical Rounds focused on systems programming, live coding, and distributed systems design, and a final Leadership Interview with a leadership or VP-level member.
Is the PlanetScale Software Engineer interview difficult, and what offer rate do candidates report?
Candidates report the most common difficulty level as average. The reported offer rate is 50% based on 4 reported interviews.
What does PlanetScale test for Software Engineer interviews, especially for distributed systems and coding?
Technical Rounds focus on systems programming, live coding, and distributed system design. The role is also strongly aligned to distributed systems and database infrastructure topics including Distributed Systems, Database Infrastructure Engineering, Vitess, MySQL, and Horizontal Scaling, plus Go (Golang) and debugging distributed systems.
What are the most important topics to prioritize when preparing for a PlanetScale Software Engineer interview?
Prioritize distributed systems and database internals tied to PlanetScale, including Vitess and MySQL, and understand horizontal scaling. The topic list also includes debugging distributed systems, plus Go (Golang), and PostgreSQL, so be ready to connect those areas to backend behavior under load.
What software engineering interview questions are publicly available for PlanetScale, and how should I use them to prepare?
Public sample questions include "Resolving an Issue Independently" and "Balancing Technical Debt and Delivery." Use these as anchors for behavioral prep by preparing clear examples that show autonomy on ambiguous problems and a pragmatic approach to trade-offs.
What compensation can I expect for a PlanetScale Software Engineer role, and does it vary?
According to Dataford, reported compensation includes a base minimum of $40,062 and a total maximum of $940,156 in job-posting reports and candidate reports. Because pay varies by level and location, you should expect a wide spread rather than one fixed number.
Working in frontier tech? Zero G Talent tracks the openings: see every open PlanetScale role, browse frontier tech jobs, the companies hiring, and the people building the field.