> Markdown version of [/jobs/ext/4720423-software-engineer-storage](https://www.wearedevelopers.com/jobs/ext/4720423-software-engineer-storage). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Engineer, Storage

- **Company:** Cursor, LLC
- **Location:** San Francisco, CA, United States
- **Salary:** $140,000 - $225,000
- **Contract:** Permanent contract
- **Skills:** Query Performance, Databases, Data Architecture, Data Infrastructure, Data Stores, Relational Databases, Database Queries, Shard (Database Architecture), PostgreSQL, MySQL, Online Transaction Processing, Caching, Database Performance
- **Published:** November 14, 2026
- **Apply:** https://www.careerboard.com/us/en/find-jobs-in-United-States/-BD74F9FA86B94FDF80/

## About the Role

* Experience with relational databases at scale (eg, Postgres, MySQL, or similar OLTP systems). Experience building and scaling databases or data infrastructure. Understanding of database performance, reliability, and caching., * Experience tackling database sharding, migration, or decomposition problems in production environments
 * Understand the tradeoffs between different storage engines and can help teams make the right choices for their workloads
 * Care about operational excellence: backups, monitoring, query performance, and capacity planning are things you think about proactively
 * Strong software engineering fundamentals and enjoying building systems that other engineers depend on

## Description

* Design the next-generation data architecture: evolving our storage layer into a partitioned, resilient topology that keeps pace with SpaceXSI's rapid growth
 * Build query attribution and guardrails: instrumenting every database query by service, catching bad patterns before they hit production, and making it impossible to ship problematic queries without review
 * Define the "when to use what" strategy for data stores: creating clear guidance and golden pathways so every team picks the right engine for their workload without second-guessing
 * Own cache infrastructure end-to-end: reliability, capacity planning, and patterns that let product teams move fast without worrying about cache correctness