Cursor interview, decoded.

The CEO and the head of talent have described the shape on record, and the two 2026 guides agree on the details below. Published accounts date from before and after the acquisition, so expect drift in names and timing rather than in the trial itself.

Cursor publishes no values list; its founders and its head of talent have said what the trial is for.

• Can you go end to end in a codebase you have never seen: the trial's first question, in the CEO's words
• What would you build if left alone: the second
• Genuine use of the product, checked at the screen
• Bottom-up experimentation and independent team-building, which Truell says the company prioritises
• Programming skill without AI assistance, tested deliberately

The reported problems are the product's own internals; the trial's question is the one the CEO has stated publicly.

The trial is the decision round, and it is described on record: every engineer and designer does it, it runs up to two days on site, and the material is a frozen snapshot of the real codebase. Its intent is stated too, which is the useful part; you are not guessing what is graded. Here is what the two days ask and how the people who clear them use the time.

• Day one, first two hours: read before you build: Orient in the snapshot: how a feature is wired from the editor surface to the model call, where tests live, how the team runs things locally. Ask the engineers around you; the trial is with the team, and how you ask is observed. Candidates who start coding in the first half hour report building the wrong thing well.
• Scope something you can finish: The task is yours to pick, and Truell's framing is what you would build if left alone. Choose a real, small improvement to the product you use: something you have wanted as a user, reachable in a day and a half, with a demo at the end. Ambition is read from the choice, completion from the demo.
• Build with the team's tools, tested: The trial uses the tools engineers use day to day; the AI ban is for the screens. Write it the way the codebase is written, with the tests the codebase expects, in small commits you can walk through. The review at the end goes line by line, so every line needs a reason.
• The demo and the review: Show it working in the product first, then the design, then what you would do next. Expect the review to press on choices; defend them or concede them cleanly. A candidate who says which part is a hack and why scores better than one who hides it.
• Meals and conversations count: The trial is a cultural interview both ways, in the CEO's words. Ask what the team is working on, what the product should do next, how decisions get made without product managers. Truell has said the two days exist to find people who care about the problem; that shows in the conversations more than in the code.
• Ask about terms before you go: Public accounts differ on whether the trial is paid and how IP is handled. Ask the recruiter directly, in writing, what compensation and IP assignment apply to the two days, before you fly.

Prepare by doing the trial to yourself: pick an open-source editor or a large TypeScript codebase you have never read, give yourself a day, and ship a small feature with tests and a demo. Then practise the screens without AI: a text buffer, a diff, a Merkle tree over a directory, streaming output into a buffer, each in under an hour.

Levels.fyi medians for Cursor software engineers, updated 17 September 2026 and read on 22 September, from a small sample that skews senior; reported packages run from under $200K to well over $1 million, most of it equity. Since 14 August 2026 that equity is SpaceX stock through the acquisition; ask what the grant converts to, on what schedule, and how the SpaceX listing affects liquidity. Third-party figures of $808K to $1.28 million are consistent with the Levels.fyi range.

1. 01Use the product for real before applying, and have opinions about it. The first screen checks this, and the trial's open task rewards it.
2. 02Practise the screens without AI assistance: a text buffer with insert, delete and line lookup; a file-tree diff; a Merkle tree over a directory; streaming output applied to a buffer. Under an hour each.
3. 03Run a self-trial: a codebase you have never read, one day, a small feature with tests and a demo.
4. 04Prepare your answer to the stated question: two days in the codebase and no assigned task. Have two candidate features in mind, one safe and one ambitious.
5. 05Be ready to explain why long context does not replace retrieval, and how you would evaluate a code-editing model offline and online.
6. 06Ask about trial pay and IP in writing before the onsite.

This guide covers Cursor's engineering and design loop, which is the same for both and distinct from the Grok loop described in the xAI guide, though both now sit in SpaceX's SpaceXAI division. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

• 01Business Insider (via AOL), inside Cursor's hiring strategy: no AI in interviews and a two-day project with the team (12 June 2025)Truell on banning AI tools beyond autocomplete in technical screeners and why (a time-boxed test of skill; fairness to strong programmers without AI experience), the two-day project on real work with team meals and a demonstration at the end, and the passion test.
• 02a16z, Cursor hires every engineer and designer through a two-day onsiteTruell on the a16z podcast: the trial tests whether they can go end to end in the codebase and what they would build if left in a vacuum.
• 03Business Insider (via Yahoo), Cursor courted top engineers by flying across the worldTruell on the a16z podcast on the recruiting of the first ten hires, and the two-day onsite as a cultural interview in both directions.
• 04Business Insider (via DNyuz), Cursor's head of talent on work trials (11 August 2026)Adam Ward, head of talent: the trials are expensive and worth it, and most companies get the onsite wrong by making it about getting something out of the candidate.
• 05Aced (Exponent), Cursor software engineer interview guidethree to five rounds, the hour-long technical rounds on applied AI systems and editor primitives (a syntax-aware edit, streaming model output, a file-tree diff, a context retrieval system), and the trial's frozen snapshot.
• 06TechInterview, Cursor interview guide 2026the onsite work trial of up to two days on a frozen snapshot of the codebase with the team's tools, and the review where every line is defended.
• 07AI Engineer Interview Questions, Cursor / Anysphere (reviewed July 2026)a compilation of the reported problem shapes (tab prediction under 100ms, indexing a 100k-file monorepo, multi-file edits while typing, the text buffer, the Merkle tree, evaluation, the agent harness, the inference-cost model) and the note that trial pay and IP terms are disputed in public accounts.
• 08Levels.fyi, Cursor software engineerthe US and Bay Area medians, updated 17 September 2026, read 22 September 2026.
• 09Yahoo Finance, SpaceX completes the Cursor acquisitionthe all-stock deal closing on 14 August 2026 into the SpaceXAI division.

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.