VMware Interview Experience for Developer | On-Campus
Question Details
VMware visited our campus in October. Around 70 students from our college registered for the VMware placement drive.I went through 5 rounds:
Online Round Technical...
Full Details
VMware visited our campus in October. Around 70 students from our college registered for the VMware placement drive. I went through 5 rounds:
Online Round Technical Round 1 Technical Round 2 Managerial Round HR Round Online Round: This round was a shortlisting round for the interviews. It was conducted on the HirePro platform. Aptitude Section: This section consisted of 10 multiple choice questions, for 15 minutes. The questions were based on logical, quantitative and verbal abilities. Technical Section: This section comprised of 29 multiple choice questions, for 30 minutes. The questions were from core Computer Science subjects, including Data Structures, Algorithms, Operating Systems, Computer Networks, Object-Oriented Programming, and Database Management systems. A few questions also required the debugging of basic C programs. Coding Section: This section consisted of 1 question, for 30 minutes. Languages offered were C, C++, Java 7 and Java 8. Given two numbers, R and S, find the number of R digit numbers whose sum equals S, https://www.geeksforgeeks.org/dsa/count-of-n-digit-numbers-whose-sum-of-digits-equals-to-given-sum/ Languages Section: This section required us to solve 5 multiple choice questions each of any 2 languages from C, C++, Java, and Python, for 15 minutes. I chose Java and C. Java questions were predominantly OOP and collections-based. C questions were based on structs and pointers. Within a couple of days, VMware came to our college for the pre-placement talk. Post the talk, results of the aptitude test were announced. 25 people made it to the interviews.
Technical Round 1: The interviewer was pretty cool and started by asking me to introduce myself. He began by giving me a simple puzzle. Given a number n, find a number k such that k % j = j - 1 for j = 2 to n. For example, for n = 3, k = 5; for n = 4, k = 11. The solution is to find LCM of all numbers from 2 to n. He then asked me to write code for the same. He noticed I'd mentioned various SQL and NoSQL databases on my resume. He then questioned me about the CAP theorem. He gave me various databases and asked me which guarantee of the CAP theorem they provided. I was aware of this so I answered correctly. He asked me to model a database design for the College Placement system and what choice of database I would make. He asked me about database indexing, and the data structures used for it. I was asked to explain the balancing of B-trees. The discussion then moved to trees, and he asked me balancing procedures for Red-Black trees and AVL trees. Further, he questioned me about sorting algorithms. He asked me to compare mergesort and quicksort, on their advantages and disadvantages. He then asked me possible approaches to improve their time complexities. Next, he gave me a simple chemical reaction and asked me to balance it. He then asked me what data structures I would use and the approach I would take to solve this programmatically. Overall, the interview was very interactive and interesting. He then asked me if I had any questions for him. I asked him about the projects he worked on and his overall experience. I was taken in for the
next round immediately.
Technical Round 2: The interviewer was very friendly. He asked me to introduce myself and then questioned me on my resume. I had a few Big Data projects on my resume. He asked me the need for Big Data. He then asked me to explain the entire working of a Map Reduce program. I chose Word Count as an example and explained the entire process. He asked me what sorting algorithm I would use in the shuffle-and-sort phase of Map Reduce. He then asked me to sort an array using merge sort by hand and model a Map-Reduce algorithm for merge sort. He then asked me to write code for merging two sorted linked lists. I wrote a simple iterative solution by creating a new linked list. He then asked me to optimize the space and also to write a recursive solution for the same. I had done a project on Web Crawlers. He asked me how a web crawler works and the discussion became project-specific. He then moved to networking and asked me to draw the OSI stack and explain the various layers. He asked me to list all protocols I knew for each of the layers. I was then required to explain HTTP and IP. Then, he moved to TCP and asked me how the sliding window protocol works. I was not aware of the details so he changed it to an analytical question and asked me to logically design a sliding window protocol of my own, giving me hints wherever required. The interview was quite refreshing. The key was to be sure of every word you have on your resume. I was then called for the managerial round.
Managerial Round: The interviewer was very crisp and to the point in his questions. He started by asking me to introduce myself and provide a family background. He then asked me about the various projects I had on my resume, and why I chose to do them. He questioned me about the failures I had faced in my life and how I dealt with them. Why VMware? Where do you see yourself in two years? He asked me about my future studies plans and how I would deal with team conflicts. The interview lasted for half an hour and 4 people made it to the HR round. A few people were asked to submit their resumes for further scrutiny, they would receive communication on their acceptance status later.
HR Round: Basic HR questions, short interview of about 10 minutes: Introduction, family background Current offers that I was holding What do my friends think of me? What if I don't get the offer? After the HR round, 1 person was offered an Internship along with a Full-time offer at VMware and 3 people were offered only an Internship with a performance-based PPO.
About This Question
This is a reported interview question from a vmware interview for a data science role (intern level) during the recruiter round reported in 2025.
It covers the following topics: Two Pointers, Linked List, Trees, Oop, Sliding Window, Sql, Stack Queue, Recursion, Sorting, Networking, Os, Math, System Design, Arrays, Stack .
Difficulty rating: Easy
Topics
More VMware Interview Questions
About VMware Interview Reports
This question was reported by a candidate who interviewed at VMware. 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 VMware are the higher-signal extractions to take from this report.
For broader preparation context, the VMware 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 VMware reports consistently are the ones worth investing in; one-off niche problems are not.
During Your VMware 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 VMware 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.