Katkat

Company

Cursor interview questions

11 practice questions in the style of Cursor's interviews, covering Software Engineering Fundamentals, Behavioral & Leadership, System Design, Coding & Algorithms.

Questions11

0 easy9 medium2 hard

Your progress0/11

Cursor interview questions by the numbers

Last updated

Katkat has 11 Cursor interview questions. The largest topics are Software Engineering Fundamentals (55%), System Design (27%) and Behavioral & Leadership (9%). By difficulty: 82% medium and 18% hard. The most common round is Technical Screen (100%). Frequent concepts include Algorithms, Hashing, Merkle Tree and algorithms.

Difficulty

  • Medium82% · 9
  • Hard18% · 2

Interview rounds

  • Technical Screen100% · 11

Roles

  • Software Engineer91% · 10
  • Backend Engineer9% · 1

Frequent concepts

  • Algorithms18% · 2
  • Hashing18% · 2
  • Merkle Tree18% · 2
  • algorithms9% · 1
  • Conflict Resolution9% · 1
  • cryptography9% · 1

Showing 1–11 of 11 results

  • Implement a Merkle tree over a real directory in Python, with N-ary directory nodes, a build method, a hash lookup by path, and a diff that compares two trees, and write the tests yourself. It tests deterministic hashing design, file-system traversal, pruning identical subtrees, and disciplined testing under time pressure.

    CursorSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests streaming string processing, finite state machine design, and edge-case handling for incrementally received Markdown code fences.

    CursorSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Connect a technical project deep dive with engineering career decisions, using clear ownership, interface trade-offs, validation, and lessons learned.

    CursorSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates expertise in designing distributed rate-limiting systems with hierarchical quotas, focusing on concurrency control, exact rolling-window counting, and correctness under concurrent stateless servers; it belongs to the System Design domain and tests practical application of distributed systems, storage, and API design as well as conceptual understanding of atomicity and consistency. It is commonly asked to assess reasoning about atomic decision-making across multiple scopes, scalability and partitioning strategies, handling reconfiguration and operational concerns, and the trade-offs between correctness and system performance (English).

    CursorBackend EngineerSystem DesignTechnical Screen
  • Design a distributed, hierarchical configuration management service for an IDE that synchronizes versioned settings across individual users, multiple teams, and workspaces while supporting offline modifications and deterministic conflict resolution.

    CursorSoftware EngineerSystem DesignTechnical Screen
  • Design a cron scheduler with durable occurrences, timezone rules, missed-run policies, worker leases, idempotent dispatch, and failure recovery.

    CursorSoftware EngineerSystem DesignTechnical Screen
  • Hash a repository with canonical Merkle nodes, compare changed subtrees, report file changes, and account for symlinks, cached hashes, and snapshot limits.

    CursorSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement an incremental, deterministic Merkle tree for a virtual repository file system with stable serialization, child ordering, and ancestor cache invalidation.

    CursorSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement a Merkle tree to model repository file systems and efficiently compute differences between two repository states using subtree hashes.

    CursorSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's understanding of Merkle trees, filesystem-aware hashing, directory traversal, and diff algorithms for detecting file-level changes.

    CursorSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Tests understanding of cryptographic hash trees (Merkle trees), including tree construction, odd-node handling, proof generation, and verification.

    CursorSoftware EngineerSoftware Engineering FundamentalsTechnical Screen

Cursor interview experiences

All 2 →
  • 60-Minute Merkle Tree Phone Screen, Finished Everything and Still RejectedCursor · Software Engineer · Technical Screen · Sep 2026
    Rejected

    Around the start of September I did a 60-minute phone screen with Cursor. After Cursor merged with SpaceX AI it got renamed to SpaceX AI. The problem was writing a Merkle tree. You have to build a Merkle tree to represent a file system, write get_hash, and write diff to compare 2 trees. You have to write all the tests yourself. The logic is the same as a Merkle tree, except a node can have N chil…

  • A Merkle Tree Diff Problem Run Inside a Real RepoCursor · Software Engineer · Technical Screen · Feb 2026
    In progress

    Just finished the interview, don't know the result yet, but I feel like I answered pretty mediocre. It really was the question that's already posted here — Merkle Tree — but the details still mattered a lot. It runs inside an actual repo, so you have to read files from the repo, which means you need to be familiar with the relevant standard library. The interviewer wanted the folder structure to…

More companies