Cursor · Phone screen → Onsite
In process2025 Cursor New Grad Software Engineer Interviews: 1 Experience
Cursor interview reports
- New Grad (current): one full loop from November 2025: a chat with the hiring manager, a 60-minute hash tree round inside a repo, and a day of building a feature in Cursor's own code.
- Posted after the SpaceX acquisition announcement: seven reports from July to October 2026: six experienced candidates (five software engineers and one machine learning engineer) and one software engineer whose hiring level wasn't given.
- Role and hiring level not reported: one technical phone screen from January 2026, a two-part per-user rate limiter.
- Cursor, SpaceX and xAI new grad reports: this report alongside a Cursor research scientist screen from 2026, eleven SpaceX and two xAI new grad reports.
Cursor told the candidate it was still working out what new grad hiring should look like.
Coverage: One new grad software engineer candidate (entry level, L3) in the United States. A 45-minute hiring manager chat, one 60-minute repo-based coding round, and an 8 to 9 hour remote final round. Interviews in November 2025; the report was written in April 2026.
What came up
Only one round had a set technical problem: a hash tree, built inside a real repository. The rest was a resume and motivation chat and an open-ended feature build in part of Cursor's codebase.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Filesystem Hash Tree (in the report, "a hash tree they actually use", built inside a repo) | 1 report | Report: November 2025 (interview month); Additional FastPrep history: 2026-09-22, 2026-09-18, 2026-08-21 |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Walk me through your background and past experience | 1 report | Report: November 2025 (interview month) |
| Why Cursor, and what are your future plans? | 1 report | Report: November 2025 (interview month) |
| When do you graduate, and what are your plans around school? | 1 report | Report: November 2025 (interview month) |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Get access to part of Cursor's codebase, find something worth building, build it on your own, and present it at the end of the day | 1 report | Report: November 2025 (interview month) |
1 detailed candidate timeline
01: A hash tree in a repo, then a full day of building inside Cursor's code
Interview date: November 2025 · Report date: April 13, 2026 · Role: Software engineer, new grad (entry level, L3) · Location: United States · Process: About 5 weeks · Result: Still waiting when the report was written
Hiring manager chat (45 minutes)
- The first call was with the hiring manager, not a recruiter. The candidate said it felt unscripted and based on fit more than a checklist.
- The manager went through the candidate's resume. The candidate walked through past internships and projects, mostly the things they had built themselves and how they went about the work.
- The questions moved on to why Cursor and future plans, including when the candidate graduates and what they plan to do around school.
- The manager was open about how Cursor works: flat, fast-growing and intense, and gave the candidate a lot of advice, which made it feel as if there was no recruiter step in between. The talk drifted to topics outside Cursor too.
Repo-based coding round (60 minutes)
- The candidate implemented a hash tree that, by their account, Cursor actually uses, working inside an existing repository.
- The candidate could use Google, GPT and Cursor for targeted syntax help.
Final round (8 to 9 hours, remote)
- Cursor gave the candidate access to part of its codebase and a Slack channel, then left the task open: figure out the code, spot something worth building, and build it on their own.
- The candidate worked in that Slack channel all day and presented the feature at the end.
Looking back, the candidate found the process more like a startup's than a typical loop: loose and not always clearly defined, but a lot closer to the actual job.
Comments
0No comments yet — be the first to share what you know.