The first call with the recruiter took 30 minutes. The second call was with the hiring manager, who was friendly and seemed engaged. I was emailed a link to a coding challenge and given 45 minutes to solve a medium LeetCode problem, followed by a couple of behavioral questions. The recruiter notified me the next day that I had made it to the next round. At this point, I asked what the rest of the interview process looked like, but didn't receive a response. The recruiter mentioned in the calendar invite that the third interview would incorporate React, HTML, and CSS. Because of this, I expected a machine coding problem. The third interview (with another engineer in the org) ended up requiring knowledge of vanilla JS, and definitely no React/CSS. The engineer interviewing was nice enough and helped me through with Google searches. I was rejected the same day.
It would have been helpful to get a little more insight/accurate info regarding what to prepare for.
Q: What was one time you overcame a challenge?
The following metrics were computed from 1 interview experience for the Vimeo Software Engineer/Web Developer role in United States.
Vimeo's interview process for their Software Engineer/Web Developer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Vimeo's Software Engineer/Web Developer interview process in United States.