VMware

  www.vmware.com
Work in HR? Unlock Free Profile

VMware Software Engineer Interview Questions & Reviews

Updated Jul 7, 2014
All Interviews Received Offers

Getting an Interview  

39%
30%
15%

Interview Experience  

40%
37%
21%

Interview Difficulty  

Average Difficulty
34 candidate interviews Back to all interview questions
Relevance Date Difficulty
in

Accepted Offer

Positive Experience

Average Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

I applied through a recruiter and the process took 4+ weeks - interviewed at VMware.

Interview Details – Starts with a phone screen with hr and they give you a choice of tea prom to join. Later there is a technical phone screen with a team member. The office interview has 5 to 6 people. Some development, management, and hr. Sometimes interviews are two days. There are logic and programing questions.

Interview Question – One person asked me use of const in C++   View Answer

Negotiation Details – Yes, it was between two companies at the time.


No Offer

Neutral Experience

Average Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

I applied online and the process took a day - interviewed at VMware in March 2012.

Interview Details – Find the convergence point of 2 linked list

Interview Question – Find the convergence point of 2 linked list   Answer Question


Accepted Offer

Positive Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

The process took 4+ weeks - interviewed at VMware in March 2012.

Interview Details – Overall I had 5 phone interviews that took about 6 hours and 5 one-on-one and group interviews On site that took about 5 hours

I was contacted by a recruiter after about a month after submitting an application online. The recruiter was extremely nice and incredibly helpful. The inital recruiter screening went well and I was told it would be progressing.

I was contacted a couple of days later by one of the senior guys on the team. It was a fun discussion about goals, ambitions, history, experience and expectations. The call lasted about an hour.

I then had a further thee phone interviews over the coming week, including a pair programming technical test with an highly skilled engineer from outside the team.I really enjoyed the banter and the attitude from everyone, it was exactly the right mix of knowledge, skill work ethic and fun.

The onsite interviews were excellent fun, I met with all the senior players, including my bosses, bosses, boss. There was a lot of white board drawing, solutions questions & scalability questions. Everyone was extremely nice and engaging, I actually enjoyed myself and never once felt out of place or out of my league. The interviews were typically 45m to an hour each, some were group chats, others were 1:1

I left feeling excited and highly motivated. It was a very pleasant experience.I liked everyone I met.

Interview Question – What bottleneck challenges do you think we would face is this architecture was scaled up x50,000   Answer Question

Negotiation Details – I negotiated a higher salary and position using some soft skills. Some good advice is to not ask for anything directly, steer the conversation in that direction without being direct. If you demand something, its more likely to be rejected.


Accepted Offer

Positive Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Cambridge, MA

I applied online and the process took 2 weeks - interviewed at VMware in June 2011.

Interview Details – 2 rounds of telephonic
1 round online
Onsite 1:1

Interview Question – Programming Concepts
Questions pertaining to resume
  Answer Question


2 people found this helpful

Declined Offer

Neutral Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

I applied through other source and the process took 6 weeks - interviewed at VMware in July 2011.

Interview Details – - Recruiter screening (Week 1)
- Phone interview screen by hiring manager (Week 2)
- Phone interview screen by Senior Engineer - Technical Round (Week 3)
- In person interview with 10 people (Week 4)
- Salary and package negotiation (Week 5)

Signed NDA. Can't talk about the questions and other details

Interview Questions

Reason for Declining – Multiple offers. Decided to go with a company where I got a great package.


1 person found this helpful

No Offer

Negative Experience

Average Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

The process took 3 months - interviewed at VMware in July 2011.

Interview Details – Terrible process. Although they were nice enough to accommodate some of my scheduling issues, it was handled awfully. For example, after two phone screen interviews in mid-April that they were flying me out for an onsite interview, but due to significant screw-ups on their part (and a 3 week period when I was on vacation), it didn't happen till mid-July.

The interview scheduling itself was quite awful. Thrice, they asked me for dates that I could fly to California. Twice, those dates went by without any contact from them (even though I told them I had another offer, and they assured me they would hurry up). The third time, they emailed me the morning before and said I was going to be booked on a flight the next day! And then after I reminded them at 9 PM that night that I still didn't have tickets for my flight the next morning, they sent them to me about half an hour before midnight. I blame this, in part, for not having enough time to prepare.

The interview itself was OK, although I don't think I did well enough to get an offer. One interviewer was openly hostile towards me because he saw my major on my resume and immediately assumed that I was not qualified (He actually said the words "Your major is XXX. Why have you even applied for THIS job?"). They assured me a result very quickly, within a day or two, since I had to tell the other company that made me an offer to wait. It's been 3 days now, and no reply. I've pretty much given up hope; even if they do make me an offer, I'm not sure I want to work here

Interview Questions


No Offer

Neutral Experience

Average Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

I applied through an employee referral and the process took 3 weeks - interviewed at VMware in January 2011.

Interview Details – Initial communication consisted of discussions with a recruiter followed by a phone screen with the hiring manger. Interview was all-day at the VMware campus in Palo Alto. It consisted of one-on-one meetings with a number of engineers of various ranks from within the group, as well as the hiring manager and another group manager. The interviews focused on programming questions, but there were also systems design questions. Recruiter followed up in a couple of days following meeting with the interview team.

Interview Question – How would you implement VMotion?   Answer Question


1 person found this helpful

No Offer

Negative Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

The process took 5 days - interviewed at VMware in January 2008.

Interview Details – They turned me down. Interviewers were highly condescending, and looking for specific answers. After they declined me, I got offers from Microsoft and Google, with a good salary / stock combo at each.
They should learn to treat interviewees with respect, and train their interviewers to judge better.
Based on interviewer's attitude, I wouldnt wanna work there anyways, even if they offered me a better salary.

Interview Question – dont remember. some programming puzzle.   View Answer


No Offer

Positive Experience

Average Interview

Software Engineer Interview

Software Engineer

The process took 2+ weeks - interviewed at VMware in February 2007.

Interview Details – The recruiter had a formal chat and then arranged 3 1:1 interview over phone. Even though all the interviews are fared well, there is no response from them. I sent a mail to one of the interviewers and he mentioned that the Manager is out of station and will give a call once she is back. But no response anymore.

Interview Question – How do you do compression? Which is better whether inline or background? If so what are the advantages and disadvantages   Answer Question


5 people found this helpful

No Offer

Negative Experience

Difficult Interview

Software Engineer Interview

Software Engineer
San Francisco, CA

I applied through a recruiter and the process took a day - interviewed at VMware in January 2007.

Interview Details – At the time I had my resume posted online; I was approached by VmWare and requested to interview with them by phone.

I agreed to take the interview and was informed that the interview would be related to C++ questions.

When the interview started, I was initially slightly taken aback at the brusque manner in which the interview proceeded; not unfriendly per-se, but there was hardly any preamble before the interviewer launched into his series of questions. I wasn't terribly put off by the manner, really; this was a screening interview, after all... however, as an experienced engineer with a steady capability to land the job I want, I now view interview processes as a 2-way street and expect the opportunity to ask at least a couple of questions.

The real issue I had with the interview was the content. Out of about 10 questions, not one related to C++, which was what I had been told; I don't care if an employer wants to keep the content of their interview secret, but to advise me of the content in advance, but then switch tack without warning is bad coordination at best, and sneaky at worst.

The actual questions asked were complex algorithm problems, not generic problem solvers, but very specific algorithmic-related scenarios, for which you pull a known algorighm out of the box and recite it; essentially a memory-test.

It became a bit ridiculous when the interviewer indicated that if I already knew the answer that I should tell him this and he would go to the next question.... So I was expected to, within seconds, over a phone, solve fairly complex problems that would normally take at least a couple of hours to review and solve from first principles.

It was basically a catch-22 situation; If I happened to know the answer , I wasn't supposed to give it, but if I didn't know the answer I was supposed to, at the drop of a hat, come up with the full solution.

It's a fairly standard process to present oblique problems to interviewees and see how they grapple with them; I do this myself when I am on the other side of the desk, but in a phone interview you simply don't have the time to work through hyper-complex problems that have specifically only one answer, and it is impossible for the interviewer to determine your collaborative capabailities; it becomes, essentially, a stress-test.

Anyways, in the end I muddled through the problems; for the algorithms I didn't know I did pretty well, I think. In fact I pulled some decent solutions out on short notice. I didn't care if they called back, I wasn't going to accept any job there; I knew I would end up working with the interviewer and, to be frank, I don't work well with people who are inflexible in their thinking. They did call back about a year later indicating that they were interested in talking to me again. At this point I had landed a great position at a different company and was still a bit annoyed so I declined.

In conclusion, for this particular group, and perhaps only this person in question, it appeared that they were filtering out people who didn't have robot-savant type quailities. This might not reflect the culture as whole, but it certainly turned me off this place.

The lack of a follow-up email after the interview was not very kosher, either... I didn't hear from them again until they were on a different recruiting drive.

Interview Question – "I'm going to ask you a series of questions, if you know the textbook answer, don't bother answering and let me know and I'll just move on to the next one, OK?"   View Answers (2)

See What VMware Employees Are Saying

 Current Marketing Manager in Palo Alto, CA

Pros: “Innovative company--never complacent, always working to reinvent itself to add more value to customers and demonstrate market success. Very smart set of coworkers--top talent.” Full Review

Worked for VMware? Contribute to the Community!

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.