My process was: HR phone call -> Tech screen -> Onsite (4hrs). It might be different depending on the team you are applying for.
The most positive part of the process was the tech screen, as it was conducted by someone who was a really thoughtful interviewer.
My onsite was ok; it consisted of:
1:1s with different team members. One of the technicals was really poorly planned in my opinion. It was a debugging exercise but it required 20 min of context and the objective of it was vague.
I left the interview feeling like I did just fine; I was able to answer all the questions and have conversations with the interviewers. But the recruiter called me a couple days later to say that they're not moving forward with me, as the team deemed that I am not senior enough for the role.
They mentioned that I would have been a fit for a mid-level role, which confused me because I was interviewing for Engineer, not Senior Engineer (and they even had a separate job posting for the latter).
I asked if the role had a senior title in it, and the recruiter said they will be looking for senior engineers moving forward.
The reasoning around the rejection sounded shady so it left me a bit confused. On the plus side, the recruiters were very warm, professional, and responsive, so that was at least a pleasant experience.
Walk me through one of your projects.
The following metrics were computed from 9 interview experiences for the Vimeo Software Engineer role in New York, New York.
Vimeo's interview process for their Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for Vimeo's Software Engineer interview process in New York, New York.