Design a File Dependency Graph Service
Three candidates have described this prompt first-hand, and none of them in the last twelve months, so read each account with its year attached. In 2019 a Cloud Engineer candidate in Romania got a 4-hour take-home with a check-in call after each requirement. The task was a REST API for file metadata and file dependencies, with Redis mandatory as the database. It needed CRUD plus three query calls, one of them a BFS or DFS variation. In 2021 a Cloud Engineer loop in Bucharest gave about six hours to design and build a working API that builds a dependency graph from input files named by their hashes. In 2024 a Senior Software Engineer loop in Pune framed it around one call. Hand it a file ID and it parses the file and pulls out the IDs it references. Then it checks which of those are on disk and returns them. That candidate could take two working days at home and then discuss it for an hour or two, or do it in person over five to six hours.
So this isn't a pure whiteboard round. You write a small program that runs, and then the conversation grows it. The Pune follow-ups were about scaling the solution to a global level and how you'd deploy it. Plan for both halves. A clean core you can demo earns you trust early, and the design talk afterwards is where you show depth.
CrowdStrikePremium lesson · System design round
The CrowdStrike design, worked end to end.
- Requirements and scopeSystem design
- The API and data model
- The design, drawn out1 diagram
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports · guide updated
CrowdStrike interview guideKnow what CrowdStrike asks before you walk in.
28 coding · 4 system design · 15 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.