How VMware fresher interviews usually run, synthesized from campus MTS/FTE reports (HirePro OAs and OS-heavy technicals). We reorganized rounds and flagged that Broadcom-era volumes may differ - treat this as a prep map, not a script.
Typical loop (candidate-reported): Online Assessment (aptitude + CS MCQs + coding) → Technical 1-2 (DSA + OS internals) → Managerial → HR. Duration often 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.
Candidate profile: On-campus FTE; 3 of ~24 shortlisted after OA received offers. Source: GeeksforGeeks FTE 2022 write-up.
OA (~107 min)
CS core MCQs + aptitude + one easy coding implementation
~24 advanced to interviews
Technical 1 & 2 (~50 min each)
Two coding rounds plus projects; second round added OS + SQL
Candidate reported answering ~85% in tech rounds - still selected
Managerial (~30 min)
Project design; OS scheduling threads; heap vs stack for a passed address
General discussion; candidate answered ~50% but stayed positive
HR (~15 min)
Five-year plan; college achievements; VMware product used; what excites you about VMware; feedback on process smoothness
Final result: Selected (1 of 3 offers)
Takeaways
What decided it: Clearing OA into a small shortlist, solid coding/projects plus OS/SQL in tech, and staying positive in managerial despite ~50% answers - curiosity in HR about VMware products helped.
Common fail: Collapsing after one hard OS question; no product awareness for HR.
How to practise: OS scheduling + heap/stack address questions; name one VMware product you have touched or researched.
One coding problem (30 min) - e.g. digit-sum counting variants
Optional: two languages chosen; output-based MCQs (C/Java common)
On-site loop
Technical 1 & 2 (coding + fundamentals)
Managerial + HR as separate panels on some schedules
Timelines: PPT same day as or after OA; interviews within days
Takeaways
What decided it: Sectional HirePro timing (aptitude + technical MCQs + one coding problem) to reach the ~25/70 interview shortlist.
Common fail: Burning the aptitude section; weak C/Java output MCQs when two languages are chosen.
How to practise: Timed four-section HirePro mocks; one digit-sum style coding problem in 30 minutes.
What candidates report
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.
Sample answers for high-frequency questions
Use these as frames, not scripts - interviewers probe follow-ups.
Q. What is virtual memory and how does paging work? A. Virtual memory gives each process its own contiguous address space that the hardware maps onto physical frames, so processes cannot read each other’s memory and the OS can over-commit RAM. The address space is split into fixed-size pages (commonly 4 KB) and physical memory into frames of the same size; a per-process page table records the virtual-to-physical mapping, and the MMU consults it on every access with a TLB caching recent translations. If a referenced page has no valid frame the MMU raises a page fault, the OS reads the page from disk into a free frame, updates the page table, and restarts the faulting instruction. Excessive faulting because the working set exceeds RAM is called thrashing, and it is why VMware-style memory over-commit needs ballooning and page sharing to stay usable.
Q. Compare process scheduling algorithms and their trade-offs. A. First-Come-First-Served is trivial but suffers the convoy effect - one long job stalls everything behind it. Shortest-Job-First gives provably minimal average waiting time but needs future burst lengths, which you can only estimate, and it can starve long jobs. Round Robin gives each process a fixed time quantum and is the practical choice for interactive systems: too large a quantum degenerates to FCFS, too small and context-switch overhead dominates. Priority scheduling risks indefinite starvation of low-priority tasks, which is fixed by ageing - gradually raising the priority of a job that has waited a long time. Linux’s CFS instead tracks virtual runtime per task in a red-black tree and always runs the task with the least virtual runtime, approximating fair sharing.
Q. What is the difference between a process and a thread in Unix? A. A process has its own virtual address space, file-descriptor table, and PID; a thread is a schedulable execution context inside a process that shares the address space, heap, and descriptors with its siblings while keeping its own stack, registers, and program counter. In Unix, fork() duplicates the calling process with copy-on-write page mappings, so the parent and child see separate memory once either one writes. Threads are created with pthread_create and are cheaper both to spawn and to context-switch, because the page tables and TLB entries stay valid. The trade-off is fault isolation: an unhandled segfault or corrupted pointer in one thread takes down the whole process.
Q. Explain Unix file permissions and what chmod 644 means. A. Each file has three permission triads - owner, group, and others - each carrying read (4), write (2), and execute (1) bits. chmod 644 sets owner to 6 (read plus write), and group and others to 4 (read only), which is the normal mode for a regular data file. chmod 755 adds execute for everyone, which is what a script or a directory needs, since on a directory the execute bit means the right to traverse into it rather than to run it. Beyond the basic nine bits there are the setuid, setgid, and sticky bits - the sticky bit on /tmp is why any user can create files there but only the owner can delete their own.
Q. Walk through what happens in a TCP three-way handshake. A. The client sends a SYN segment carrying its initial sequence number and moves to SYN_SENT. The server replies with SYN-ACK, acknowledging the client’s sequence number and supplying its own, and enters SYN_RECEIVED. The client sends a final ACK and both sides move to ESTABLISHED, at which point data can flow. The handshake exists so both sides agree on starting sequence numbers and confirm bidirectional reachability, which is exactly what UDP skips - it is connectionless, with no handshake, no ordering, and no retransmission, which is why it suits DNS lookups and live video where a late packet is worse than a lost one. Teardown is four-way (FIN, ACK, FIN, ACK) because each direction closes independently.
Tips from successful candidates
Assessment tips
Confirm the current VMware pattern from the drive mail before practising old papers
Finish one problem or section fully before starting the next
Revise the fundamentals listed in the round table on this page
Interview tips
Narrate trade-offs; expect “why” after every answer
Only list projects you can defend under follow-ups
Prepare 3-4 STAR stories for behavioural prompts
HR tips
Know why VMware, not just why the industry
Be clear on location / notice period / higher studies
These links are research inputs we used to map MTS campus loops and OS-weighted panels - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for VMware.
Reports vary by campus, year, and role, and VMware’s hiring has changed post-acquisition. If your placement email says something different, follow that.
Questions that come up often
Coding / technical
Longest substring without repeating characters. Usually expects sliding window + hashmap
Binary tree level order traversal. Usually expects BFS
Detect cycle in a directed graph. Usually expects DFS colouring / topological sort
Discussion on virtualization basics and OS, bottlenecks, failure modes, simple APIs
Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Why this company?
A disagreement with a teammate and how you handled it
An ownership example from a project
Relocation preference
Practical tips for VMware
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.
HR interview
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.
