Design a Parts Inventory System
An inventory system answers one question all day: where a part is, and how many there are. A technician at a bench scans a valve out of a bin. In another building, a planner wants to know whether there are enough of those valves across every site to finish next week's builds. A quality engineer wants every vehicle that got a part from a supplier lot that just failed inspection. All three questions run against the same records. The prompt tends to arrive as a single line, something like "how would you design the database for a parts supply chain?", with almost nothing else. The product looks like a plain forms-over-a-database app. Correctness is what makes it hard. Stock can't go negative, a serialized part can't be in two places, and no movement can quietly disappear. Those rules have to hold while hundreds of people scan at once, at sites in different states.
SpaceXPremium lesson · System design round
The SpaceX design, worked end to end.
- The API and data modelSystem design · Frequently asked
- The design, drawn out2 diagrams
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports · guide updated
SpaceX interview guideKnow what SpaceX asks before you walk in.
20 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.