Cursor
Software Engineer, Services Platform
San FranciscofulltimemidAdded 1 month ago
About this role
Build foundational platform abstractions that enable hundreds of engineers to ship resilient systems at scale. You'll design service provisioning frameworks, workflow orchestration standards, and deployment tooling that make it easy for teams to operate services reliably.
What you'll do
- Design and implement platform-level primitives for service provisioning, deployment, and operations
- Establish durable workflow orchestration standards and best practices across the organization
- Create declarative service configuration frameworks to accelerate service creation and deployment
- Define service ownership contracts and build tooling to reduce incident resolution time
- Work on deployment tooling, CI/CD infrastructure, and service mesh architectures
- Partner with product teams to improve developer experience and system resilience
What they're looking for
- Internal developer platforms or infrastructure abstraction design
- Workflow orchestration systems (Temporal or similar)
- Deployment tooling and CI/CD pipeline experience
- Microservice architecture design and service decomposition
- Service mesh architectures
- Strong software engineering fundamentals
- Developer experience mindset
- Production system design and reliability
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 built an internal developer platform or infrastructure abstraction that other teams depended on. What made it successful or what would you do differently?
- Describe your experience with workflow orchestration systems like Temporal. What are the key design patterns you've seen work well, and what pitfalls should teams avoid?