1 min lesson
Onsite-project simulation
Walk through "Onsite-project simulation" in order, then name the proof that tells you it worked.
Step 1 of 3
Cursor's signature round is a paid, multi-hour working session - one or two ~8-hour days building a real project alongside the team. No whiteboard theater. They watch how you actually build and whether they'd want you on the next desk.
You can't fully replicate a paid onsite at home, but you can rehearse the two things that go wrong: environment friction that eats your hours and forgetting that as an EM you're being judged on collaboration as much as the artifact.
Learn more
Full explanation
Kill environment friction before the day
Kill environment friction before the daySetup speed
Hours lost to a broken setup are hours you can't get back and fumbling your own editor in front of the team that builds the editor is a bad look. Get fast and fluent before you arrive.
- Know your Cursor and editor shortcuts cold - multi-cursor, jump-to-symbol, integrated terminal, git, test runner.
- Have a clean dotfiles/setup you can stand up in minutes and rehearse cloning + building + testing an unfamiliar repo end to end.
- Pre-decide your debugging loop: how you read an unfamiliar codebase, where you set the first breakpoint, how you find the test that covers the area.
Learn more
Advanced table
Solicit feedback on the right axis
Solicit feedback on the right axisWhat actually gets scored
- Signal
- Collaboration
- What they're watching
- Do you make pairs better - ask, listen, hand off cleanly?
- How to rehearse it
- Have your partner rate how it felt to build with you, not just the code.
- Signal
- Communication
- What they're watching
- Do you narrate intent and surface blockers early?
- How to rehearse it
- Practice thinking aloud; ask for the moments you went quiet or rabbit-holed.
- Signal
- Judgment / taste
- What they're watching
- Do you scope tightly and finish cleanly?
- How to rehearse it
- Review your diff as if it were a PR you'd approve or reject.
- Signal
- Culture fit
- What they're watching
- Would this team want you on the next desk?
- How to rehearse it
- Ask the honest question: was I someone you'd want to keep working with?
| Signal | What they're watching | How to rehearse it |
|---|---|---|
| Collaboration | Do you make pairs better - ask, listen, hand off cleanly? | Have your partner rate how it felt to build with you, not just the code. |
| Communication | Do you narrate intent and surface blockers early? | Practice thinking aloud; ask for the moments you went quiet or rabbit-holed. |
| Judgment / taste | Do you scope tightly and finish cleanly? | Review your diff as if it were a PR you'd approve or reject. |
| Culture fit | Would this team want you on the next desk? | Ask the honest question: was I someone you'd want to keep working with? |
The manager failure mode here is going full IC and disappearing into the code, head down, headphones on. That's the opposite of what they're hiring. Equally bad is the reverse - directing traffic without writing a line, which reads as someone who's forgotten how to build. Cursor's culture is hands-on and flat, so the pass is a player-coach who ships real code and lifts the room at the same time.
End the simulation with one question: would this team want to work with me and would they want to work for me? Sit with the answer. If your partner's feedback was “great code, hard to pair with,” that gap will end the real onsite and you have time to close it now.
QCursor's onsite working session is paid and runs alongside the real team. For an EM candidate, what is it actually testing that a take-home or whiteboard wouldn't?