Two candidates describe Applied Intuition's PM interviews: screening and behavioral calls, product sense and pricing prompts, wireframing and prioritization cases, and a behavioral round that reached back over a decade.
$189K
Avg. Base Comp
$310K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates describe Applied Intuition's product manager interviews, and neither received an offer. Their accounts differ in format, so treat them as two data points rather than a fixed script.
One candidate reports virtual early rounds followed by onsites made up of multiple product case rounds. They were asked to sketch a wireframe for a product and to prioritize features and defend the order. They describe interviewers who wanted technical depth and fast, clear answers rather than polished slides. The same candidate had an in-person behavioral round with senior engineers and product managers. The questions went back more than a decade, covering college choices and major career decisions. Rehearsing your reasoning for older decisions, not just recent ones, looks worthwhile. This candidate also credits the recruiter with feedback throughout.
The other candidate reports a couple of one-hour screening and behavioral calls, then a pricing question in a round they had been told would be product sense. They also found the recruiter's prep guidance unclear. They were told to expect a remote case study that seemed loosely tied to the role, though they did not reach that stage.
So practice thinking aloud under time pressure, prioritizing with a clear rationale, and handling pricing as a product question. Ask your recruiter exactly what each round covers.
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 Applied Intuition process.
The process felt longer and more disjointed than I expected for a product manager role. I started with a couple of one-hour screening and behavioral calls, which were pretty standard on the surface, but the recruiter was oddly cryptic about what to prepare for. I was told to expect a product sense round, and then the actual interview turned into a random pricing question instead. The interviewer was also late, which set a strange tone, and there wasn’t really any space left at the end for me to ask questions.
What stood out most was how little the process seemed to match the role description. The early calls were conversational and light, with only a few real questions about my past experience, but then I was told to expect a remote case study that apparently had nothing to do with the role I was interviewing for. I never even got that far because the recruiter stopped following up and eventually emailed to say they were moving on with other candidates. Another review I saw described a much longer process with a three-hour case study-style interview, starting with meeting the whole team and then doing 30-minute breakout sessions focused on writing, sales, and project management, so it seems like the later stages can get pretty involved. My main takeaway is to be ready for a pricing-style product question even if you’re told to prep for product sense, and don’t assume the case study will be tightly aligned to the PM role.
Prep tip from this candidate
Be ready for a pricing question framed as product sense, since that was the actual prompt instead of the expected round. Also prepare for a long case-study format with breakout discussions that can touch writing, sales, and project management rather than just classic PM product thinking.
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 Applied Intuition
Diagnose why the pricing algorithm is under-pricing a consumer product
| Question | |
|---|---|
| Empty Neighborhoods | |
| Experiment Validity | |
| 2nd Highest Salary | |
| Button AB Test | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Closest SAT Scores | |
| WAU vs Open Rates | |
| Manager Team Sizes | |
| Find the First Non-Repeating Character in a String | |
| Subscription Overlap | |
| First Touch Attribution | |
| Monthly Customer Report | |
| Size of Joins | |
| Upsell Transactions | |
| Download Facts | |
| Instagram TV Success | |
| Google Maps Improvement | |
| Group Success | |
| Random SQL Sample | |
| Compute Deviation | |
| Bagging vs Boosting | |
| Hurdles In Data Projects | |
| Employee Salaries (ETL Error) | |
| Job Recommendation | |
| Last Transaction |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports a couple of one-hour screening and behavioral calls that were conversational, with only a few pointed questions about past experience. The same candidate found the recruiter's guidance on preparation vague, so asking for round-by-round expectations may help.
One candidate was told to expect a product sense interview but reports receiving a pricing question instead. That is a single report, but it suggests preparing to reason about pricing and value as part of product thinking, and not only classic product design prompts.
One candidate reports virtual early rounds before the onsites. The other was told to expect a remote case study that seemed unrelated to the role but did not reach it, so later-stage formats may vary.
One candidate reports multiple casing rounds onsite. They sketched wireframes for a product and prioritized features, defending the order. Interviewers reportedly valued technical depth and quick, clear thinking aloud over polished slides, so timed practice is likely useful.
The same candidate reports a behavioral round with a mix of senior engineering and product managers. Questions covered major education and career decisions, some more than a decade old, such as college applications and why they chose their school. Prepare specific reasoning for each.
