Principal Software Engineer - Roblox Database

Roblox Roblox · Consumer · San Mateo, CA · Software Engineering

Principal Software Engineer role focused on building and operating a next-generation, multi-tenant database platform at Roblox. Responsibilities include designing and implementing engine features (indexing, storage, replication, sharding), evolving the control plane for elastic scaling and autonomous healing, optimizing critical code paths, establishing engineering best practices, and automating platform operations. Requires deep experience with large-scale distributed databases, database internals, and C/C++, GO, or Rust.

What you'd actually do

  1. Design and implement new engine features—indexing, storage formats, WAL and replication protocols, sharding, and query-planner enhancements—that push latency, throughput, and availability boundaries.
  2. Evolve the control plane to deliver elastic scaling, autonomous healing, and zero-downtime schema or tenant moves across global regions.
  3. Profile and optimize critical code paths using kernel-level tracing and advanced performance tooling; drive systematic tail-latency reductions.
  4. Establish engineering best practices by leading design reviews, performance benchmarks, failure drills, and post-incident retrospectives.
  5. Automate everything: develop frameworks for testing, CI/CD, rollout safety, observability, and autoscaling so that the platform operates hands-off at scale.

Skills

Required

  • 8+ years of experience in software engineering or a relevant field
  • Building and operating large-scale distributed databases or storage engines (e.g., PostgreSQL, MySQL/InnoDB, RocksDB, Spanner, Aurora, AlloyDB)
  • Database internals—B-trees, MVCC, WAL, query optimization, buffer management
  • C/C++, GO or Rust
  • Consensus algorithms (Raft, Paxos) and multi-region replication models
  • Shipping high-QPS, low-latency services on container orchestration stacks (Kubernetes or Nomad) with comprehensive observability
  • Turning ambiguous product requirements into a clear technical roadmap and influence cross-functional stakeholders
  • Automation, rigorous testing, and data-driven decision-making

Nice to have

  • Upstream contributions to PostgreSQL, RocksDB or other OSS databases
  • Familiarity with disaggregated storage, HTAP workloads, or custom query languages

What the JD emphasized

  • large-scale distributed databases
  • database internals
  • high-QPS, low-latency services