Software Engineer, Services Platform

Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and engineering. Our organization is very flat, and our team is small and talent dense. We particularly like people who are truth‑seeking, passionate, and creative. We enjoy spirited debate, crazy ideas, and shipping code.

As a Software Engineer, Services Platform at Cursor, you'll build the platform-level primitives that make it hard for product teams to build brittle systems and easy to build resilient ones.

Cursor is scaling fast, hundreds of engineers shipping to millions of developers, and your core focus will be the abstractions that make that sustainable: service provisioning, deploy tooling, workflow orchestration, and defining what it means to own and operate a service 'll work at the intersection of developer experience and production reliability, building the golden pathways that every engineering team runs on.

• Establishing durable workflow orchestration as a first-class platform: defining best practices, building shared abstractions, and creating the standard that every team uses for reliable, long-running workflows.

• Designing a declarative service configuration framework that makes it trivial to provision, deploy, and operate new services, so spinning up a new backend goes from days to minutes.

• Defining the contract for service ownership: what it means to own a service, how services integrate with Cursor's infrastructure abstractions, and building the service catalogue so incidents get resolved in minutes, not hours.

• You have experience building internal developer platforms, service frameworks, or infrastructure abstractions that other engineers depend on.

• You've worked extensively with Temporal, durable workflow engines, or similar orchestration systems and have strong opinions on best practices.

• You care deeply about developer experience. You think about how other engineers interact with your systems and design for simplicity and correctness by default.

• You have experience with deployment tooling, CI/CD pipelines, or service mesh architectures.

• You understand the tradeoffs in microservice vs. monolith architectures and can help teams navigate service decomposition pragmatically.

• You have strong software engineering fundamentals and enjoy shipping production systems that make the entire organization more productive.