
Nextdoor Product Manager candidates report behavioral, product sense, analytics and open-ended case rounds, ending with a CPO conversation. Both reports describe friendly interviewers but slow or unclear follow-up.
$194K
Avg. Base Comp
$260K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates who interviewed for Nextdoor's Product Manager role, one of them in mid-2024, describe loops that tested how you think more than what you can recite. One candidate described open-ended case rounds covering ideation around emerging tech, org structure and an ambiguous request, plus a separate exercise. They said the difficulty came from structuring messy problems on the fly rather than from technical depth.
The other candidate described a different shape. A first onsite was mostly behavioral, with detailed walk-throughs of past work, prioritization, cross-functional conflict and shipping under constraints. A second onsite focused on product sense and analytics: define success for a product problem from scratch and explain which metrics you would watch and why. Both reports end with a CPO interview, and both candidates were rejected afterward.
For preparation, keep a few project stories ready that show tradeoffs and conflict, and practice turning vague prompts into a structured approach with clear success metrics. Both candidates found the interviewers friendly and thoughtful. Both also described frustrating follow-up, from slow scheduling to a rejection without specific feedback, so track your own timeline and follow up politely. One reported a total of roughly a month and a half; the other described long gaps between rounds and about three weeks of silence after the final interview. Only two reports exist, so treat the round order as a guide rather than a fixed format.
Synthesized from 2 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 Nextdoor 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 Nextdoor
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| Button AB Test | |
| Employee Salaries | |
| Last Transaction | |
| Subscription Overlap | |
| Ad Comments | |
| Payments Received | |
| Third Purchase | |
| Attribution Rules | |
| Revenue Retention | |
| Underpricing Algorithm | |
| Detecting Firearm Sales | |
| Campaign Goals | |
| Fill Rate Drop | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Experiment Validity | |
| Top 3 Users | |
| Longest Streak Users | |
| Testing Price Increase | |
| User Experience Percentage | |
| Size of Joins | |
| Top Three Salaries | |
| Comments Histogram | |
| WAU vs Open Rates | |
| Employee Salaries (ETL Error) | |
| Google Maps Improvement | |
| Monthly Customer Report | |
| Marketing Dollar Efficiency |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports starting with a recruiter screen and then a hiring manager interview, and described the hiring manager as excellent. Scheduling reportedly needed repeated reminder emails, so you may want to keep your own timeline and follow up proactively.
One candidate reports a first onsite that was mostly behavioral. Interviewers asked for detailed walk-throughs of past work, with questions on prioritization, cross-functional conflict and shipping under constraints. Prepare specific stories with clear tradeoffs.
Candidates report open-ended problems. One was asked to define success and choose metrics for a product problem built from scratch. The other describes cases on emerging tech ideation, org structure and an ambiguous request, plus an exercise. Practice structuring messy prompts and explaining your decisions.
Both candidates report a final interview with the CPO. One said it felt more informational than evaluative, and that references were requested beforehand. Both were rejected afterward, one with no feedback, so avoid assuming a good conversation signals an offer.