I got in through a referral, and a recruiter reached out. I went through a more generic L6 PM loop. The process itself was streamlined: recruiter screen, one PM screen, then a four-round final covering behavioral, product design, analytics, and strategy. The whole thing felt very Google in the sense that it was generic rather than team-specific, but the follow-up pressure was higher than I expected and there really felt like there was no room for error. I didn’t get the L6 offer.
I applied right before the Google APM application closed, got in through a referral, and tried to make my resume read a lot more product-focused without completely rewriting my background.
The process for me was one first-round product design interview, then five second-round interviews, then a 72-hour take-home and a final presentation with a PM. The interviews felt pretty traditional PM overall, mostly product vision, analysis, strategy, and judgment, and not especially AI-heavy outside of one Gemini-style prompt.
A few interviewers definitely pushed on weak spots and made me pivot, and one round felt rushed enough that I basically had to deliver my answer in one shot. Google gave me no feedback at any stage, but I ended up getting the offer.
I was honestly surprised to even get the Google and DeepMind interview, and the process ended up being much lighter and more ambiguous than I expected. After a very standard recruiter screen, I had two short calls: one with the hiring manager that was mostly background, interest in AI, and a light product or growth prompt, and one with a partner on a sister team that mixed behaviorals with a very open-ended "Gemini usage is down" case. I had prepped like crazy for a much tougher consulting-style case and a deeper data exercise, so I left feeling very neutral, not like I crushed it and not like I bombed. One frustrating part was that there was basically no time to ask my own questions, so I learned almost nothing from the interviewers about the real mandate of the role. In the end they told me I was very qualified and they enjoyed the conversations, but I got rejected before moving to the assignment round.
I got in through a referral for an L7 PM role on NotebookLM inside Gemini. The process included a recruiter screen, a conversational hiring manager deep dive, and an on-site split into two phases: first, product design and execution; then, technical system design and a leadership behavioral.
The unusual part was a live-coding section during the product design round, where I had to prototype the thing I had just proposed, and most of the pushback was about how I prompted and reprompted. Overall, it was one of the most practical AI PM loops I have done, and it matched what the recruiter told me almost exactly. I made it to the final round but did not get the offer.
I did a recruiter call, then a PM phone screen, then an async take-home, then a virtual onsite with about three interviews. The whole loop was more open-ended than I expected and mixed classic PM questions with consulting-style cases. The onsite interviews were blended, and the interviewers interrupted throughout to push deeper. The take-home was a slide deck on designing an app for people moving to a new city, and it was reviewed async with no presentation or follow-ups.
It was calm, they just wanted to see how I think etc. They were heavy on product sense, and how you look at their exisiting products. Also weighing on if you could be a senior pm
The process was smooth. First round was a mix of product solutioning and code evaluation. Recruiter screen was easy too , had to walk through the resume basically.
The interview was challenging and required me to think deeply about my product decisions and experiences. I enjoyed the level of detail and the directness of the conversation. I felt well prepared by the recruiting team, and the interview gave me a good opportunity to discuss real product problems and the reasoning behind my decisions.
The interview was comparable to other interviews for product management and cross-functional roles, with a strong emphasis on relevant experience, analytical thinking, and communication. It provided a good opportunity to demonstrate how I approach product challenges and work with different stakeholders.
The process is very unpredictable because I had one question where I was tested for strategic insight where I was asked very generic question about vision for agentic applications in infra. And then then I had a question on hardware strategy, including Android. And then I had a very vague question on success metrics. Um, I think Google processes very... um, while they test for a specific set of metrics, it is very unpredictable.
The overall interview process consisted of four stages: an initial recruiter screen, two domain-specific technical rounds, and a final behavioral interview with the leadership team.
What went well
Communication from the recruiting team was proactive and transparent. Expectations for each round were clearly outlined in advance, and the interviewers were highly engaged. The case study round was a standout experience; it felt less like a rigid assessment and more like a collaborative whiteboard session, allowing for a genuine exchange of ideas and a clear view into the team's working dynamics.
What didn’t go well
There were noticeable scheduling bottlenecks between the technical rounds and the final leadership interview, stretching the total timeline by an unexpected two weeks. Additionally, during the technical presentation, the primary video conferencing platform experienced severe connectivity drops. This disrupted the flow of the discussion and required us to switch to an audio-only fallback, making it difficult to present visual data effectively.
The process was long and hard, I prepared A LOT. The interviewers were mostly nice and positive. The recruiter was very helpful.
The hiring manager provided an overview of the team's structure, mission, and the open PM role. I shared my background and drew relevant connections to the team's focus area. The conversation included a brief informal problem-solving discussion around product success metrics and go-to-market strategy for an open-source developer platform. The call concluded with alignment on next steps, including onsites.
I had prepared well with product sense, and had a good understanding of how ML algo's work, that instilled a lot of confidence in me.
Having a clear structure and a lot of clarification questions helped with articulating my thoughts.
- What algorithm will you use for recommendation of Google Maps?
- Design a feature to improve Google Classroom.
Product Manager
Screening round with product design question on Google Maps and Apple Maps
Product Manager
30 min over Google meet
1 additional behavioral question
Overall, this was one of the more rigorous interview processes I've been through, but also one of the most organized. The recruiter was transparent about the interview stages, what each round would focus on, and even shared preparation resources ahead of time, which I really appreciated. Their guidance ended up being quite accurate, so I felt I knew what to expect at a high level.
What went well was that every interviewer seemed genuinely interested in understanding how I think rather than just looking for the "right" answer. Most of the conversations felt collaborative, and when I explained my assumptions or reasoning, interviewers often engaged with them instead of immediately moving on. I also appreciated that several interviewers shared context about the team, their own work, and how the role contributes to the business, which made the conversations feel more balanced.
recruiter was helpful and gave accurate pointers on what to expect. They also try to set expectations wrt timing
Product Manager
1. Recruiter Screen (30 min).
Background, motivation, product experience, culture fit.
2. Product Sense (45 min)
Example: “How would you improve YouTube’s recommendation algorithm?”
Focus on users, problems, solutions, and metrics.
3. Data & Metrics (45 min)
Analyze drops in watch time, design A/B tests, interpret engagement signals.
4. Execution & Trade-offs (45 min)
Prioritization, stakeholder alignment, handling legal/ethical concerns.
5. Behavioral / Leadership (45 min)
Conflict resolution, failures, influence without authority.
Final round = 4–5 back-to-back interviews covering strategy, analytics, and collaboration.
Product Manager
I had a recruiter call followed by a discussion with the HM.
During the HM round, she asked me:
- A system design question
- An estimation question.
- A behavioral question.
The conversation was structured but conversational. The design and estimation questions required structured thinking and clear communication, while the behavioral question focused on ownership and decision-making.
After this round, I received a rejection email along with feedback.
Product Manager
I interviewed for a mid-level Product Designer position. The entire process took about 3 weeks and consisted of four stages.
1. Recruiter screening (30 minutes)
This was mostly about my background, previous experience, salary expectations, and why I was interested in the company. Pretty straightforward.
2. Hiring manager interview (1 hour)
We discussed my portfolio in detail. They asked me to walk through 2 case studies, focusing on decision-making, trade-offs, and measurable impact. They were especially interested in how I approached user research and validated assumptions.
Product Manager
It was an online interview round where they tested on product sense
The process was rigorous, and they clearly expected a high standard of technical knowledge even for a PM role. My recruiter was awesome and really helped move the process forward.
The process included an initial recruiter screen followed by two APM-style interviews focused on product sense, analytical thinking, and execution. I felt strong on the product design and user-focused questions, but I could have been more structured and quantitative when discussing metrics and tradeoffs.
- Work through improving a product
Online application, then technical product manager interview, where I had to talk them through improving a selected product.
Product Manager
Applied through my MBA program and was assigned a final round directly.
Completed my first interview out of 3 of the final round.
Product Manager
1. Recruiter screen round - Expectations on role, pay and location
2. Product Design Round - 45 mins
3. Product Strategy Round - 45 mins
4. Product Design Round - 45 mins
Product Manager
First round interview with a PM at Google. 40 minutes. One question only
Product Manager
1. Recruiter Call (Informational)
2. Hiring Manager Round (Product Sense/Design)
3. Final Round (Three Interviews: Product Execution, Analytics and Strategy)
Product Manager
The interviewer has just gave an brief introduction about his role and introduction & then asked me to introduce my self later on gave an question to brainstorm
Product Manager
Product design, execution! Chill conversation, one behavioral in the beginning.
Product Manager
45 min screen with PM, asked this question and behaviorals
Product Manager
A 45 Min Phone call with a top recruiter! It was an interview with a gritty analysis.
Associate Product Manager
The first round of Google APM program in which they asked more about me and my background.
Few pieces of advice:
1. Try to keep your interview in the morning (it will help both you and the interviewer) and don't ever have it around lunch time.
2. Don't have your interview in non working hours (non 9-5) as you'll get a PM from different nation and then there is a chance that he might not know your country numbers or apps (a little disadvantage)
3. Use stories in your answer wherever possible, it's a must! Practice this habit more.
4. If your interviewer asks you about the same thing twice, it means you need to pivot and update your answer. It's a hint from the interviewer so that you can give a better answer.
5. Always summarize your answer e.g. repeat the problem statement and the final points so that both of you are on the same track.
6. Prepare some good questions to ask e.g. what product are you working on, what is expected from an APM. Don't ask the interviewer for feedback, ask the hiring manager for the feedback.
Product Manager
Product Manager
Product Manager
The interviewer was more in listening mode, Didn't nudge towards a direction.
The interview process moved very quickly overall, which I appreciated because it kept momentum high and reduced uncertainty between stages. Communication from the recruiting team was generally responsive, and scheduling was efficient despite the number of rounds involved.
- Walk me through your resume
- Which behavior looks more like you?
- Design a vending machine.
Product Manager
Product Manager
Truly enjoyed the experience, the interviewer was very kind and nudged me a couple of times to double click on a particular solution, was selected with strong hire grade.
Product Manager
Product Manager
The overall process was spread across months making it challenging to keep up with constant preparation. I was able to ace the product design, analytics and execution questions. I could have done better in the cross functional round.
Regular case questions, but took too long. Made final round and then team matching went on for months, until I finally pulled out.
Product Manager
Product Manager
I went through 5 rounds for a Senior PM role: a recruiter screen, a hiring manager call, then three virtual on-sites covering Product Sense, Analytical/Metrics, and Googleyness/Leadership, followed by a cross-functional interview with an engineering partner. The whole process took about 5 weeks from initial outreach to offer.
What went well: The recruiter was communicative throughout and gave clear prep guidance before each round, which helped me calibrate expectations. The Product Sense interview felt collaborative — the interviewer built on my ideas rather than just grading me, and I appreciated that the analytical round used a real, de-identified product problem rather than an abstract puzzle.
What didn't go well: Scheduling took longer than expected between the hiring manager call and the on-site loop (about 10 days), which created some uncertainty. I also found the case interview time pressure tight — 45 minutes wasn't quite enough to fully structure and solve the prompt, so I'd have appreciated a few extra minutes to synthesize a recommendation at the end.
My process started with a talent screen with the recruiter and quickly moved to a hiring manager interview. They then scheduled me for a full loop on a tight timeline as I was far along with another offer. I had 4 interviews in the full loop and after those 4 rounds I was notified by the recruiter that I'd passed and was going for review with a hiring committee, a week later I was told I was going to get the offer.
Product Manager
What went well was my effort and organization. What didn't go well was time management. Next time, I would start earlier and ask for help sooner if I needed it. What stands out to me is how well this role matches my background and goals. The interview has also given me a good sense of a professional and supportive team culture.
It was a very long process. Got to Team matching phase, but wasn't able to match after several tentatives. The rounds after the full loop (where I got mixed rating) were harder than the techinical ones.
Product Manager
Product Manager
Interviewer was very professional. Asked followup questions to the case. Cut me off at the end and said the CEO walked into the elevator and asked for the 2 minute pitch.
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager
Product Manager