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.
Product Manager
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.
About the Role
Product at Cursor is not a traditional PM org. We have product-minded engineers building tools for developers. Every project is ambiguous. There is no roadmap committee. The role is to take an idea and turn it into something customers use every day.
That means you do what it takes. Customer discovery. Writing code. Onsite implementations. High-stakes demos. Blog posts. PMs here are technical builders. You should be able to build and deploy an app yourself, reason through architecture decisions with engineering, and pair with design on UX. Titles matter less than the quality of what ships.
There is a lot of work left to do and many of these problems are new. The agent era is changing what developers need from their tools faster than most product organizations can keep up with. We think that's an opportunity.
This role is based in SF or NY. We build in person.
Example projects include...
- Building the first version of a feature yourself—prototyping with AI coding tools, getting it in front of users, and iterating until it's ready to hand off or scale with engineering.
- Defining feature strategy for capabilities that need to work at scale, across individual developers and enterprise teams. Scoping what to build, what to cut, and in what order.
- Owning launch execution end-to-end with PMM: GTM checklists, rollout sequencing, feedback loops, and measuring what worked.
- Partnering directly with customers, sales, field engineering, and TAMs to align what we build with what they need. Running demos when the stakes are high. Doing BD work when a partnership matters.
- Prioritizing the 1,000 paper cuts—triaging, sequencing, and making sure the small things that erode trust actually get fixed.
- Working with data science on instrumentation, metrics, and measuring success. Building the feedback loops that tell you whether what shipped is working.
- Writing changelogs, shaping marketing, and telling the story of what we built clearly enough that developers understand it on first read.
You may be a fit if
- You use AI coding tools daily—not as a novelty, but as part of how you work. You use them to read code, prototype, and move faster.
- You have been an engineer or have deep experience with developer tools. You can navigate a codebase without pulling engineers off their work.
- You have worked on infrastructure, cloud, or platform products. We are less interested in a narrow consumer product background.
- For enterprise-focused work: you have shipped enterprise developer products, you are comfortable with sales, and you are polished but gritty.
- You are an executor. You default to shipping the high-leverage thing now, not spending months exploring what to build.
- You can build and deploy an application yourself and reason through technical architecture with engineers.
- You move fast and communicate clearly. You are comfortable owning decisions that directly affect the product millions of developers use.
Applying
If there appears to be a fit, we'll reach out to schedule 2-3 interviews. After, we'll schedule an onsite in our office, where you'll work on a small project, discuss ideas, and meet the team.