Verkada PM candidates describe a multi-stage loop: recruiter and hiring manager conversations, a case or presentation, and an onsite with a VP. Experience level and specific examples came up repeatedly.
$153K
Avg. Base Comp
$200K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Verkada Product Manager interview as a multi-stage loop that usually starts with a recruiter conversation and a hiring manager conversation and ends in an onsite. Two of the four reports mention a case study or presentation. One candidate had three to four days on a take-home case and presented it to a panel. Another described a presentation prep meeting followed by an hour-long panel at the San Francisco headquarters.
The candidate who accepted an offer said specificity was rewarded. The hiring manager asked how many projects they managed and how their time split across them, and product-led growth examples with real numbers came up across several rounds. A technical conversation covered the tech stack rather than coding, so be ready to discuss how the product is built and its tradeoffs in plain language. Another candidate was asked how they collaborate with internal teams, and answered with cross-functional examples.
Two candidates were turned down for not having enough experience, one after a long loop that included reference checks and an extra round. That makes level fit worth raising with the recruiter early. Two others described unclear expectations, including an open-ended on-campus strategy question. Learn the team's products and priorities beforehand, and ask clarifying questions about users and goals before you answer. Reports on communication and timing varied, so keep your own notes on next steps. The reports are few, and no two candidates described exactly the same loop.
Synthesized from 4 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
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Upsell Transactions | |
| Top 3 Users | |
| Experiment Validity | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Manager Team Sizes | |
| Size of Joins | |
| Paired Products | |
| Closest SAT Scores | |
| Last Transaction | |
| Longest Streak Users | |
| Subscription Overlap | |
| Button AB Test | |
| Customer Orders | |
| Random SQL Sample | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Google Maps Improvement | |
| Employee Salaries (ETL Error) | |
| Monthly Customer Report | |
| Download Facts | |
| Pre-Launching Shows | |
| Hurdles In Data Projects | |
| Largest Salary by Department | |
| First Touch Attribution | |
| Cyclic Detection | |
| WAU vs Open Rates | |
| Justify a Neural Network |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter screen. One described a fifteen-minute call that walked through the job description and checked fit. Another was contacted through LinkedIn. Use this call to ask which level is being hired and what the later stages will cover.
Candidates report a conversation with the hiring manager or a product team member. One described a thirty-minute remote interview mixing past experience with a case scenario and asking about project count and time split. Another described behavioral questions about motivation, strengths and weaknesses.
This step varied by candidate. One reported a thirty-minute stack conversation with a senior technical team member that was not a coding test. Another reported a take-home case study with three to four days to prepare. Expect to explain your product thinking clearly and defend your choices.
Candidates report presenting to a panel, either virtually after a take-home or in person for about an hour at the San Francisco headquarters. One also had a short preparation meeting beforehand. Panels may probe your approach with follow-up questions, so practice concise answers.
Candidates report onsite conversations with the hiring manager, a sales executive and a VP. Topics included product-led growth, collaboration with internal teams and strategy prompts. One report also describes reference checks and an extra round after a verbal-offer signal, so timing may vary.
