1 min lesson
Recruiter & hiring-manager screen
Draft a two-sentence "why Cursor" for the recruiter screen that a different candidate could not have written.
Step 1 of 2
The first call is short and easy to underestimate. It sorts for a specific reason you want Cursor's research, a research background that fits RL-for-coding and the basic logistics that make a hire possible. Generic enthusiasm fails here faster than anywhere else in the loop.
What this screen covers
- Length & tone
- 30-45 min, conversational - background, motivation and logistics, not a quiz.
- Research fit
- Where your work sits relative to RL for LLMs, reward modeling and agent-assisted coding.
- Why Cursor
- A concrete bet you care about: RL on real sessions, graders for non-verifiable rewards, online RL.
- Logistics
- Location (SF / NY), visa and sponsorship status and timeline - surfaced early on purpose.
Your application already carries signal before this call. The job asks for a GitHub and a project description, so your prior work is screened before you ever talk to a human. Treat the recruiter call as the moment to turn that paper trail into a story.