1 min lesson
The seventh responsibility
Tell someone how to act on this idea: "Writing changelogs and shaping the developer narrative."
Step 1 of 3
The seventh responsibility - writing changelogs and shaping the developer narrative - sits alongside the rest because at Cursor the person who built the feature is often the person best placed to explain it to engineers. Marketing copy is not handed off; it's part of the craft of shipping.
Learn more
Advanced table
Reference table
- Responsibility
- Build the first version yourself
- What it really tests
- Can you prototype with AI tools and reason about architecture?
- Where it shows up in the loop
- Onsite small project (prototype or spec/teardown)
- Responsibility
- Set direction across individual + enterprise
- What it really tests
- Segmentation judgment and the courage to cut
- Where it shows up in the loop
- Onsite "discuss ideas" strategy session
- Responsibility
- Own launch end-to-end with PMM
- What it really tests
- GTM sequencing and closing the feedback loop
- Where it shows up in the loop
- Product/execution rounds and the discuss-ideas session
- Responsibility
- Customers, sales, field, demos
- What it really tests
- Developer empathy and live composure
- Where it shows up in the loop
- Behavioral round; demo running may appear onsite
- Responsibility
- Kill the 1,000 paper cuts
- What it really tests
- Taste and trust-and-craft instinct
- Where it shows up in the loop
- Discuss-ideas paper-cut triage; behavioral stories
- Responsibility
- Metrics with data science
- What it really tests
- Defining success so you don't reward a worse product
- Where it shows up in the loop
- Product rounds and the metrics part of discuss-ideas
| Responsibility | What it really tests | Where it shows up in the loop |
|---|---|---|
| Build the first version yourself | Can you prototype with AI tools and reason about architecture? | Onsite small project (prototype or spec/teardown) |
| Set direction across individual + enterprise | Segmentation judgment and the courage to cut | Onsite "discuss ideas" strategy session |
| Own launch end-to-end with PMM | GTM sequencing and closing the feedback loop | Product/execution rounds and the discuss-ideas session |
| Customers, sales, field, demos | Developer empathy and live composure | Behavioral round; demo running may appear onsite |
| Kill the 1,000 paper cuts | Taste and trust-and-craft instinct | Discuss-ideas paper-cut triage; behavioral stories |
| Metrics with data science | Defining success so you don't reward a worse product | Product rounds and the metrics part of discuss-ideas |
Each duty maps to a skill the loop grades and a stage where you'll show it.
Don't describe these as things you'd "coordinate" or "drive alignment on." Every one of them is something you personally do at Cursor: you write the prototype, you run the demo, you fix the paper cut, you pull the metric. Coordination verbs are a tell that you'd manage builders instead of being one.