GeeksforGeeks Question · Aug 2023

Nutanix Interview Expereince

Question Details

I got to know about the hiring from the LinkedIn job section and asked for a referral from one of the Adobe employees. I received a call from HR and got the first intervie...

Full Details

I got to know about the hiring from the LinkedIn job section and asked for a referral from one of the Adobe employees. I received a call from HR and got the first interview scheduled.

Round 1 The first round was a technical round. The interviewer asked me 2 coding questions mainly on SLIDING WINDOW & BINARY SEARCH. First, I explained the approach, did a dry run, and then coded the same.

Round 2 The second round was a technical round. I was asked to code one question with a few modifications and a follow-up ques on BFS.

Round 3 The third round was again a technical round. I was asked to code a problem on Linked List and along with that few questions were asked on System Design. At last, HRM round.

Free preview — 6 questions shown. Unlock all Nutanix questions →

About This Question

This is a reported interview question from a nutanix interview for a swe role during the phone screen round reported in 2023.

It covers the following topics: Two Pointers, Linked List, Sliding Window, Binary Search, Graph, Graphs, System Design .

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.