Cursor
Software Engineer, Storage
San FranciscofulltimemidAdded 1 month ago
About this role
Join Cursor's Storage team to design and own the data layer serving millions of developers. You'll architect scalable database topologies, implement query safeguards, and define data store strategies that enable rapid product growth and reliability across the platform.
What you'll do
- Design and execute next-generation data architecture supporting multi-database topology at scale
- Build query attribution systems and guardrails to catch problematic patterns before production
- Create guidance and golden pathways for teams selecting appropriate data stores by workload
- Own cache infrastructure including reliability, capacity planning, and correctness patterns
- Ensure operational excellence through backups, monitoring, performance tuning, and capacity planning
- Collaborate with product teams to enable fast shipping without compromising data integrity
What they're looking for
- Relational database expertise (Postgres, MySQL, or similar OLTP systems)
- Database sharding, migration, and decomposition in production
- Storage engine architecture and tradeoff analysis
- Cache infrastructure design and management
- Query performance optimization and monitoring
- Systems design and software engineering fundamentals
- Operational excellence and infrastructure reliability
- Capacity planning and scaling strategies
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.
Cursor
Cursor builds an AI-driven code editor used by millions of developers to transform how software is built. The company is hiring for infrastructure engineers, ML systems specialists, enterprise platform builders, security engineers, and customer success roles focused on driving adoption within large organizations.
- Website
- cursor.com
Likely interview questions
- Tell us about a time you designed or executed a database sharding or migration strategy in production. What were the biggest challenges and how did you solve them?
- How do you approach choosing between different storage engines (e.g., Postgres vs. MySQL vs. NoSQL) for a given workload? Walk us through your decision-making process.