Tips & Tricks for Product Sense Questions
These hints apply to any product design/sense case-like questions in a product interview. They are more common with the big guns but also at startups when it gets thrown in between behavioral interviews.
Context
Remember, you only have about 30 to 35 minutes on average to answer the design prompts. You are under the gun to come up with an answer by ruthlessly prioritizing, make decisions on the fly and only giving a quick acknowledgement to many of the things you are glossing over, that is part of the process and what you are getting graded on. The following items are suggested with that in mind.
Tips and Tricks
Clarifying questions - At the very start, ask at least 2 questions or you could be out before it starts. Sample clarifying questions:
Related or Random: For X company or a start up?
Platform: Do you have a particular platform in mind? Mobile? Web?
Location: Should I consider this for X country or Y region?
Level-Set: If super broad topic, make sure you understand the definitions?
Not always digital: Should I design a digital solution or more tangible product?
Frameworks - Let them know how you think. This person listens to at least 3 or 5 of these interviews a week. They are busy. Share your roadmap so they know how you think.
User Identification - This is the crucial setup piece and what could make or break you. Show them how you would identify users. Product managers focus on the user. Show them you can and do think about users all the time.
Bucket: Don’t forget to bucket before listing, if it is a marketplace, identify it as such. (i.e. Buyers vs Sellers. I am going to focus on Buyer Experiences. Drivers vs Riders. Doctors vs Patients.)
Stakeholders: Sometimes there are external parties with influence or impact you should acknowledge but not let distract you. (i.e. anything medical also includes employers and insurers.)
Stump the Candidate - Some like to see if they can catch you off guard or they might be trying to help nudge you in the right direction. If asked a question, take it in and try to figure out what is up.
Can’t read the interviewer - Some will be stoic and give you nothing you can gauge against. Don’t let that throw you off. Be aware. Still act like they are engaged and check to see if they have any input or opinions at the end of each stage.
Don’t get fooled/caught off guard. - The product sense/design question can take many forms. But what they all have in common is that you need to identify users and pain points BEFORE you explore solutions.
Question Types
What is your favorite product?
How would you improve X?
What product do you hate the most?
How would you design an app for X?
Common themes: You need to identify users, pain points, solutions and metrics. The only difference in setup is the clarification you need before jumping in. If you talk about the product you love or hate, you have already answered your own clarifying questions.