Nutanix U.S. SWE Intern Interviews: 54 Experiences (Part 1 of 3)

Shared by janebeingjane ·
Company
Nutanix
Reports
18 interview reports
Level
Internship
Stages
OA → Phone screen → Onsite

Nutanix U.S. SWE intern reports from 2024–2025 describe an OA, a recruiter call, then technical and hiring-manager rounds, often back to back.

At a glance

  • Process: an online test (HackerRank in five reports; 75 minutes and two questions in 13), a recruiter screen (30 minutes in 09), one to three technical interviews (45 minutes each in 05 and 09), then the hiring manager (30 minutes in 05 and 14). Six candidates had the later rounds in one sitting (05, 08, 11, 14, 15, 18).
  • Asked recently: most write-ups don't name the coding problem. The named ones are Top K and swapping linked-list nodes in pairs (08), an array iterator class (10) and 3Sum (16). Résumé and project talk came up in 10 of 18 reports, and "why Nutanix" in 4.
  • Difficulty: candidates who rated the coding called it LeetCode medium (04, 14, 16) or medium to hard (05, 13). Candidate 04 didn't find the process hard.
  • Practise first: Unique Triplets Summing to Zero, Swap Adjacent Linked List Nodes, Custom Array Iterator and what draws you to Nutanix.

Coverage: 54 U.S. software engineering intern reports in all. This part covers the 18 from Jan 2024 to Nov 2025: SWE and Software Engineer interns, one Summer 2025 backend intern, and one MTS2-titled role that ended in an internship offer, in San Jose (5), Durham (1), New York (1), "United States" with no city (10) and one with no place. Fourteen of the 18 ended with an offer. The other 36 reports (2016–2022) are more than three years old, so Parts 2 and 3 keep them as history, outside the counts here. Nutanix intern hiring outside the U.S. is in our broader Nutanix intern roundup, and reports with no clear hiring level are in their own roundup.

In this series

What came up

Talking about your own work is the most common thread: 10 of the 18 reports mention résumé, project or background questions, often inside a technical round. Few recent write-ups name the coding task, so the coding rows below are thin.

Topic Reports Last seen
Résumé, projects and background 10 of 18 Nov 2025 (report date)
Behavioral questions 9 of 18 Nov 2025 (report date)
Why Nutanix, or what you know about it 4 of 18 Apr 2025 (report date)
Systems concepts (OS, networking, encryption) 3 of 18 Nov 2025 (report date)
Arrays and binary search 3 of 18 Jul 2025 (report date)
Linked lists 1 of 18 Mar 2025 (report date)
Top K 1 of 18 Mar 2025 (report date)
Writing a class (an iterator) 1 of 18 Dec 2024 (report date)
Grid problem (DP or BFS) 1 of 18 Dec 2024 (report date)
Graphs (minimum spanning tree) 1 of 18 Nov 2024

One report can count toward several rows. Résumé rows: 01, 02, 05, 06, 07, 09, 10, 11, 13, 18. Behavioral rows: 01, 02, 03, 04, 11, 13, 14, 15, 16.

Questions we found

These tables cover the 18 current reports. The older tests and phone screens have their own tables in Parts 2 and 3.

Algorithms / Data Structures

Question Reports Last seen
"Top K elements": Top K Most Frequent Values 1: 08 Mar 2025 (report date)
LeetCode 24, Swap Adjacent Linked List Nodes 1: 08 Mar 2025 (report date)
Custom Array Iterator 1: 10 Dec 2024 (report date)
LeetCode 15, 3Sum: Unique Triplets Summing to Zero 1: 16 Sep 2024 (report date)

Behavioral (BQ)

Question Reports Last seen
What draws you to this position, or to Nutanix? 3: 06, 09, 18 Apr 2025 (report date)
Your working style (14 adds conflict) 2: 13, 14 Nov 2024 (report date)
What is the hardest technical project you have worked on? 1: 01 Nov 2025 (report date)
A past project and how it connects to this role 1: 05 May 2025 (report date)
One résumé experience and the choices behind it (practice) 1: 07 Mar 2025 (report date)
What have you learned about Nutanix? 1: 13 Nov 2024
What stood out about Nutanix's technology? 1: 13 Nov 2024
Teach me something I don't already know 1: 15 Oct 2024 (report date)
What kind of project would you like to work on? 1: 16 Sep 2024 (report date)

CS fundamentals

Question Reports Last seen
Encryption and decryption, one-way versus two-way 1: 02 Nov 2025 (report date)

Candidate 14 also had a run of low-level operating systems and networking questions, and candidate 11 a long talk on systems concepts; neither listed the exact questions.

18 candidate timelines from 2024–2025

01: A patient coding interviewer, then a hiring manager who dug into the résumé

Report date: Nov 18, 2025 · Role: Software Intern · Location: United States · Result: Offer

Technical interview

  1. One coding problem, not named. The interviewer was friendly and walked the candidate through it. The candidate's sense was that the interviewer wanted to see how they broke the problem into small parts and fit those parts back together.

Hiring manager interview

  1. Mostly behavioral, with detailed résumé questions, how the candidate would approach some problems, and how well they knew some concepts. None of these were spelled out.
  2. What is the hardest technical project you have worked on?

02: LeetCode-style problems, then a senior engineer and encryption

Report date: Nov 14, 2025 · Role: Software Engineer Intern · Location: United States · Result: Offer

Technical interview

  1. A short talk about background, then LeetCode-style problems that weren't named.

Final round with a senior engineer

  1. Behavioral, going further into the résumé.

The write-up also mentions, without placing it in a round, a detailed discussion of encryption and decryption, including one-way and two-way schemes.


03: Around five rounds across several teams, then a slow rejection

Report date: Aug 30, 2025 · Role: SWE Intern · Location: United States · Result: No offer

  1. About five interviews in total, with different teams. The first was standard behavioral questions, none of them listed.
  2. Two final rounds, which the candidate felt went well.
  3. Several weeks later, a rejection.

The candidate was unhappy with how long the process dragged on.


04: Two medium problems in a single technical interview

Report date: Jul 9, 2025 · Role: Software Engineering Intern · Location: San Jose, CA · Result: Offer

  1. Online assessment: no details.
  2. Technical interview: two medium LeetCode-style problems. One called for binary search over an array; the exact task wasn't given. The other wasn't described.
  3. Hiring manager: a behavioral interview.

The candidate didn't find the process hard and was happy with how they were kept informed.


05: A San Jose superday that opened with a project tied to the role

Report date: May 1, 2025 · Role: Software Engineer Intern · Location: San Jose, CA · Result: Offer

Superday, three interviews

  1. 30 minutes with the hiring manager, about a project the candidate had built and how that project connects to this role.
  2. Then two technical interviews of 45 minutes each. Four coding problems came up across the day, rated medium to hard, none of them named.

A second San Jose write-up with the same date and the same 30/45/45-minute shape calls the first interviewer the hiring lead, says every round mixed coding with résumé questions, and mentions a question about one résumé project. We count the two write-ups as one experience.


06: HackerRank, one technical round, and a short interest check

Report date: Apr 1, 2025 · Role: SWE Intern · Location: United States · Result: Offer

  1. HackerRank assessment.
  2. Technical interview: some background first, then technical questions that weren't described.
  3. Hiring manager: brief and relaxed, with little technical or behavioral depth. It mostly checked whether the candidate was interested, including why they wanted this position.

07: A whiteboard round with an engineer, then coding with the hiring manager

Report date: Mar 28, 2025 · Role: SWE Intern · Location: San Jose, CA · Result: Offer

  1. Recruiter call: background and past work.
  2. An engineer's technical round: whiteboarding plus more about background.
  3. Hiring manager: coding, then a close look at the résumé. One question asked the candidate to walk through a specific experience on the résumé and explain the decisions behind it.

The candidate called the whole process smooth, with friendly interviewers and an HR contact who answered questions quickly.


08: Top K and pairwise node swaps in a three-hour block

Report date: Mar 1, 2025 · Role: Software Engineer (Internship) · Location: San Jose, CA · Result: No offer

  1. HackerRank assessment, which had to be done before any recruiter call.
  2. Recruiter screen.
  3. About three hours of technical interviews in a row, and after them the hiring manager.

Somewhere in that process came two coding questions:

  1. "Top K elements", with no ranking rule given. Our closest practice version ranks values by how often they appear: Top K Most Frequent Values.
  2. Swap the nodes of a linked list two at a time (Swap Adjacent Linked List Nodes).

The whole process took about three weeks.


09: A recruiter screen, then two technical rounds with one coding question apiece

Report date: Mar 1, 2025 · Role: Software Engineering Intern · Location: United States · Result: Offer

  1. Recruiter screen, 30 minutes.
  2. Two technical interviews, 45 minutes each, with one LeetCode-style question apiece (not named). Most of the time went to background, projects, and past work.

At some point the candidate was asked why this particular role at Nutanix, with the answer expected to draw on their background and what they had read about the company.


10: An ML résumé check, then 45 minutes on an iterator class

Report date: Dec 30, 2024 · Role: SWE Intern · Location: San Jose, CA · Result: No offer

  1. Phone screen, 15 minutes.
  2. Technical interview, one hour. The first quarter hour went to the ML work on the candidate's résumé. The remaining 45 minutes went to writing a class that walks through an array item by item; the methods it had to support weren't reported. Our practice version picks a set of operations: Custom Array Iterator.

11: Coding, systems concepts, and a hiring manager, back to back

Report date: Dec 1, 2024 · Role: SWE Intern · Location: United States · Result: Offer

  1. Recruiter call.
  2. Three interviews in a row:
    • A technical interview with coding only.
    • A technical interview that started with a long discussion of systems concepts and ended with a short coding task.
    • The hiring manager: the candidate's technical past, some behavioral questions, and what the team does.

The only coding question the candidate described was a grid problem that they say works with either dynamic programming or BFS. Its exact task and round weren't given.


12: An MTS2 title, but an internship offer with no formal interviews

Report date: Nov 22, 2024 · Role: Software Engineer MTS2 (the write-up describes an internship offer) · Location: United States · Result: Offer

  1. Informal conversations with the manager instead of formal interviews.
  2. A recruiter call about pay and location, including whether the candidate was open to relocating.
  3. Within a week or two of that first manager chat, the offer was talked through and signed.

13: Summer 2025 backend intern in Durham: a full-score OA and two interested teams

Interview date: Oct–Nov 2024 (posted Nov 12, 2024) · Role: SWE Intern, Summer 2025 (backend) · Location: Durham, NC · Result: Offer

The candidate, an undergraduate, applied in early October, and a recruiter reached out on October 18.

Online assessment (HackerRank, 75 minutes)

  1. Two questions, one medium and one hard. Neither prompt was described: the candidate couldn't recall the medium one, and solved the hard one with Kruskal's algorithm, finishing with a full score.
  2. There was no camera, but the test tracked switching tabs.

Recruiter phone screen

  1. What have you learned about Nutanix?
  2. What stood out to you about Nutanix's technology or how it operates?
  3. Résumé, working style, and personality.

Team interviews

  1. The recruiter matched the candidate with teams. Two teams were interested, and one made the offer. These interviews weren't described.

14: A superday with low-level OS and networking questions

Report date: Nov 1, 2024 · Role: Software Engineer (Internship) · Location: United States · Result: Offer

  1. HackerRank assessment.
  2. Recruiter phone screen.
  3. Superday: two technical interviews plus 30 minutes with the hiring manager. Across them came one LeetCode-style medium question, a run of low-level operating systems and networking questions, and behavioral prompts on how the candidate likes to work and handles conflict.

The candidate's note was that the questions depend on the team. They found the recruiter unusually supportive.


15: A late interviewer and a "teach me" round

Report date: Oct 29, 2024 · Role: SWE Intern · Location: United States · Result: No offer

Final round, two interviews back to back

  1. Technical: basic coding on an array question the candidate didn't describe further. The interviewer joined far behind schedule.
  2. Senior hiring manager: the candidate had to teach him something he didn't already know.

The candidate came away very unhappy. They described the manager as condescending and said some of his comments were sexist.


16: 3Sum and a relaxed manager

Report date: Sep 1, 2024 · Role: Software Engineering Intern · Location: United States · Result: Offer

  1. Online assessment.
  2. A second assessment step, an "LC" assessment tied to the OA, which the write-up expands as "lights camera" without explaining further, followed by a manager conversation mixing behavioral and technical questions.
  3. The manager was easygoing and asked what kind of project the candidate wanted to work on.

The candidate also lists 3Sum (Unique Triplets Summing to Zero), rated medium, among the questions, without saying which round it came in. They said the recruiter was open with them throughout.


17: A spring 2024 search: three video rounds over a month

Interview dates: Mar 14–Apr 24, 2024 · Role: SWE Intern · Location: Not stated · Result: Offer

Through 2023 the author held a part-time startup job alongside school, missed most of fall recruiting, and began applying widely in 2024.

  1. Mar 1: applied through RippleMatch, where recruiters see the résumé directly.
  2. Mar 12: a recruiter set up the online test, taken on HackerRank on Mar 14.
  3. Mar 19: recruiter call.
  4. Mar 22, Apr 2, and Apr 23: three video interviews.
  5. Apr 24: hiring manager call. Apr 25: offer.

No questions were listed. The recruiter helped the author choose teams and get ready for the interviews. In the author's view, Nutanix does most of its intern hiring in October and November, and some openings may be filled later, between January and March.


18: Two senior staff interviewers from different offices

Report date: Jan 1, 2024 · Role: Software Engineer Intern · Location: New York, NY · Result: Offer

  1. Résumé screen, then an online assessment.
  2. Recruiter interview, short.
  3. Two technical interviews back to back, each with a Senior Staff member; the two were based in different offices.

Questions: algorithm problems that weren't named, standard questions about the candidate, and why Nutanix.


Patterns across the reports

  1. Later rounds in one sitting. Six of the 18 had them together: a superday in 05 and 14, and back-to-back interviews in 08, 11, 15 and 18. Where lengths were given, the technical interviews ran 45 minutes (05, 09) and the hiring manager 30 minutes (05, 14).
  2. Background inside the technical rounds. Six candidates say a technical interview opened with or spent much of its time on their background: 02, 06, 07, 09, 10 (a quarter hour on ML work before the coding) and 05 (résumé questions in every round).
  3. A hiring-manager round in most loops. Twelve reports include one (01, 04–08, 11, 12, 14–17), and its content varied a lot (see the hiring-manager question below). Candidate 14 noted that the questions depend on the team.

Common questions

How long is the Nutanix SWE intern OA?

Only report 13 describes a recent test in detail: HackerRank, 75 minutes, two questions (one medium, one hard), no camera, with tab switches tracked. The older tests in Part 2 had two questions in 90 minutes.

How many interview rounds does Nutanix have after the OA?

The usual shape was a recruiter screen, one to three technical interviews and a hiring-manager round; reports 08, 11 and 14 list all of these, and 05 and 09 had two 45-minute technical interviews. Candidate 17 had three video interviews before the manager, candidate 03 about five, and candidate 12 only informal manager chats.

Is the Nutanix hiring manager round technical?

It depends on the manager. Some were behavioral (04) or a brief check of interest (06); others mixed in coding (07), technical background (11) or a "teach me something" task (15).

How long does it take to hear back from Nutanix?

Candidate 08's whole process took about three weeks, and candidate 12 had an offer within one or two weeks of the first manager chat. Candidate 17 went from the OA on Mar 14 to an offer on Apr 25, one day after the manager call. Candidate 03 waited several weeks after the final rounds for a rejection.

Does Nutanix ask operating systems questions?

Some teams do. Candidate 14 had low-level OS and networking questions, and candidate 11 a long talk on systems concepts. Older reports in Part 3 go deeper, into mutexes, virtual memory and fixing a producer-consumer buffer.

What to practise

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesNutanix SWE Intern OA Questions: 16 Experiences (Part 2 of 3)
0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.