Google product manager interview (Design theme park app)

[@IGotAnOfferPM]

Get 1-1 interview coaching and land a PM job at Google, Facebook, Amazon, etc. Browse our coaches: igotanoffer.com/en/interview-coaching/type/tech-interview?KZbin&

[@e.w.6470]

One of the biggest pain points that immediately jumps into my mind is there are so many lines for each ride. Waiting is really painful! Especially in a hot city! Happy to see it's mentioned in debug! Really fantastic answer! no try to force a framework. no rambling like other mock interviews. the question I have is it looks like the pain points apply to all the users. Why do we need to segment users in this case?

[@IGotAnOfferPM]

Happy you found it useful. Yes I think that's a fair point, I think mark segmented because it's generally a good thing to do but wasn't really necessary in the end here.

[@sudarshanvig9222]

Like a lot of folks mentioned already, I think a necessary feature of the MVP ought to be the absence of lines and waiting time. Ideally, it should be like a token system and if your token number is in the next cycle of the ride, there would be a notification (say 10 mins earlier or something). Another feature comes to mind, many older kids and friends have different tastes and want to go on different rides. Have the app in all their phones and track their friends whereabouts at all the time and form groups and do quests and what not!! Thanks for this video though, very helpful!!

[@prashanthn9887]

Very interesting discussion, However i felt one of main pain points which was schedule and timings of various games and events should be present in the app so that people dont miss it, they get constant alerts and reminders based on thier preferences and starring various events

[@shikhajain8341]

One key pain point my parents faced with a curious kid like me was kids getting excited and running away or you let go of their hand for a second and voila you are 1 kid short!! 😂 Locating connected devices should be a feature as well IMO

[@rickadias]

In the segmentation part: my first inclination would be to segment by "roles" instead of age group. Think about: The optimizer guest, the chill guest, the big family, the solo goers, etc. Would that be an acceptable way to segment this problem?

[@IGotAnOfferPM]

I think it could be but it might be a bit ambiguous as what you mean by each role (ie define 'chill guest') so you'd need to explain clearly.

[@aditisharma3108]

I found this video really helpful. One of the most enjoyable and informative video, I have ever seen. Thank you so much for making this.

[@IGotAnOfferPM]

Really glad you found it useful Aditi, thanks for your kind words!

[@rickhouten1622]

Mark is typically really good with these questions. He missed the mission first and also should have clarified if the app is a mobile or a kiosk. Is it supposed to be for companies in Dubai that partner with the park or is it for potential tourists and also tourists who will be visits the park? Very different use cases though he does go into that later

[@joannatarnawska8047]

Great material. I have a question though - you didn't mention people working in the amusement park as a user segment who may have some problems that need to be solved. I feel that this group should at least be mentioned and then maybe not included in the prioritisation stage. What do you think?

[@IGotAnOfferPM]

Hey Joanna, I agree it would be nice to mention them, even if you don't then prioritise their needs.

[@AI-kj7xb]

Is this a Meta/Google PM metre? Who does navigation in the app? Who does navigation in the app for parents holding kids' hands and bags with kid-related stuff? Best way to navigate in the park, same as on the tube or similar spaces, is: maps, special signs and marks on the ground, some interactivity on map stands. The app is for skipping ticket lines in kiosks, buying stuff in advance to save time and plan, and ordering additional services, like in-park rides and so on. Very poor interview. No hire.

[@PGG-o6r]

Hi, thank you for the interview! Very interesting points. I have a question about prioritising. Mark prioritises user segments based on whether they will use the App. But isn't it an upside-down approach? Each segment will use the app in case it solves this User Group's pain points. For example, a Kids Amusement Park App could have tons of minigames, etc.