1 min lesson
The seven responsibilities, decoded
Say what this means in practice: "A responsibility on a JD is abstract."
Step 1 of 3
A responsibility on a JD is abstract. An artifact is what you'd actually hand a developer. The skill of this role is the translation: read "gather market intelligence" and know it means a structured feedback doc that lands in a product channel, not a vague promise to "talk to users."
Here is each responsibility mapped to the concrete thing you'd ship and the signal an interviewer reads from it.
Learn more
Advanced table
Seven bullets, but they collapse into two muscles
- JD responsibility
- Teach what you can build with API/SDK/Plugins/Automations
- The artifact you ship
- Tutorials, sample apps, reference repos that run end to end
- Signal it sends
- You can build the thing, not just describe it
- JD responsibility
- Explore the edges of AI models and agents
- The artifact you ship
- Experiments turned into write-ups and demos
- Signal it sends
- You probe what's new and make it shareable
- JD responsibility
- Automate your own work with agents
- The artifact you ship
- Canonical workflow examples others copy
- Signal it sends
- You dogfood the product to its ceiling
- JD responsibility
- Gather market intelligence from developers
- The artifact you ship
- Structured feedback loops routed into product
- Signal it sends
- You're a conduit, not just a megaphone
- JD responsibility
- Represent Cursor at events and online
- The artifact you ship
- Talks, threads, authentic community presence
- Signal it sends
- Developers trust you, not the brand voice
- JD responsibility
- Hold the bar on documentation correctness
- The artifact you ship
- Verify-before-publish discipline; fixed gaps
- Signal it sends
- You sweat correctness others wave past
| JD responsibility | The artifact you ship | Signal it sends |
|---|---|---|
| Teach what you can build with API/SDK/Plugins/Automations | Tutorials, sample apps, reference repos that run end to end | You can build the thing, not just describe it |
| Explore the edges of AI models and agents | Experiments turned into write-ups and demos | You probe what's new and make it shareable |
| Automate your own work with agents | Canonical workflow examples others copy | You dogfood the product to its ceiling |
| Gather market intelligence from developers | Structured feedback loops routed into product | You're a conduit, not just a megaphone |
| Represent Cursor at events and online | Talks, threads, authentic community presence | Developers trust you, not the brand voice |
| Hold the bar on documentation correctness | Verify-before-publish discipline; fixed gaps | You sweat correctness others wave past |
Seven bullets, but they collapse into two muscles: make a developer able to do something and feed what you learn back in.
The responsibilities are not equally weighted: the maker core is where a portfolio either carries you or sinks you.
Teach, explore the fringe, automate your own work.
Output is runnable code and demos.
This is what the work-trial actually tests.
Represent Cursor, gather intel, hold the docs bar.
Output is narrative, presence and feedback loops.
This is what the screen and portfolio test.