Vimeo software engineer candidates report a recruiter call and a hiring manager conversation, and two describe a timed coding round next. Prepare project deep-dives, feedback stories, LRU-style coding, and vanilla JavaScript.
$163K
Avg. Base Comp
$190K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Three candidates describe Vimeo's engineering interviews, and all three report no offer. All three started with a recruiter conversation followed by a hiring manager call. The later rounds are where the reports diverge.
One candidate says the Zoom hiring manager call lasted about 45 minutes. They were asked to walk through a current project in detail, covering their technical decisions and challenges, plus a behavioral question about receiving constructive feedback. Prepare one project you can explain end to end, including the trade-offs you made and what you would change.
The technical round is where the reports differ most. One candidate, who interviewed for a senior role, describes an LRU cache problem with set and get methods in a fixed time window. They say every test case had to pass, and a single failed edge case ended their candidacy. Another candidate reports a 45-minute, medium LeetCode-style coding challenge with a couple of behavioral questions. That candidate's third round was announced as React, HTML and CSS, but the engineer tested vanilla JavaScript instead. That engineer allowed Googling during the session. Treat these as individual reports, not a fixed format. Ask your recruiter what each round will cover.
Practice classic data structure problems such as caches, and finish with time left to test edge cases. Also brush up on core JavaScript without a framework if your role is front-end leaning. Candidates describe the people they met as friendly. Two said they got little feedback or detail on next steps, so confirm the schedule and format as you go.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Vimeo process.
I started with a recruiter screen that was pretty straightforward, just covering basics and what I was looking for in a role. They seemed genuinely interested in finding a good fit and mentioned they'd try to match me with a team that aligned with my interests. The hiring manager call came next over Zoom and lasted about 45 minutes. That's where things got more substantive—they asked me to walk through a project from my current work in detail, digging into the decisions I made and the technical challenges I faced. They also threw in a behavioral question about a time I'd received constructive feedback and how I handled it, which felt like a genuine conversation rather than a scripted interview. After that initial screening, I was told I'd move to a technical assessment and virtual onsite, but I didn't end up advancing. I asked the recruiter for feedback on what went wrong, but they never got back to me, which was frustrating. The whole process felt transparent and the people I spoke with were genuinely nice, but ultimately it didn't work out. Looking back, I wish I'd gotten clearer signal on where I fell short—whether it was the technical assessment, the behavioral fit, or something else entirely.
Prep tip from this candidate
Be ready to dive deep into a specific project you've worked on—they'll ask detailed follow-up questions about your technical decisions. Practice the behavioral component too, especially around receiving and acting on feedback, since that seems to be a key part of their evaluation.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Vimeo
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Largest Salary by Department | |
| String Shift | |
| Top 3 Users | |
| Prime to N | |
| Random SQL Sample | |
| Upsell Transactions | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Customer Orders | |
| Minimum Change | |
| Scrambled Tickets | |
| Comments Histogram | |
| Size of Joins | |
| Retailer Data Warehouse | |
| The Brackets Problem | |
| Find the Missing Number | |
| Flight Records | |
| P-value to a Layman | |
| Project Pairs | |
| Google Maps Improvement | |
| Download Facts |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening recruiter call, about 30 minutes in one account, covering background and what you want in a role. One candidate says the recruiter mentioned trying to match them with a team that fit their interests. Expect it to be fairly standard.
Candidates report a video call with the hiring manager, about 45 minutes in one account. That candidate was asked to walk through a current project in detail, including their decisions and technical challenges, and to describe how they handled constructive feedback. Another candidate describes the call as friendly and engaged.
Candidates report a timed coding round. One describes a 45-minute, medium LeetCode-style challenge with a few behavioral questions. A senior-role candidate was asked to implement an LRU cache with set and get within a fixed window, and says all test cases had to pass. Practice edge cases and debugging under time pressure.
One candidate reports a third round with an engineer, announced as React, HTML and CSS but actually testing vanilla JavaScript. Googling was allowed. Another candidate was told a technical assessment and virtual onsite would follow. Clarify the format and stack of each round with your recruiter ahead of time.
