Problem-solving/product question is something that you'll come across in every PM interview. Here's a way on how shall one approach it. (Not my technique, an amalgamation of the best possible ways) Read the summary again- As I mentioned, the idea is to help on “how shall one the question”. We need to understand that every time the interviewers are not looking just at the solution. It’s how does one reach those solutions also matter. Having said that, I am not trying to undercut the importance of a We will come to this) approach good solution that moves the needle for the product in a significant manner. ( There are different versions of this but broadly these question looks like the one mentioned below: Question Type: What is your favorite app and what would you improve in it? Design an alarm clock for the blind? or Design navigation for the blind Questions asked will be designed to unsettle you and will not something your mind is familiar with. how do you think, strategize, prioritize and design the features Skills being looked for: Again, before we jump into what to do, most important is what not to do Don’ts: Please do not directly jump into solutioning and start throwing solutions features. The features/solutions suggested should not on the lines of visual element changes or an incremental feature. The solution should fundamentally impact the product and its users. Additionally, the feature should have a significant desired impact. (moving the needle) Solving framework: To begin with, always lay out your approach on how you’re going to solve the question. Lay the Approach: First, I’ll discuss the problem in depth to make sure I understand it correctly. Then we can discuss the business situation and our objective in details. Subsequently, I will focus on defining the target user and brainstorming what problems we could solve for them. And lastly, I will try to generate solutions for these problems, prioritize them, and make a recommendation . Sounds counterintuitive, huh? It’s not. The very first thing that you should do is clarify the problems and break them into smaller problems. Always start with the application of the . will be one of the most important skill sets in your gamut. Focus on the problem: first principle The first principles The problem given might seem very obvious but still do clarify every pointer which is not stated. Clarify assumptions: This is a very important step to zero in on what exactly is expected to be solved or achieved. Sometimes we jump into solutions only to be made aware that we aren’t solving the right problems and end up embarrassing ourselves Define the business/product objective: Once we have the simplified problem statements and the business objective, clearly define the target groups for which you’re trying to solve. There can be possibly different segments. In order to keep the solution focussed, choose the target group with a maximum base or the group that can make the most impact Define the target groups: : Explain why the users are/will use the product for. Also, this step really helps in setting up the base for your solutions. Explain in detail, how the current product is faring in addressing those use cases and are there any weak spots. Use cases definition Once we have identified the weak spots, narrow down the weak spot or challenge that you’ll address which shall circle back to the objective by making a significant impact. Narrowing down the weak spots/problems: Suggest all the features that you can think of which can address the weak spots. Among all the features suggested, do pay heed to and explain the order in which these features can be implemented and how. Suggest features to address the weak spots: prioritization Once features are suggested, please highlight the metrics and impact on them. Also, be mindful of the second-order impact analysis of each feature. First and second-order impact analysis: Side Note Sometimes interviewers might give inputs about say which target user to solve for or what particular aspect needs to be addressed. Please do skip steps as per your recognizance. Also, after each step or after a couple of steps, do keep checking with the interviewer if he/she thinks the approach is okay or if there is any feedback. It really helps to keep correcting the way rather than going off track. Previously published at https://nishitraj.substack.com/p/cracking-pm-interview-problem-solving

Target

How To Write a Killer Resume

Subscribe my newsletter

2021 - HackerNoon Contributor of the Year - PRODUCT

Too Long; Didn't Read

CTA: Download the FREE AI Productivity Shift report

Problem Solving Questions During PM Interview

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

How To Write a Killer Resume

10 Ways To Effectively Sell Yourself During A Job Interview

10 JavaScript Interview Questions and Answers to Help you Land Your Next Role

10 Essential Javascript Questions

23 Common Data Science Interview Questions for Beginners

How To Write a Killer Resume

10 Ways To Effectively Sell Yourself During A Job Interview

10 JavaScript Interview Questions and Answers to Help you Land Your Next Role

10 Essential Javascript Questions

23 Common Data Science Interview Questions for Beginners

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps