Verkada Software Engineer candidates describe a recruiter screen, LeetCode-medium coding, a system design or troubleshooting round, and a hiring manager conversation. Some also report an onsite presentation.
$171K
Avg. Base Comp
$255K
Avg. Total Comp
5 rounds
Typical Rounds
3-4 weeks
Process Length
Candidates who interviewed for Verkada's Software Engineer role describe a loop that starts with a recruiter screen and then moves into coding. Reports mention LeetCode-medium style problems, including an online assessment with a DFS graph question, and interviewers who want you to explain your reasoning out loud.
System design and troubleshooting come up repeatedly. One candidate was asked to design a log system that records a camera only after a 10-second threshold, with no duplicate entries inside that window. Another recalls multithreading and socket programming questions alongside a design discussion. A third was given an unfamiliar troubleshooting scenario and told to keep trying. Practice stateful designs, deduplication and time windows, and concurrency basics.
The final stages vary. One candidate describes an onsite in San Mateo with a presentation and a panel. Another describes a presentation on a topic they chose within loose parameters, followed by one-on-one conversations with engineers from firmware, cloud and product. Pick a project you can explain clearly in 20 to 30 minutes. Hiring manager rounds usually probe past projects and behavioral questions.
Experiences are mixed. Two candidates received offers, one declined an offer, one withdrew, and two did not get offers. In the most recent no-offer report, the recruiter call was canceled and rescheduled. The technical problem was described verbally, and the candidate was unsure whether code or discussion was wanted. It ended with a 20-minute design round where the interviewer expected a fast move through requirements to a final design. Ask early what format the interviewer expects, and practice scoping requirements quickly. Reported timelines run from about three weeks to a month.
Synthesized from 11 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 Verkada process.
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 Verkada
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Random SQL Sample | |
| Upsell Transactions | |
| Top 3 Users | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Size of Joins | |
| Prime to N | |
| String Shift | |
| Largest Salary by Department | |
| Paired Products | |
| Find Bigrams | |
| Last Transaction | |
| Longest Streak Users | |
| Duplicate Rows | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Minimum Change | |
| Comments Histogram | |
| Payments Received | |
| The Brackets Problem | |
| Raining in Seattle |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation about background, interest in the role and career direction. Most describe it as casual and low-pressure. One candidate says the recruiter canceled shortly after the scheduled start and rescheduled by email, so keep your availability flexible and have a clear answer ready on why you want the role.
Candidates describe a timed online assessment or a live coding screen, such as HackerRank or CodeSignal, with data structures and algorithms problems around medium difficulty. One report includes a DFS graph question. Interviewers typically want you to narrate your approach and discuss complexity. Format can vary, so confirm whether code or discussion is expected.
Candidates report system design and troubleshooting questions. Examples include a log-deduplication design with a 10-second threshold, multithreading and socket questions, and an unfamiliar troubleshooting scenario. Experiences differ: some interviewers were supportive and gave hints, while one expected a full design in about 20 minutes. Practice scoping requirements quickly.
Candidates describe manager or team conversations about past projects, difficult problems and how they handled challenges. One candidate was asked how they would explain a technical issue to a non-technical person. Experiences with these rounds range from relaxed and engaged to scripted, so prepare specific project stories you can discuss in depth.
Some candidates report a final stage that includes a presentation and several one-on-one conversations with engineers across teams, including an onsite in San Mateo. One candidate chose their presentation topic within loose parameters. Not every report describes this stage, so it may depend on team or timing. Prepare a project you can present in 20 to 30 minutes.
