Nutanix system design interview
Design rounds lean towards infrastructure and storage: backup services, file systems, telemetry search and ETL at scale. Teams also ask realistic data-structure designs such as caches and key-value stores, sometimes in a low-level, interactive style.
| Progress | Question as candidates report it | Next step |
|---|---|---|
| Search and delete APIs over sorted per-cluster telemetry filesMonitoring and alerting | Watch | |
| Design a key-value storeKey-value store | Watch | |
| Design a database backup serviceWalkthrough being added | Coming soon | |
| Scalable fault-tolerant ETL pipeline for petabyte dataWalkthrough being added | Coming soon | |
| Design a log storage and query systemWalkthrough being added | Coming soon | |
| Trading app portfolio page with live pricesWalkthrough being added | Coming soon |
Which levels get a design round
How to answer any design question: the LADDER method · How the design round is scored by level
Questions people ask
When does Nutanix ask system design?
A design round is part of the loop at SDE 2 (MTS-2), Senior Software Engineer (SDE 3) (MTS-3 / MTS-4), Staff Software Engineer (Senior MTS / Staff Engineer). Design rounds lean towards infrastructure and storage: backup services, file systems, telemetry search and ETL at scale. Teams also ask realistic data-structure designs such as caches and key-value stores, sometimes in a low-level, interactive style.
What system design questions does Nutanix ask?
Search and delete APIs over sorted per-cluster telemetry files; Design a key-value store; Design a database backup service; Scalable fault-tolerant ETL pipeline for petabyte data; Design a log storage and query system; Trading app portfolio page with live prices.