Vimeo Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 34 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Vimeo.
Vimeo
Software Engineer Intern
Intern Difficult Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Technical Behavioral
I went through 4 rounds for the internship. It started with a recruiter screening, followed by two technical rounds, and finished with an Engineering Manager round. The whole process was pretty smooth and the recruiter gave me updates nearly every week. I feel like I could have performed better in the technical rounds, but everyone I met was pretty chill.
Confirmed questions1 question
- What makes you want to join Vimeo?
Vimeo
Software Engineer
Mid Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Offer
Interview formats
Behavioral Technical Coding
Had a 30min recruiter chat first. Then a hiring manager call, who was chill and seemed into it. Got a coding challenge via email, had 45 mins to do a medium LeetCode, plus some behavioral questions. The recruiter let me know the next day I passed. I asked about the rest of the process but didn't hear back. The invite said the next interview would be React/HTML/CSS, so I thought it'd be a machine coding thing. But the third interview (with an engineer) was actually vanilla JS, no React/CSS at all. The engineer was cool and helped me out with Google. Got rejected the same day. It woulda been nice to have more accurate info on what to prep for!
Confirmed questions1 question
- Can you share an instance where you overcame a challenge?
Vimeo
Software Engineer
Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Background check
Interview formats
Coding
It began with a standard recruiter call, and I was promptly scheduled for a technical screen. Sadly, the recruiter misinformed me about the tech screen's focus, leading me to prepare for the wrong subject matter. The actual screen involved two LeetCode problems within 30 minutes. If I'd had accurate information, I would have breezed through them and demonstrated my relevant skills later. However, I was caught off guard. I managed optimal solutions for both but stumbled due to the lack of preparation. After a period of silence, I had to inquire about my status, only to receive an automated rejection email. The recruiter seemed generally unclear about the role, and I had to seek clarification from engineers. Communication with engineers needs significant improvement! It's truly a pity.
Confirmed questions1 question
- Complete two LeetCode problems in 30 minutes.
Vimeo Software Engineer Interview Questions
Quoted word for word from Vimeo interview reports.
“What's the minimum characters needed to add to make a string a palindrome?”
Read reports →“Can you write an algorithm to find repeating characters within a given string?”
Read reports →“Could you create an interface to add a comment to a video at a given time-mark?”
Read reports →“What are the different types of data structures?”
Read reports →“Can you implement an in-memory cache that supports Add, Delete, and Update operations?”
Read report →“Can you explain how to do DOM manipulation with vanilla JS, specifically filtering a list?”
Read report →“Could you implement an LCU cache class that includes set and get methods, adhering to a specified capacity?”
Read report →“How would you design an algorithm to optimize large file upload speeds?”
Read report →“Could you write a webserver in Go, Java, or Node.js that processes metadata for HLS streams?”
Read report →Formats, difficulty and experience
Across all 34 Vimeo interview reports.