Cursor (Anysphere)¶
English · Русский · AI Interview Atlas › Companies
AI-native products · International · Loop reviewed 2026-09-29
One new-graduate candidate describes rounds held in real code: a data structure from the product implemented in a cloned repository with limited AI help, and a long remote onsite shipping a self-chosen feature.
On this page: Interview loop · Questions (2)
Roles covered¶
- AI Engineering: Software engineer on AI products
Interview loop¶
| Stage | What happens | Basis |
|---|---|---|
| Technical round in the product's code Software engineer on AI products |
Implement a hash tree the product actually uses inside a cloned repository; search, ChatGPT and Cursor were allowed for targeted syntax help, announced to the interviewer before use. | 🗣 candidate report Cursor Software Engineer (New Grad) Interview Experience, Aced (formerly Exponent), candidate report, retrieved 2026-09-29 |
| Remote onsite build Software engineer on AI products |
Eight to nine hours with access to the codebase: decide what to build, build it, then explain why it was implemented that way and what the trade-offs are. | 🗣 candidate report Cursor Software Engineer (New Grad) Interview Experience, Aced (formerly Exponent), candidate report, retrieved 2026-09-29 |
Coding: required (Cursor Software Engineer (New Grad) Interview Experience, Aced (formerly Exponent), candidate report, retrieved 2026-09-29)
Questions reported for Cursor (Anysphere)¶
Practical coding¶
- Inside a clone of the product's repository, implement a data structure the product actually uses, asking for AI help only on targeted syntax questions.
- Coding · Asked at: Cursor (Anysphere) 🗣 · ✍ Answer
- Tests: Whether you can read an unfamiliar real codebase and implement a core structure correctly.
- A strong answer covers:
- Locate callers, required operations, operation frequency and tests; derive the representation from that contract.
- State invariants and time/memory costs, then challenge the choice with duplicate, empty and changed-constraint examples.
- Follow repository conventions and verify behaviour at callers; keep AI help to the targeted syntax questions permitted by this reported session.
- Read: Working Inside Existing Systems (Palantir Careers) · collections: OrderedDict objects (Python Software Foundation) · Algorithms, fourth edition: Directed Graphs (Robert Sedgewick and Kevin Wayne, Princeton University)
- Given a real codebase for a working day, decide what to build, ship it, and explain your implementation choices and trade-offs.
- Applied scenario · Asked at: Cursor (Anysphere) 🗣
- Tests: Whether you scope your own work, deliver it and defend it without step-by-step direction.
- A strong answer covers:
- Explore the codebase first, then pick a change that is useful and finishable within the day.
- Ship a working core early, then iterate, keeping a running note of decisions and trade-offs.
- Close with a demonstration, naming its tests and limits and what you would build next.
- Read: Working Inside Existing Systems (Palantir Careers)
← Cognition · Perplexity →