Nutanix Interview Experience for MTS-1 with 1.5 Years Experience
Interview Experience
I am a 2024 passout and recently appeared for interviews in Nutanix for their MTS-1 Role. Background - SDE I at US Core Bank (Recently switched from an US Investment Bank) YoE - 1.5 Years I applied vi
Full Details
I am a 2024 passout and recently appeared for interviews in Nutanix for their MTS-1 Role. Background - SDE I at US Core Bank (Recently switched from an US Investment Bank) YoE - 1.5 Years I applied via referral and got call from recruiter after few weeks. I was serving notice period at the Investment Bank, and was about to join the Core Bank.
Round 1 There were 2 hard but standard questions on graphs. Alien Dictionary Word Ladder II It went smooth, interviewer was friendly. Got a call from the recruiter to schedule
next round the next day.
Round 2 It was a problem solving and debugging round. I had to clone an open source database driver codebase from GitHub. Then, the interviewer asked me to explain where different features are implemented in the code - the code block or the line. He started with specific database configurations like pools, connection logic. Then I had to clone the database codebase itself. The interviewer asked where indexing is implemented. Then I had to show where the actual execution logic was implemented. I was appearing for such type of round for the first time. I had prior open-source experience, so that helped. Few days later, I got a call from the recruiter that they have chosen someone internally. (I got another call after 2 weeks that there is one more opening, and I was the foremost in interview queue so they wanted to schedule next rounds. But I had joined the core bank by then. Still I appeared for the interview.)
Round 3 It was an HLD round. The interviewer was friendly and asked to design a Chat Application. I presented my approach, we discussed on the tradeoffs and it went well. Got a call the same day to schedule
next round.
Round 4 It was HM round. He asked some technical questions around Kafka and messaging systems. Then there was some discussion around the job role and day-to-day activities. We discussed on my open source experience, and my interests in core technologies. It was perhaps my favourite round. Got final result after a few days.
Result Selected
About This Question
This is a candidate experience report from a nutanix interview for a swe role reported in 2025.
It covers the following topics: Hash Table, Graph, Sql, System Design, Queue, Stack .
Difficulty rating: Hard
Topics
More Nutanix Interview Questions
About Nutanix Interview Reports
This question was reported by a candidate who interviewed at Nutanix. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Nutanix are the higher-signal extractions to take from this report.
For broader preparation context, the Nutanix interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Nutanix reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Nutanix Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Nutanix reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.