Skip to main content

PlanetScale

Software Engineer - PlanetScale Postgres

Remote (Remote)$120k–$290kmidAdded 1 month ago

About this role

PlanetScale is seeking a Software Engineer to enhance their managed Postgres service, focusing on building robust solutions for provisioning, scaling, and safeguarding data. The role requires expertise in large-scale Postgres systems and the ability to collaborate with teams and customers to drive improvements.

What you'll do

  • Design and build the control plane for Postgres clusters
  • Maintain high availability and disaster recovery solutions
  • Tune Postgres for large-scale workloads
  • Develop tooling for operations, backups, and migrations
  • Collaborate directly with customers to enhance platform offerings

What they're looking for

  • 5+ years in software engineering
  • Proficiency in Go and other languages (Ruby, Python, Zig, Rust)
  • Experience with distributed fault-tolerant services
  • Knowledge of Kubernetes and containerized applications
  • Understanding of operating systems concepts

Benefits

  • Support for diverse backgrounds
  • Inclusive work environment
  • Accommodations for disabilities
  • Equity in compensation
  • Base salary range of $120,000 - $290,000 USD
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

PlanetScale

PlanetScale builds advanced database infrastructure products including Neki, a sharded PostgreSQL platform, managed Postgres services, and database observability tools. The company is hiring Software Engineers to develop core database systems, contribute to PostgreSQL engines, build orchestration platforms, and enhance monitoring and insights products.

View all jobs at PlanetScale

Likely interview questions

  • Walk us through your experience operating large-scale Postgres deployments in production—what were the biggest challenges you faced around scaling, replication, or failover?
  • Describe a time you designed a control plane or orchestration system for managing infrastructure at scale. What trade-offs did you make?