Ask questions. Acknowledge answers are 'cool'. Ask more questions. Throw some stuff on the wall. Sign the offer letter. Buy the Porsche. Good stuff and very helpful for interview prep. Thanks for the upload!
I really appreciate these videos! Would love to see more consulting mock case interview videos as well! Thank you for providing this free content to us, you are really making a positive impact on our lives and helping us achieve our full potential.
@@rocketblocks I am under graduate Biomedical Engineer and wanted to know more about product design .I had been doing the prosthetic design of limb course on Fusion 360 interface
in the metrics section 33:20, i think the very reason that Allen chose to prioritize end user engagement vs Kenton thought that percentage of businesses putting in information is the most important, is that from the very beginning Allen has changed the challenge from "helping small businesses" to "user engagement increase." This kind of makes sense to me in terms of what I think a PM does-people all talk about being user-centric but PMs and designers first need to keep their company's product alive right? So did he do the right thing or could this turn into a big issue of steering away from the original challenge? This video is absolutely great and I have learned a lot. thank you for making it.
I really like his structure and his answers, though I think he got off easy at the beginning by choosing Google Maps--a product he is very familiar with as an ex-Googler. If I were the interviewer, I would've pushed him to explore the Problem space--thinking about the kinds of pains businesses experience as a result of COVID and then choosing one to try to solve for. Instead, he tailored the solution to a Product he is very familiar with, and he shone. I guess another way of saying this is, why should Google invest in this project via-a-vis other compelling solutions to problems out there? He didn't answer that question because he latched onto Google Maps as a vehicle to his solution from the get go. As a interviewee, I might be tempted to do the same thing because I can speak intelligently about a product I know. I'd be curious to know if the interviewer would consider this to be a drawback to his approach.
I feel like this might be partly an intentional trick of this challenge. "A product/feature that can help small businesses during covid" is as broad as a challenge can get and can be literally implemented on any product. It gives interviewees the freedom to choose their own level. He could either take a risk and design a whole new product from the ground up, or stick with what he know. And the interviewer knows that. I think I read a note when Allen started to get into specific features he had in mind and it was considered "not very exciting." So he did not shine all the way, but I think he still showed his skills in the most important thing which is the thought process.
Were all of Allen's product ideas generated on the spot, or was there any preparation time? Is there any concern that asking someone to come up with product ideas on the spot leads to half baked ideas? Or is the idea just to see how good and quick a person can think, with relatively little data available at their fingertips?
Awww! this is a super cool and solid interview video that I've ever watched. have a quick question on Metrics. is it the task that especially PM needs to solve for the product design? I'm a product designer, so I'm wondering about whether I should replace the metrics with the *wireframing* or not. btw, this is really helpful content!! much appreciated!!
As a product designer you will have to think about metrics as well. The only difference between this interview and a product designer interview would be how all this information translates into a screen or series of screens.
Very well rounded video. Thank you! Is it true that some interviewers (particularly google) consider using frameworks like the one outlined in the beginning of this video as "robotic" ? Or is it ok to do it casually like you did in this video?
many product interviews I have found online don't cover an MVP. would you advise in favor of this practice? My impression is that there is an expectation for most of the discussion to remain in the problem space.
The starting was pretty boring and slow, but by middle you got to the main point of discussion. MVP could have been presented better - about how you would make it effective using Google Maps.
As much as it may not be as interesting, it is very necessary for Allen to ask the questions and define the requirements for him to really proceed into the actual brainstorming. Jumping into it right away would mean not understanding or defining the problem enough, because everything ties back to the goals and users
Very boring video, I letrally slept off. They have clearly chosen a wrong example. Answer to "What is the feature" should come early in the process andnot going through the whole story.The product interviews should delve into the concept of designing a feature. Instead, the interview gets too deep into the mechanics (probably due to his background and experience with Google Map). The speaking speed is also too fast. One bad mock from RocketBlocks.
it's a scam field full of scammers, so of course the discussion will sound like two hucksters plotting and scheming....and I do have to say, the UX lingo is so cringe, persona, pain point, friction, just lol how sad it is, at least there are 100000000000 layoffs from this bogus industry happening right now and I hope they run this "profession" to the ground with outsourcing and diversity hires. The dummass on the left side of the screen is epitome of scammer. PAIN POINT, muh paint point. Pathetic.
