In-Memory Transactional Key-Value Store
Cursor's first technical screen in 2026 is usually the Merkle tree. The second one rotates, and the transactional key-value store is one of the problems it rotates through. A software engineer who passed the second round in March 2026 described it as designing an in-memory transactional KV database. In their words it wasn't system design, more like object-oriented class design, starting from a class named something like InMemoryDB. Handling concurrency was part of it too.
Later 2026 reports line up with it. A July 2026 version stresses clear API semantics and doesn't need a full distributed design. By October 2026 candidates describe it as an alternative second coding screen with concurrency follow-ups, sharing that slot with the rate limiter. Every version runs the same way: a transactional store first, concurrency after.
CursorPremium lesson · Coding round
The Cursor problem is below.
- A Premium questionCoding · Medium
With hints, the follow-up and a tested solution.
Get the Cursor questions$49 a year · all 107 companies · instant access
20,000+ candidate reports
Cursor interview guideKnow what Cursor asks before you walk in.
9 coding · 4 system design · 16 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.