All Posts

A question like “Should Google offer fine-tuning as a service?” can leave you wondering how you are supposed to approach it. You can see arguments for yes and no, but that still does not tell you how to decide. I think about these questions as bets. Start with the company, not the idea: What is this company trying to accomplish, and what would have to be true for this investment to help it get there? That prompt gives the rest of the answer a direction. First, make a reasonab

At the Director and VP level, a structured, complete product sense answer is only the baseline. Two gaps decide whether it lands: a choice that contradicts an earlier one, and a reason that does not actually support the pick. Here is how to find and close both before the interview.

By the GPM, Director, and VP level, this question is not about which project. It is about what makes one project stand above a whole career, and whether the interviewer leaves convinced you can solve their problem.

Reimagine the product instead of improving it. How to answer a product strategy question like “how would you 10x Google Gemini” at the GPM, Director, and VP level: reframe what the product competes for, generate more than one 10x bet only Google could make, and reason your way to the one to commit to.

How senior product leaders find the crux of a problem and commit before they have the full picture, the real bar in L7 to L9 interviews.

What changes when you interview from L7 to L8, L8 to L9, or into a VP or head of product role, and how to make them feel you already operate at that level.

What companies like Google and Meta evaluate at L7, L8, and L9, why L6 interview prep stops working, and how to get your stories to the right altitude.