Skip to main content

PlanetScale

Software Engineer - Insights

San Francisco Bay Area or Remote (Remote)$120k–$290kmidAdded 1 month ago

About this role

PlanetScale is looking for an experienced Software Engineer to join their Insights team, focusing on enhancing database observability products. The role involves working with Vitess, MySQL, and PostgreSQL to improve database performance monitoring and implement actionable insights for developers.

What you'll do

  • Instrument databases to emit performance data
  • Design and maintain data collection pipelines
  • Create dashboards and visualizations for database insights
  • Develop APIs for exposing insights data to customers
  • Collaborate on database observability features
  • Build tools for query analysis and performance profiling

What they're looking for

  • 5+ years of software engineering experience
  • Experience with observability and telemetry products
  • Knowledge of distributed systems
  • Proficiency in time-series data handling
  • Backend development (Go, Rust, Ruby, Python)
  • Ability to work across varying technical domains
  • Self-directed work style

Benefits

  • Supportive work environment
  • Diversity and inclusion focused
  • Work with top brands in tech
  • Competitive salary range
  • Equity opportunities
  • Remote work flexibility
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 a time you built an observability or monitoring product from scratch. What were the key technical decisions around data collection, storage, and visualization?
  • How would you approach instrumenting a distributed database system like Vitess or PostgreSQL to emit performance telemetry? What metrics would you prioritize?