System Reliability Engineer applicants have rated the interview process at Nutanix with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 95% positive. To compare, the company-average is 82.5% positive. This is according to Glassdoor user ratings.
Candidates applying for System Reliability Engineer roles take an average of 26 days to get hired, when considering 130 user submitted interviews for this role. To compare, the hiring process at Nutanix overall takes an average of 30 days.
Common stages of the interview process at Nutanix as a System Reliability Engineer according to 130 Glassdoor interviews include:
Phone interview: 20%
Group panel interview: 17%
One on one interview: 16%
Presentation: 13%
Drug test: 11%
Skills test: 6%
Background check: 6%
IQ intelligence test: 5%
Personality test: 3%
Other: 2%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Nutanix (Amsterdam) in Mar 2021
Interview
The interview process was pretty straight forward and very well outlined by the initial interviewer.
He was very friendly and did everything to make me feel relaxed. Not sure if I can give his name so, thank you very much M.D. for the help.
He kept me in the loop with all the updates, informed me on what are the steps and sessions that I have to go through and also did a small technical interview.
After this, I was scheduled for a more in-depth technical interview with a Senior Engineer, who checked how far my knowledge goes and if I'd be a good fit for the team. Here I had some basic linux questions, storage and a bit of network and virtualization.
After this step, I was scheduled for a 2 and a half hour interview with both Management and other 3 Senior Technical Engineers. The Management part will check for the softskills that you have, if you can fit in the team from a cultural point of view.
The technical part took all the 4 main areas and went deeper with tech skill assessment, going for a mock ticket approach, where I would be given a ticket example and go from there with the steps I would take to check, analyze and solve a certain technical issue.
Interview questions [1]
Question 1
What would you do/check if a customer told you he cannot write anything in a certain filesystem?
First round: OA (core CS concepts: OS, Computer Networks and Aptitude)
Technical Round 1: Questions on Resume, Scenario based questions
Technical Round 2: Weaknesses from Technical Round 1
HR Round: Company fit and culture questions
Interview questions [1]
Question 1
Explain the CPU scheduling algorithms and the important parameters to decide the most efficient algorithms
They wanted in-depth theory knowledge on virtualization concepts, Linux Commands, Operating System Concepts, Networking Concepts, etc. since their role also aligned with that. SREs will be in constant touch with clients troubleshooting issues, which require these theory fundamentals right.
Interview questions [1]
Question 1
They asked about OS (Zombie/orphan processes), Networks (VLAN), virtualization concepts, linux commands, etc
Firstly, there was a test conducted on Hackerrank for all the applicants, which consisted of questions from Computer Networks, Operating System, and some aptitude questions and around 50 of us were shortlisted for the interview round.
In the interview, I was asked in-depth questions about CN, OS and Cloud. Also, there was a thorough review of my resume and my projects that I had mentioned in there
Interview questions [1]
Question 1
I was asked about my Cloud Certification course in detail