The opportunity
This role will be based in San Francisco. We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days) because we do our best thinking and building together in person.
What you'll do
Take a new product from alpha to general availability. Work with early: customers to understand what matters, iterate on feedback, and help shape what we ship.
Make real customer workloads fast. Improve query execution, indexing, and: client data loading so performance holds up as datasets grow and workflows become more demanding.
Build systems businesses can trust with their data. Make schema changes,: concurrent writes, permissions, and recovery reliable enough for customers to build essential workflows on top.
Make powerful capabilities approachable. Turn database provisioning,: migrations, and indexes into a reliable, easy-to-use product experience that gives people the power of a database without the burden of managing one.
Build for the customers who come next. Automate database provisioning and: fleet operations, strengthen observability, and evolve the architecture so we can serve many, many customers.
Production relational database experience (e.g., Postgres or MySQL). You’ve: made decisions about schemas and indexes, analyzed database performance, and debugged issues involving transactions, locking, or concurrency. Your experience goes beyond accessing a database through an ORM.
What they're looking for
- Engineering experience and technical leadership. You bring 10+ years of: experience building and operating production software, with a track record of setting technical direction and leading complex, cross-team initiatives from concept through delivery. You identify the most important problems to solve, turn ambiguous goals into a technical strategy, and align engineers and partner teams around a practical plan. You stay hands-on while helping others make better decisions through design reviews, mentorship, and clear technical guidance.
- Strong backend engineering fundamentals. You’ve built services that need to: remain correct under concurrency and failure. You can reason about retries, partial failures, consistency, and the trade-offs involved in reliable reads and writes.
- A systematic approach to performance. You use query plans, traces, profiles,: and experiments to find bottlenecks and verify improvements. You’re willing to follow a problem across storage, services, and client code rather than stopping at a team boundary.
- Product judgment. You’re interested in who will use what you build, not just: how it works. You can turn a customer’s problem into a technical approach and recognize when a better default or simpler workflow would solve it more effectively.
