VMware
41 questions · 13 experiences · LeetCode (51) · Blind (1) · 1p3a (1) · Other (1)
54 entries
1/3Omnissa | MTS-3 | BLR
VMWare | MTS2 | Bengaluru | Jan 2023 | Offer
Vmware | SMTS (C/C++, networking) | Bangalore | 22 Jun 2023 | Rejected 😀😀
VMWare
VMware Interviewer NoShow
VMWare Interview
Help need for VMware Sr. Software Engineer interview USA
VMWare Onsite Experience - SDE [US]
Vmware OA
VMware | SMTS | 8.5 yoe | Interview Experience [Rejected]
Vmware Workspace ONE UEM
OA assesment | VMware
VMware | MTS | India-Banglore | 9 Feb 2022 (Reject)
VMware | Staff Software Engineer | Bangalore | June 2022 [Rejected]
VMware | MTS 3 | Bengaluru, India | Apr 2022 [Reject]
VMware | Decode all possibilities from a given encoded ASCII string
VMware | OA New Grad 2020
VMware | SWE | Palo Alto | Nov 2019
VMware | Phone | Hangman Solver
VMware | Phone | Validate JSON
VMware | SWE | Bangalore | May 2020 [Reject]
VMware | MST4 | Sennior Lead Software Engineer | All Rounds (Team 2)
Phone Screen - Front End - VMWare - Reject
VMWare | MTS3 | Bangalore | April 2021 [Offer]
VMware | MTS 1 | Sept 2021 [Offer]
Omnissa | MTS-3 | BLR
Question Details
CSE B.Tech from Tier-1 Institution
3 years of experience in a product-based company.
Application Process:
I applied through LinkedIn and received a call from a recruiter. He asked for my interview availability and scheduled it (no online assessment).
Round 1:
Type: DSA Round
This round started with a brief introduction from both sides, and then we moved on to the problems. The interviewer asked 2-3 DSA questions, primarily related to trees and strings. The difficulty level of the problems was medium. I was able to solve all the problems within the given time. He also mentioned that this role requires a deeper knowledge of Windows and highlighted that it might be challenging to switch from such a tech stack.
Verdict: Strong hire
Round 2:
Type: Technical Round
This round also began with a brief introduction from both sides, followed by a few questions related to .NET. The interviewer asked one problem on strings. The difficulty level was medium. I managed to solve the problem, but it took some time. I faced power cuts multiple times (3-4) during the interview, and I was concerned that the interviewer might think I was cheating since it happened just when I was figuring out the solution. However, she was supportive and never made me feel nervous. Later, she asked me to write unit tests for a few dummy methods and classes. After that, she asked a few questions about OOP concepts. She seemed quite impressed, and I asked her a closing question about the team she was working with.
Verdict: Strong hire
F2F Scenario: I got to know that next rounds going to be onsite. I had to travel to Bangalore for the onsite rounds and was a bit disappointed as I thought face-to-face interviews were outdated. I arrived in Bangalore just after Diwali with high hopes. Both were scheduled face-to-face on the same day, but unfortunately, there was no one to guide me as the recruiter seemed to be out of the office. After multiple attempts, I managed to reach out to the recruiter. I reached the Omnissa office.The interviewer himself came to meet me, and we started before the scheduled time. After that I had lunch there, but wasn\'t impressed by the food and facilities.
Round 3:
Type: Design Round (Onsite in BLR)
He asked a few questions around .NET and OOP concepts, then asked me to design an orchestrator to schedule processes with priorities. Initially, he mentioned 3 priorities, later extending it to multiple priorities. I explained the FIFO approach and discussed using Map<int, vector<int>> processByPriority, considering higher numbers as higher priority. I would always take the first process from the highest priority, with two events running as the orchestrator starts\u2014one pushing the process to the map and the other scheduling the processes. I kept a lock while scheduling to deal with concurrency. It was a great discussion, and he actively participated. I drew diagrams to show the workflows of incoming processes and scheduling, and he seemed convinced.
Verdict: Strong hire
Round 4:
Type: Managerial Round
This round was supposed to happen after Round 3, but the manager was busy with meetings. I was told by the Round 3 interviewer that the managerial round could happen online later, and I could leave for the day. After waiting for half an hour, I had lunch and left for home. Ultimately, the managerial round didn\'t happen, and they directly offered me the position, mentioning that they were happy with the feedback from Round 3.
Verdict: Offer extended without the managerial round.
I believe there was a bit of luck involved, whether it was dealing with the power cut issue or not having the managerial round. I have another offer as well, so I haven\'t made my decision yet.
Compensation details: https://leetcode.com/discuss/compensation/6260549/PayPal-Vs-Omnissa-or-Urgent-help-needed-or-offer-evaluation