2 min lesson
Documentation quality and correctness
Use "Documentation quality and correctness" to tell the cases apart, then choose a response for each one.
Step 1 of 3
The fastest way to lose a developer is a docs example that doesn't run. They don't file a bug. They quietly decide the product is unfinished and leave.
Holding a high bar on documentation quality and correctness across Cursor's developer surface is a named responsibility for this role. The job lists "comfortable reading source and SDK internals to verify claims" as a required skill. That phrasing is deliberate. Docs correctness here means verifying against the implementation, not restating a plausible guess.