IMO, most of these PM interviews feel very monotonous and script-like (CIRCLES method!). Before going into users, success metrics, etc, I would also like to understand why does the company want to get into this? Is it an established firm or a new startup? Why does the company feel it can create a strong product to bridge the gap? What is the scope of the project - is it a digital discovery platform, an addon product or even a physical solution? What are the existing solutions and why they do not work effectively enough to solve the problem? Once, we have an idea - we can look at who will be first 10/100/1000 users? What pain-points can be tested through a quick and dirty MVP? How can we learn from our MVP and decide on persevere/pivot/kill?
great questions. I just get started on production sense questions for my data science interview. Every instruction is teaching us a similar framework, like clarify the scenario and metrics, bugs, segment by user behaviors or platforms, other features in the same company, etc, and then summarize. Your questions make me feel like jumping out the box which is very refreshing and interesting. But I have this funny thought that if I ask interviewer these questions, this might sounds like an interview for the interviewer. Hahaha.
Would love to know from experienced PMs: How much of interview success translates to job success? Its often called the HR paradox - the skills needed to get the job aren't always (or even complementary to) the skills needed to actually do the job.
Following thoughts Common User segment - users who changed their jobs and their insurance has changed and looking for a new doctor. This could be common besides those who move to a new location Major pain point is not only figuring out if the doctor is capable and trustworthy for whatever condition I’m looking for but also is in-network or out of network, the associated costs for in-network / out of network or no insurance at all EHR / EMR - Ease of Data transfer from previous doctor to new doctor can be good consideration when someone is searching and if that information is provided for user to make decision. This lack of access to prior medical records and history is major pain point in my opinion
I liked where she was going with demographc/identity, but the alumni affiliation seems weak. When searching for a doctor you want to know specialty so you know if they can serve your need, coverage by your insurance, and where they are among other things.
the biggest challenge with watching these public videos is that you are not sure of the quality and you discover that when invest that time which is scarce for PMs. Can exponent also share a link of the summary of the solution. User can just go thru that and then take a call whether to watch the video or not
So the third solution is that when I need a doctor , I enter in a app what sort of doctor I need and then just put on my watch and keep strolling in the city in hope that one day my smart watch will buzz and then my medical problem will get looked at . Did I miss something ?
Kevin/stephen, SWE focus on developing specific skills and move between product areas and build different products but many tend to pivot around one or 2 languages or types of work. Do you think 'PM as a skill' is similarly generalized or should one start with a domain where one is experienced as you think of a PM career? In this example, would the best outcome for product development be hiring a person from Health tech industry? I see this in some Cloud PM job reqs - the need to have enterprise experience.
Can someone help with the approach to solve this? 1. We are a classified for cars. 2. We have a PWA website in a particular market, say Mexico 3. We are deciding if we should launch an app. 4. How should we arrive at a conclusion whether to launch app or not. or how to size this opportunity?
Use analytics to check if the website is being opened more on desktop browsers or on mobile browsers. Second, ask users to fill a short survey like.. 1. if they are okay with Email newsletters or they want push notification in their mobile. 2. Ask questions if they would be okay to receive 5-10% discounts (example) if they use mobile apps. Since you already have a PWA, it can be cheaper to make a Hybrid mobile apps.
I am assuming you already have a functioning website and want to monitor the health of the website and the business First step would be track and monitor - Conversion rate: people visiting the websites vs sales - Split between the new and existing customer to understand if you have enough new customer visiting the website - Also page/marketing flow: homepage > product > payment > successful/failed order This would help in understanding the missing links in the website and if you don't find anything there, you can always ask feedback/survey on - Product variety - price point - ease of use of website - competitor etc
You create user segments when the needs of the user segments are distinct and cannot be solved by a single product. I don't see the needs of the segments called out by the interviewee being distinct at all. I think a better approach would have been to consider patients and doctors and maybe insurance providers as distinct user segments. Otherwise, this is a pretty poor interview.
Don't leave your product management career to chance. Sign up for Exponent's PM interview course today: bit.ly/3NBc87B
IMO, most of these PM interviews feel very monotonous and script-like (CIRCLES method!). Before going into users, success metrics, etc, I would also like to understand why does the company want to get into this? Is it an established firm or a new startup? Why does the company feel it can create a strong product to bridge the gap? What is the scope of the project - is it a digital discovery platform, an addon product or even a physical solution? What are the existing solutions and why they do not work effectively enough to solve the problem? Once, we have an idea - we can look at who will be first 10/100/1000 users? What pain-points can be tested through a quick and dirty MVP? How can we learn from our MVP and decide on persevere/pivot/kill?
great questions. I just get started on production sense questions for my data science interview. Every instruction is teaching us a similar framework, like clarify the scenario and metrics, bugs, segment by user behaviors or platforms, other features in the same company, etc, and then summarize. Your questions make me feel like jumping out the box which is very refreshing and interesting. But I have this funny thought that if I ask interviewer these questions, this might sounds like an interview for the interviewer. Hahaha.
Would love to know from experienced PMs: How much of interview success translates to job success? Its often called the HR paradox - the skills needed to get the job aren't always (or even complementary to) the skills needed to actually do the job.
kevin is staring into my soul
Seriously 😂😂😂
Following thoughts
Common User segment - users who changed their jobs and their insurance has changed and looking for a new doctor. This could be common besides those who move to a new location
Major pain point is not only figuring out if the doctor is capable and trustworthy for whatever condition I’m looking for but also is in-network or out of network, the associated costs for in-network / out of network or no insurance at all
EHR / EMR - Ease of Data transfer from previous doctor to new doctor can be good consideration when someone is searching and if that information is provided for user to make decision. This lack of access to prior medical records and history is major pain point in my opinion
Take a shot whenever Kevin blinks
Looks like he wants to murder someone.
@@snafu4714 11:01
The interviewer is quite robotic!! The discussion has to be lively... though the interviewee was making it better!
he has plenty of paralinguals anyone can pick up on.
Thanks!
I had trouble following what problem she was trying to solve and what the product would be
I liked where she was going with demographc/identity, but the alumni affiliation seems weak. When searching for a doctor you want to know specialty so you know if they can serve your need, coverage by your insurance, and where they are among other things.
the biggest challenge with watching these public videos is that you are not sure of the quality and you discover that when invest that time which is scarce for PMs. Can exponent also share a link of the summary of the solution. User can just go thru that and then take a call whether to watch the video or not
Thanks for the feedback! We'll look into it 👀
Interview didn’t have very strong user behaviors. Imo not everyone grows up with a doctor or has insurance through their life.
There are many other user buckets, e.g. people switching insurance providers or immigrants just arriving in the US.
how are their needs any different from people moving to a different location ?
i thought the interview started off really well ,but her pain points were not good.
So the third solution is that when I need a doctor , I enter in a app what sort of doctor I need and then just put on my watch and keep strolling in the city in hope that one day my smart watch will buzz and then my medical problem will get looked at . Did I miss something ?
Another customer bucket is with the 4th one she mentioned "dont like" but also looking for a second opinion
Also those physicians that have retired or moved to another area/clinic/other and left the patient
This answer doesn't take into account immigrants and people who've moved from a different state and have no "parents" around
Kevin/stephen, SWE focus on developing specific skills and move between product areas and build different products but many tend to pivot around one or 2 languages or types of work. Do you think 'PM as a skill' is similarly generalized or should one start with a domain where one is experienced as you think of a PM career? In this example, would the best outcome for product development be hiring a person from Health tech industry? I see this in some Cloud PM job reqs - the need to have enterprise experience.
Can someone help with the approach to solve this?
1. We are a classified for cars.
2. We have a PWA website in a particular market, say Mexico
3. We are deciding if we should launch an app.
4. How should we arrive at a conclusion whether to launch app or not. or how to size this opportunity?
Use analytics to check if the website is being opened more on desktop browsers or on mobile browsers.
Second, ask users to fill a short survey like..
1. if they are okay with Email newsletters or they want push notification in their mobile.
2. Ask questions if they would be okay to receive 5-10% discounts (example) if they use mobile apps.
Since you already have a PWA, it can be cheaper to make a Hybrid mobile apps.
I am assuming you already have a functioning website and want to monitor the health of the website and the business
First step would be track and monitor
- Conversion rate: people visiting the websites vs sales
- Split between the new and existing customer to understand if you have enough new customer visiting the website
- Also page/marketing flow: homepage > product > payment > successful/failed order
This would help in understanding the missing links in the website and if you don't find anything there, you can always ask feedback/survey on
- Product variety
- price point
- ease of use of website
- competitor etc
I love her!
bring ux researchers & designers
You create user segments when the needs of the user segments are distinct and cannot be solved by a single product. I don't see the needs of the segments called out by the interviewee being distinct at all. I think a better approach would have been to consider patients and doctors and maybe insurance providers as distinct user segments.
Otherwise, this is a pretty poor interview.
she doesn't make much sense
she will be great PM
lol
Not selected
Awesome