I applied through a recruiter - interviewed at VMware in February 2014.
Interview Details – My circumstances extended the process as well as the time of year. However the process was smooth overall. Many of the interviewers remained on-topic and wanted to ensure that the position was being fulfilled. Beyond that, they were interested in other interests to see where I may want to go within the company.
Interview Question – No questions asked were outside of the job realm Answer Question
Reason for Declining – Offer was competitive however I was looking forward to a better base salary. not a match with better compensation in other categories.
I applied through an employee referral and the process took 1+ week - interviewed at VMware in August 2012.
Interview Details – First phone interview, then a problem would be given over mail to be solved. Onsite interview will consist of 5 rounds typically. Team members would interview in elaborate style (not very tough), basic data structures, little bit language specific interviews might be there.
Interview Question – One manager asked to write lot of syntaxes in Java. Which I was not prepared. View Answer
Negotiation Details – Non- negotiable. For New graduates.
Interviewed at VMware
Interview Details – 2 rounds of phone and 5 rounds of onsite
Interview Question – all can be found from here. Answer Question
Interviewed at VMware
Interview Details – It went for almost a month.
first 3 telephonic interviews happened after that on-site (in Bangalore India office) interview happened.
After 3 days of on-site interview I got the offer
Interview Question – Questions were fairly easy.
Graphs, trees concepts were the focus Answer Question
I applied online and the process took 4 weeks - interviewed at VMware in November 2013.
Interview Details – I applied through the VMWare website. I heard back from a recruiter within 2 weeks of applying.
Step 1>There was a high level non technical conversation with the recruiter. Stuff like whats your background, what are you looking for and so on.
A few days later the recruiter called back to schedule a phone screen.
Step 2> The phone screen was 15 minutes long. They asked me some questions on C#, SQL, asp.net mvc and other stuff that was there on my resume. Nothing too hard.
Few days later the recruiter called back to schedule an in person interview. I asked for a date 1 week later and they were okay with it.
Step 3>The in person interview was about 5-6 hours of back to back interviews. All the interviewers were extremely polite. They made me very comfortable. During the interview they even helped me a few times when I got stuck. However I must say that this was the toughest interview I ever attended. The interview involves a lot of white board coding. There were obviously many questions based on what was there in my resume, besides that these are the general areas that they targeted
Questions on my master's thesis ( which I submitted 7 years ago!)
Many algorithm based questions (code in your language of choice).
Low level questions on memory management.
Design/Architecture based questions.
There was a question where they asked me to pick flaws in the architecture of a certain system.
At the end of the interview I was about 70% confident that I would get an offer. (The 30% doubt was there because they had to help me a few times along the way)
Step 4> About 2 days later I got a call from the recruiter with an offer.
Interview Question – Using minimum memory, write a program that can fit a dictionary inside the smallest possible crossword (words have to make sense horizontally as well as vertically). Answer Question
Negotiation Details – They gave a very generous (due to the benefits) offer and I did not even try to negotiate.
I applied through a recruiter and interviewed at VMware.
Interview Details – Was contacted by a recruiter through linkedin and there was a technical phone interview scheduled.
I applied through a recruiter and the process took 2 weeks - interviewed at VMware.
Interview Details – The interview process at VMWare seems similar to other technical companies. It starts in the morning, about 9am. 5 or 6 interviews are given. Often each interviewer has different areas to explore, but not always. They range from behavioral questions ("Tell me about the time you...") to code test questions.
Interview Question – "What do you see yourself doing in 5 years." View Answer
Negotiation Details – There was no negotiation.
I applied through an employee referral and the process took 4 weeks - interviewed at VMware in September 2010.
Interview Details – 2 phone interviews and a 1 day onsite interview. Onsite interview had 6 rounds of interviews including lunch + an interview with HR in the end.
C++, Java, algorithms, OS and networking concepts, distributed systems, writing code in each round of interview. Your previous projects.
Interview Question – If you have all the CS concepts covered you should not have much difficulty. Answer Question
I applied through an employee referral and the process took a day - interviewed at VMware in October 2011.
Interview Details – Was referred by a friend for this position. The manager called me first for a telephonic interview. The had done research in grad school which aligned with the requirements for this position. The manager asked few questions about my research and explained what they do and what they expect. Things went well and was called onsite in a week.
My first interview was with a staff engineer. He was really good, asked really interlligent questions and helped me when needed. It went really well. The second interviewer asked questions on my research and some on OS frundamentals. And then, I had to interview with an arrogant engineer after lunch. He dint know a damm about my research and or experience. The interviewer and me worked in the same city back in India a few years back, so he started asking about projects that company worked on (and not me). He was just too arrogant. I refused to answer questions after a point even though I thought i knew.
So expect for this one interview, others went fine. But as usually, the company never contacted me back. When I called the recruiter, he said the mgr and team was busy..
So to summarize, from what I have heard and experienced, vmware looks for ppl with specific expertise only. It is not a place u can learn new things, u just develop based on your existing knowledge.
I applied through a recruiter and the process took 6 weeks - interviewed at VMware in January 2012.
Interview Details – Not a super hard interview, but definitely not easy. I had 3 phone screens followed by 6 1-on-1 interviews onsite. Luckily, the recruiter I worked with was very helpful. Had a difficult time communicating with one interviewer(both on the phone and onsite), but in general everybody was extremely professional. As for the answers to the questions, they aren't as important as your approach to the problem. The interviewers generally tend to push you in the right direction if they think you are off track .
Questions mostly focussed on string manipulations, scalability, multithreading, design patterns, and data structures. Definitely brush up on the basic data structures.
Interview Question – multithreading Answer Question
Negotiation Details – I didn't negotiate much as the initial offer was pretty good. If they think you're good, they will make a matching offer.
— Full Overview
Provided by employer [?]
This is the employer's chance to tell you why you should work for them. The information provided is from their perspective.
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –