Tell me about a time in your career when you faced ambiguity.

"It was a mix of behavioral and hypthetical questions. The behaviroal part I was good at I think, but the hypothetical part it took me too long to answer and I was probably not confident enough, also some answer I gave was not clear and straightforward"

"The process took some time to schedule, they made a mistake and scheduled a day where my behavioral interviewer did not show up."

"The whole process was really fast for me, about three weeks end to end, and the ads org was super snappy about scheduling and responses. The recruiter reached out because my background lined up with what they want, and it felt obvious from the start that this team cares a lot more about ads domain fluency than generic big tech interview performance. I had a recruiter screen, a TTL cache phone screen, and then a five-round onsite with one coding round, two behavioral EM rounds, data modeling, and system design. The technicals were mostly straightforward if I could talk through tradeoffs, but the behaviorals were a much harder vibe check than I expected. I am still waiting to hear back, but the biggest thing I took away is that if I can speak confidently about how ads serving, demand, targeting, and capping actually work, they will forgive more than they would at other companies."

"I got into the loop through a backdoor-ish hiring manager route instead of a cold apply, and for L4+ I had to have a soft match with a team before the loop even started. My process was a recruiter alignment call, the GHA questionnaire, one phone screen, two onsite technicals, and a standard Googliness behavioral. What stood out was how collaborative and non-LeetCodey it felt, especially the phone screen, which was basically a live algorithms conversation that pushed on first principles instead of rehearsed patterns. I also learned that Google is doing more team matching before hiring committee now, because a hiring manager's statement of support can strengthen your packet if one round is only lean hire. I ended up accepting because the interview experience was consistently positive and honestly much better than how Google interviews are usually portrayed online."

"I went through a very Amazon-style process for a Senior Product Manager L6 role: recruiter screen, hiring manager, then several additional rounds. The whole loop was heavily centered on leadership principles and past work examples, and honestly every round felt pretty consistent in structure. The biggest thing that felt newer was the AI layer on top, where they asked how I had used AI at work and how I integrated it into product development to drive innovation or simplification. I did not find it especially tricky in the sense of on-the-spot problem solving, but they absolutely expected crisp storytelling and strong follow-through on metrics. The toughest part was being ready for sharp follow-ups on why I made certain decisions and how I arrived at the numbers I used."