1 min lesson
Player-coach, not pure manager
Walk through each part of "Player-coach, not pure manager", then explain what each one does.
Step 1 of 2
Cursor's culture line is blunt: no narrow job descriptions. Engineers - and managers - write copy, fix user issues, optimize infra and sit in hiring loops. An EM here is a player-coach who still ships, not a process owner who delegates the building.
The org is flat and lean with limited management hierarchy. Decisions happen through conversation and consensus, not approval chains. That structure only works if the manager in the room can argue the technical merits, not just facilitate the meeting.
- Player
- Review code, make architecture calls, contribute directly to auth/webhooks/agent backend.
- Coach
- Source, interview, hire, mentor and grow backend engineers.
- Decisions
- Won by argument and evidence in conversation, not by your title in an approval chain.
- Hierarchy
- Shallow on purpose; you can't hide behind layers of reports or process.
This is the trap to avoid in prep: the role is failed from both ends. A brilliant builder who can't grow a team is wrong for it and so is a polished people-manager who hasn't touched production in years. The loop is engineered to screen against the second far harder than most companies do.
Learn more
Advanced table
Reference table
- Dimension
- Code
- Big-company hands-off EM
- Reviews occasionally, rarely writes
- Cursor player-coach EM
- Reviews regularly, ships on hot paths
- Dimension
- Architecture
- Big-company hands-off EM
- Approves designs in a doc
- Cursor player-coach EM
- Makes the call and defends it in conversation
- Dimension
- Decisions
- Big-company hands-off EM
- Routed through approval chains
- Cursor player-coach EM
- Won by argument and consensus
- Dimension
- Screening
- Big-company hands-off EM
- Behavioral and org-design focus
- Cursor player-coach EM
- Hands-on coding with no AI, plus a paid build session
- Dimension
- Failure mode
- Big-company hands-off EM
- Loses touch with the system
- Cursor player-coach EM
- Can't both build and grow people
| Dimension | Big-company hands-off EM | Cursor player-coach EM |
|---|---|---|
| Code | Reviews occasionally, rarely writes | Reviews regularly, ships on hot paths |
| Architecture | Approves designs in a doc | Makes the call and defends it in conversation |
| Decisions | Routed through approval chains | Won by argument and consensus |
| Screening | Behavioral and org-design focus | Hands-on coding with no AI, plus a paid build session |
| Failure mode | Loses touch with the system | Can't both build and grow people |
Cursor screens against the hands-off pattern that some large orgs tolerate.