The opportunity
Sentry’s Foundational Storage team builds and supports the stateful storage systems that all our products rely on: object storage, relational databases, key-value stores, and caches. We help Sentry engineers store and access data consistently, durably, securely, and efficiently as our products and traffic grow.
What you'll do
Design and operate storage systems used across Sentry, including their configuration and performance tuning.
Create APIs and abstractions that make storage easy for product teams to use,: with best practices for correctness, security, and scale built in.
Solve storage challenges at scale, including consistency under concurrent: access, sharding and rebalancing, and routing reads and writes across storage backends as workloads grow.
Work with product engineers to choose storage approaches, plan safe: migrations, and help teams adopt the tools you build.
Plan and build with other Platform and Infrastructure teams, including: analytical storage and streaming, to deliver a complete, fault-tolerant platform for product teams. Align roadmaps and standards, and design for failures and recovery.
Improve storage performance and cost efficiency by making better use of: backends and resources, while keeping the platform simple for product teams.
What they're looking for
- + years of software engineering experience building and operating distributed, stateful systems in production.
- Hands-on experience with object storage, relational databases, OR caching: systems at production scale. Experience with key-value or wide-column stores is a plus.
- An understanding of distributed systems fundamentals, including consistency,: concurrency, and what happens when requests fail or need to be retried.
- Proficiency in a systems language such as Go, C++, Java, or Rust, and comfort: working in Python. We primarily use Rust and Python, and welcome engineers who are new to Rust.
- Experience running services on Kubernetes in a cloud environment, including: observability, SLOs, and incident response. Familiarity with Terraform is a plus.
- Good written and spoken English, especially in explaining technical choices and writing documentation.
- Nice to have: experience building shared libraries or internal APIs, migrating data between systems, or improving system performance and cost.
