The Debugging Round

Most coding rounds ask you to write code from a blank editor. The Nutanix debugging round inverts that. You are handed code that already exists and already misbehaves, and the job is to make it correct. It takes three shapes. The first is buggy pseudo-code in Java or C++, often something small like a palindrome linked-list check, seeded with several logical errors you must find and dry-run. The second is a multi-page client-server program you have to make thread-safe, with side questions on malloc, semaphores, and mutex versus spinlock. The hardest hands you a real open-source codebase, a database driver and then the database itself, and asks you to clone it, build it, and explain where a feature lives. This lesson teaches the method those three share, then works two bugs you fix by returning a correct function.

The Nutanix angle

This round grades how you behave in unfamiliar code, so it needs a different kind of preparation. Nutanix maintains a large distributed storage system. The daily job is reading code someone else wrote, forming a hypothesis about why it fails, and confirming it by reasoning instead of guessing. The debugging round is that job compressed into an hour. It appears across the MTS-2, MTS-3, and MTS-4 loops. Candidates who narrate a disciplined search through unfamiliar code pass even when they don't fix everything, because the interviewer watches the method more than the finish line. So practice the search itself: read code you did not write, trace data flow, and say what you expect before you check.