Update from June 15 - Recruiter just confirmed that the new process has been rolled out. The six components for the PM interviews are: 1. Product Insights 2. Strategic Insights 3. Analytical 4. Cross-functional collaboration [Sample Questions] ● How do you resolve conflicting product requirements? What or who determines which requirement takes the hit? ● How would you manage through a latent field failure or bug that is directly impacting customers and driving return rates up or support contacts? ● Your largest customer is loudly advocating for a new feature which is not in your prioritized roadmap. Sales, eager to please, have gone straight to Engineering to see if they can drop everything and get this done. What do you do? 5. Craft & Execution [Sample Questions] ● Pick a product of your choice. What are the goals of the product? What’s in your monthly business review deck for the leadership team? ● You are about to launch a new app that is of strategic importance for the company. 1 month out from launch internal Dogfood suggests the app isn't ready (you are below target on several key metrics including CSAT). What do you do? ● Imagine I'm a VC, offering you $20M to build any technology-enabled product/service you'd like. Please walk me through how you would get started? (Problem, Solution, User, Monetize, TAM) ● At what milestone or markers would you look for to determine if a product isn’t performing well and what considerations do you make before you sunset the product? What is the process you would lay out? How do you handle the stakeholders? ---------------------------- Update from June 1 - The new process with an interview panel (including hiring managers) will roll out on June 13th. I'm based in Zurich - not sure if this is the same anywhere else. All interviews after this date will follow the new process. The new guidance on the Crafts and Execution interview that replaces the Technical will be released around June 6th. Does anyone have any further updates? ------ original post ------ I'm due for my second round in June and my recruiter told me that they'll be replacing the Tech (System Design/Algo) with a new interview - Craft & Execution. It's a bit unnerving as I have no idea how to prep for this. What she's told me is that it will include hypothetical scenarios to understand cross-functional collaboration, able to prioritise and execute, evolve a product and technical consideration during launch. She said the dimensions are unknown but this interview is meant to be 'easier'. Does anyone know more about this? I'm not sure how to prep since the Exponent/Product Alliance/all other courses don't quite cover this. Or am I missing something? What would some example questions be - apart from "tell me about a time where a team member wasn't performing" -> or is this more behavioural? #productmanager #pm #google
But system design was ez
What would some example questions be apart from "tell me about a time a team member wasn't performing".... ?
Tell me a time you built something from an idea into a new process or product? Things like that maybe
I hadn’t heard this but actually does sound easier.
When I interview for other jobs, this kind of questions came up - “imagine you are two months away from launch and your engineering team tells you they need 4 extra months to finish. Now what do you do?” Answer should cover all the possible stakeholders that you need to communicate and get alignment with, like eng., sales, marketing, etc. I suspect that it would be questions like this.
Other option: See if there's anything that you can deliver immediately to provide value quickly. Opt for a phased/incremental deployment. Sell it as confirming and testing assumptions and validation of value adds. Then communicate the value to ease the sting of a delay, continue to communicate and align expectations.
Thant is great news, I did mine 2 weeks ago and I passed all positive but technical.. passed to HC but for lower level 😅if I had the chance to have no technical I would do much better
I think I remembered that Google had a product sense, execution, and system design loop. Like one of the example questions I saw was explain how you would build Google docs and they were talking about technical implementation and what were the tradeoffs lol.
technical is the least important round in all kinds. Literally you can screw it up really hard but still land well. In your case, you just give recruiters and google an excuse to downlevel you. But sorry for that happened.
Isn't this just in line with product sense and execution, like Meta? I recall the reason why I was opposed to interviewing for a PM role at Google is because of system design, which tbh I have only limited knowledge in. Rather, as a PM I just need to understand the limitations and tradeoffs to make a decision...
sounds way easier
Is this just another take of RRK?!?!
This should be better than answering system design questions
Do you have technical background? If not, how would you start for sys design interview ? Thanks!