Design Undo-Delete for Postman Collections
Candidates reported this prompt from 2024 loops in India, for SE1 and SE2 roles. Two called it the bar-raiser round, and one of those said it was asked as low-level design. A third met it as the high-level design round, worded as a delete feature with a restore option. The reported follow-ups were the deleted-collections view, a TTL (time to live) on the undo so a delete eventually becomes permanent, how the implementation scales, and open-ended trade-off questions. It looks small. Hiding a row and showing it again is a five-minute feature. The hour goes on everything around that row. A collection is a tree of folders, requests and saved examples, sometimes thousands of them, and teammates may have it open while it disappears. The restore has to bring back exactly what was there. The purge has to finish even when the server running it crashes halfway.
PostmanPremium lesson · System design round
The Postman design, worked end to end.
- Requirements and scopeSystem design · Frequently asked
- The API and data model
- The design, drawn out1 diagram
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
106 Postman interview reports · guide updated
Postman interview guideKnow what Postman asks before you walk in.
10 coding · 4 system design · 27 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.