Vevo logo

Vevo Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 8 interview experiences · FREE TO READ

3 Rounds average
Easy Typical difficulty
62.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Vevo.

Showing 3 of 8
Vevo logo
Vevo

Software Engineer

Engineering · more than a year ago

Entry Easy Negative experience No offer 5 rounds
Interview process
Phone screen Technical screen Onsite Presentation Offer
Interview formats
Coding Technical Behavioral Presentation

The interview process was pretty typical. It started with a video call where I had to solve an algorithm problem. Then, I had an on-site interview where I met the CTO virtually, and I think they would be a great person to work for. However, one of the on-site rounds was a really bad experience. The interviewer was super condescending, and it was the only time I ever wanted to leave an interview. Their question had five parts, and if you couldn't solve the first part, you couldn't get the other four. They wouldn't move on if you got it wrong unless you were quiet for 3 minutes. Even after I said I didn't know the answer, they told me to guess. When I guessed, they made me feel dumb for even suggesting it. I definitely won't be applying to VEVO again and will tell others about this.

Confirmed questions2 questions
  • I was asked some easy data structures and algorithms questions.
  • I was also asked some domain specific questions that were challenging.
Vevo logo
Vevo

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Technical Coding Behavioral

First, there was a phone chat with the recruiter, which included some standard technical questions. Then, I had another phone screen with a developer who gave me a programming challenge. Finally, I went in person to meet with some developers and the CTO. There weren't any programming challenges in this last part, just a few pre-written questions. Mostly, they wanted to get a feel for my personality and how competent I am through conversation. It was pretty relaxed, and I had plenty of time to talk and ask questions. Everyone I met had a great personality, and the developer culture seemed really awesome.

Confirmed questions1 question
  • Can you discuss the pros and cons of using configuration management tools such as Puppet?
Vevo logo
Vevo

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical Coding

Recruiter reached out, then had a screening phone call, followed by a technical screening with an engineer. I got a great impression about the team and the company after the conversation. An on-site interview with 5 people included technical challenges, whiteboarding, lunch with the team, discussions with the team's project manager, and an interview with the CTO.

Confirmed questions2 questions
  • Can you solve problems using recursion?
  • JavaScript coding tasks

Vevo Software Engineer Interview Questions

Quoted word for word from Vevo interview reports.

Can you discuss the pros and cons of using configuration management tools such as Puppet?

Read reports

How would you design a system to manage multiple elevators in a big building?

Read reports

Formats, difficulty and experience

Across all 8 Vevo interview reports.

Interview formats

Technical 36.8%
Coding 31.6%
Behavioral 21.1%
Presentation 5.3%
System Design 5.3%

Interview difficulty

Easy 50%
Average 37.5%
Difficult 12.5%

Candidate experience

Negative 37.5%
Positive 62.5%