Skip to content

VMware Interview Experiences

How VMware fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

VMware placement process includes: 1. Online Coding Round (90 minutes) - 2-3 coding questions on DSA and algorithms. 2. Technical Interview Round 1 (60 minutes) - DSA and algorithms. 3. Technical Interview Round 2 (60 minutes) - System design and virtualization concepts. 4. HR Interview (30 minutes) - Motivation and company fit. Total duration: 2-3 weeks from application to offer.

Eligibility (from student reports): 7.5+ CGPA or 75%.

Fresher package ballpark (from student reports): ₹25-35 LPA. Confirm on your offer letter.

Round Duration What they test
Online Assessment 90-120 min 2-3 coding problems (DSA)
Technical Round 1 45-60 min DSA + detailed project discussion
Technical Round 2 45-60 min DSA / system design basics
Hiring Manager / HR 30-45 min Behavioural + team fit

These notes are consolidated from public student write-ups of VMware’s India campus and off-campus MTS / Intern+MTS hiring. Most detailed accounts are from the 2021-2022 on-campus cycles (VMware has since been acquired by Broadcom, and fresher hiring volumes and branding have changed), so treat the round shape as the durable part and confirm the current cycle with your placement cell.

Who was hiring and for what. Reports are mostly for MTS-1 / Member of Technical Staff, often offered as a 6-month internship converting to full-time. Selections are small: one on-campus account describes 5 students getting FTE + internship and 1 getting internship only out of the whole drive. CSE is not a hard requirement in every drive — that same write-up is from an ECE candidate.

Online assessment. Candidates commonly report the test running on hirepro.in, with roughly three sections: aptitude, general programming MCQs, and a coding section where you pick a language (Java or C++ are the ones people mention). Nobody describes an exotic screen — clean, fully-passing solutions are what carries you through.

Technical rounds (usually two, ~50 minutes each). The recurring theme in reports is that VMware pushes on internals, not just on getting a working solution:

  • Data structures with follow-ups on how they work inside — e.g. hash maps and collision handling, priority queues, BSTs. Reported coding asks include group anagrams, LRU cache, checking whether a binary tree is a BST, inverting a binary tree, minimum insertions to make a string a palindrome, and counting ways to climb stairs one or two at a time.
  • Operating systems is heavily weighted across accounts: process vs thread, process synchronisation, deadlock, memory management, zombie and orphan processes, interrupts, and basic Linux/bash commands.
  • Core language and OOP: static, polymorphism, encapsulation, pointers, C vs C++.

Managerial round (~30 minutes). Resume, internships and projects in depth, plus how you apply OOP / interfaces / threading to something real. Also softer probes on time management and how you pick up new things.

HR round (~10 minutes). Short. Where you see yourself, what you are proud of, background, and feedback on the process.

What the accounts suggest actually matters

  • OS depth is the differentiator. Several write-ups spend more space on OS questions than on DSA.
  • Be ready to explain a data structure’s implementation, not only its API.
  • The managerial and HR rounds are reported as conversational rather than eliminating, but resume claims do get tested.

Reports vary by campus, year, and role, and VMware’s hiring has changed post-acquisition. If your placement email says something different, follow that.

  1. Longest substring without repeating characters. Usually expects sliding window + hashmap
  2. Binary tree level order traversal. Usually expects BFS
  3. Detect cycle in a directed graph. Usually expects DFS colouring / topological sort
  4. Discussion on virtualization basics and OS, bottlenecks, failure modes, simple APIs
  5. Detailed project discussion, architecture, hardest bug, what you would change
  1. Why this company?
  2. A disagreement with a teammate and how you handled it
  3. An ownership example from a project
  4. Relocation preference
  • Clear the screening round first. Timed practice beats last-minute topic hopping.
  • For domain questions, explain virtualization basics in plain language, inputs, outputs, what breaks at scale.
  • OOPs and SQL still open a lot of VMware panels. Do not skip fundamentals.
  • HR answers should be concrete. One story with a result beats five slogans.
  • If you do not know something, say so and outline how you would find out.

After technical rounds, VMware usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

Cisco · IBM · Oracle · Microsoft · Dell · Google