How I Prepared for PM Interviews (Targeting Google, Uber & Co.)
When I decided to seriously prepare for Product Manager interviews, I was targeting companies like Google and Uber.
I knew two things:
- The bar would be high.
- “Winging it” wasn’t going to work.
This post is not an exhaustive guide. It’s simply what actually worked for me — especially what moved the needle the most.
Spoiler: mock interviews.
Step 1: I Treated Prep Like a Product
Before diving into frameworks and question banks, I paused and asked:
- What skills are being evaluated?
- Where am I weak?
- How will I measure improvement?
For PM roles at companies like Google and Uber, interviews usually test:
- Product sense
- Execution / metrics
- Analytical thinking
- Leadership & drive
- Communication clarity
Instead of studying randomly, I mapped my prep to these buckets.
This alone made my prep feel structured instead of chaotic.
Step 2: I Used AI — But Not the Way You Think
AI didn’t replace practice. It accelerated feedback.
Here’s how I used it:
1. Brainstorming partner
When practicing product design questions (“Design a product for X”), I would:
- Draft my answer.
- Ask AI to critique it like a senior PM interviewer.
- Request pushback: “Where is this weak?” “What follow-ups would you ask?”
It forced me to defend my thinking.
2. Generating realistic follow-ups
One mistake I made early: practicing only the first question.
Real interviews don’t stop there.
So I used AI to simulate:
- Edge case challenges
- Metric trade-off questions
- Prioritization conflicts
It made my answers less rehearsed and more flexible.
3. Tightening communication
Sometimes I’d paste a long, messy answer and ask:
“How can I say this more concisely while keeping the structure strong?”
Over time, I internalized cleaner communication patterns.
But here’s the important part:
AI improved polish.
It did not build instinct.
Mock interviews did.
Step 3: Mock Interviews Changed Everything
Nothing — and I mean nothing — improved my performance more than mock interviews.
Here’s why.
1. Real-time pressure exposes gaps
When practicing alone, you feel smart.
When someone interrupts you with:
“Why that metric?”
“Is that really the biggest user pain?”
“What trade-offs are you making?”
You suddenly realize where your thinking is shallow.
I still remember one mock where I confidently proposed a feature and the interviewer asked:
“What would you cut from the roadmap to ship this?”
I had no answer.
That moment hurt — but it permanently upgraded how I approached prioritization.
2. You Fix Communication, Not Just Thinking
In one mock, I spent 8 minutes structuring the problem.
The feedback:
“This was solid, but too slow. In a real interview, you’d run out of time.”
That changed my pacing completely.
Mocks helped me:
- Get sharper openings
- Be hypothesis-driven
- Avoid rambling
- Drive conversations instead of reacting to them
3. Patterns Start Clicking
After ~15–20 mocks, something interesting happened.
Questions stopped feeling random.
“Improve Uber Eats”
“Design a feature for Google Maps”
“Launch a new product in X market”
They all started feeling like variations of the same core muscles:
- Clarify user
- Identify pain
- Prioritize ruthlessly
- Tie everything to impact
That confidence only came from repetition under pressure.
Step 4: I Reviewed My Own Performances Brutally
After each mock, I wrote down:
- Where did I hesitate?
- What feedback repeated?
- Did I drive or react?
- Did I quantify impact?
Patterns emerged:
- I over-explained.
- I sometimes skipped trade-offs.
- My metrics weren’t always crisp.
Instead of fixing everything at once, I picked one weakness per week.
That compounding effect was real.
What Helped the Most?
If I had to rank what mattered most:
- Mock interviews (by far)
- Reviewing and iterating deliberately
- Using AI for structured feedback
- Reading frameworks (least impactful after a point)
Frameworks are useful early.
Mocks are transformative later.
One Anecdote That Stuck With Me
In an early mock, I was asked:
“How would you improve driver retention at Uber?”
I jumped straight into features.
The interviewer stopped me:
“What’s the root cause?”
I hadn’t even defined the problem properly.
From that day on, I forced myself to:
- Diagnose before prescribing
- State assumptions explicitly
- Anchor every solution in a user pain
That shift alone made my answers feel more senior.
Final Thoughts
Preparing for PM interviews — especially for companies like Google and Uber — is less about memorizing frameworks and more about building product instinct under pressure.
AI can:
- Sharpen you
- Stress-test ideas
- Improve clarity
But it won’t replace the discomfort of someone challenging your thinking live.
If you’re preparing right now, my biggest advice:
Do more mocks than you think you need.
Then do five more.
That’s where the real growth happens.
Top comments (0)