Skip to content

Latest commit

 

History

History
56 lines (44 loc) · 3.42 KB

README.md

File metadata and controls

56 lines (44 loc) · 3.42 KB
title created modified
Nutanix Interview
2021-06-21T10:27:01.217Z
2021-06-26T01:38:02.025Z

Nutanix Interview

  • IPv4 : 20 B Header; 32b address
  • IPv6 : 40 B Header; 128b address
  • segment size: 4000 B
  • Private Addresses:
  1. 10.0.0.0 - 10.255.255.255
  2. 172.16.0.0 - 172.31.255.255
  3. 192.168.0.0 - 192.168.255.255
  • TCP Header size: 20 B
  • UDP Header Size: 8 B

Questions asked in Round 1:

It was a MCQ based round where 60 questions were asked and time duration of test was 60 minutes. It was conducted on hacerrank and live proctoring was being done from the zoom breakout groups. Some of the questions were:

Questions asked in Round 2:

  1. Tell me about yourself.
  2. What is DHCP?
  3. DNS?
  4. If an ip address couldn't be pinged on a system, how would you correct it?
  5. If a website is unreachable, what measures to take to check it?
  6. Command for listing out running processes in linux.
  7. What are hypervisors and explain their types?

My Experience: Suddenly, there was a power cut before the start of interview 3:30PM. I became a little nervous, and started telling answers quickly. Interview thought that I knew everything. I was so fast in speaking that my words weren't pronounced correctly. The interviewer was from Bihar and got my influence of mothertounge over pronounciation. He told me that I had enough knowledge and could easily crack the interviews but I should sit in good environment and speak slowly in the next round. His name was Snehansh Verma.

Conclusion:

  1. Go slowly. Speak clearly and confidently.
  2. Start from physical layer and move to the top layer or vice versa during debugging the issue.

Result: Qualified for Round 3

Round 3

  1. What subjects do you like most?
  2. What projects have you done or worked upon?
  3. Explain any one : TCP/IP stack or TCP.
  4. What do you understand from the role for which you are applying for?
  5. Explain any two instances where you have debugged and corrected your friends or somenone's PC and what were the issues?
  6. How checkdisk utility program present in Windows works?
  7. What command is used to list processes in linux and what are the information you get in the output of the command?
  8. Hypervisors and their types.

My experience: The interviewer didn't seem interested. He was doing some other work and there was a lot of pauses during the interview. He said that my resume matches more of a developer and since I have done a number of projects in web-development and a few in cybersecurity, why am I applying for a support role. Then, he went on justifying how support role people suffers from growth stagnation in long run and they only have two options, either to continue on same profile or go into consultation. I had to prove him that I was deeply motivated to work on support profile. So, I told him that I have studied Networking deeply and from a book called Computer Networks by Jeff Kuros and once, in my 2nd year, I was searching for opportunity to give CCNA exam with college support. Anyhow, he was consistent on his words and lastly, told that I should be developer.

Conclusion:

  1. Depending upon the role you are apply, change your words.
  2. Explain your points clearly and don't speak extra or add up something which even you might not be sure of. They are very experienced people in their domain. So, don't over mouth. Speak clearly and stick to the point.

Result: Rejected in Final Round