After talking to several product managers (PMs) and understanding the interview process, it was evident to me that getting the right job wasn’t going to be easy. Several aspects of the process were a mystery to me (and some still are!). This post highlights my learnings from preparing for interviews and accepting the position of a Product Manager - New Grad at Yelp.
I started looking into the companies I was interested in. I researched the mission, values, skills the company looked for, whether I would be a good culture fit, product growth and whether their mission resonated with me.
In all, I scheduled more than 100 mock interviews through the Slack community during my internship and full-time job search. The interviews usually lasted for 1 hour and 15 minutes comprising of two 30 minute long interviews where each individual took turns to interview the other followed by 15 minutes of feedback. I usually found questions to ask on Glassdoor. I tried to make it a two-way interaction by asking questions, taking pauses and often checking if they were following.
To my surprise, I learned a great deal by interviewing other people. I found it helpful to take note of what I liked about the interviewee and tried to incorporate those strategies into my own. This helped me develop a keen eye for product design, come up with creative ideas and pay attention to detail.
I suggest that you try to do at least 5 mocks for each category of questions (elaborated below). This practice will help you think on your feet, build muscle memory and tackle unexpected follow-ups in the interview. Don’t hesitate to do mock interviews even when you feel less confident about your preparation. I cannot emphasize enough the utility of mock interviews. This will allow you to identify what truly differentiates you from other candidates. To find partners for mock interviews, I signed up for the PMInterview Slack team and reached out to friends and school alumni.
Product Design Questions
Product design is one of the most important PM interview question categories. I started by preparing my own framework - a modified version of the popular CIRCLES method. You should stick to what works best for you.
In order to empathize with the user in question, I define a good mix of user personas in the beginning and then describe their demographics, values, and characteristics. I think of people I already know while outlining the personas. Several resources on building user personas are available online. I particularly like the IDEO ones.
The personas need to be complemented with unique and creative ideas. I read technology blogs like Stratechery, subscribe to newsletters like Springwise and listen to podcasts like Exponent to help me with that. Being aware of market trends and competing products in the market made the task of coming up with good ideas easier. I also practiced wire-framing solutions with designer friends of mine. This makes it easier to explain to the interviewer what the solution looks like and ensure that both of you have the same idea in mind.
Products You Like/Dislike Questions
I picked five products I liked and five I didn’t. For each product, I brainstormed the user personas, what utility it serves, its shortcomings and how it can be improved. Before interviewing with a particular company, focus on its products along with a few others.
I applied this process to different classes of products: apps (such as LinkedIn and Google Trips), services (such as supermarket checkout) and physical products (such as wearables).
After identifying qualities that the company cares about, I prepared a spreadsheet with those qualities along the rows and past experiences along the columns. I referred to the company’s website and Amazon leadership principles to fill the rows. Then, I filled the cells with a few stories from my past experiences highlighting those qualities, in the STAR (Situation, Task, Action, Result) format.
I practiced my pitch in front of the mirror and with my friends. I wasn’t able to complete the spreadsheet in one iteration. Talking to friends and colleagues helped in discovering qualities and remembering incidents I hadn’t thought of. Stories should be authentic otherwise the delivery makes it evident that they are either rehearsed or made up. Additionally, I kept a 30-second and a 2-minute ‘About Me’ pitch handy.
Usually, one of the interviews is dedicated to evaluating the candidate’s analytical ability. It is essential to have your metrics game on point. My strategy is to define the key actions that the user needs to perform (such as upload a picture or save an article) and then describe how this can be best measured using the available data. In order to focus on the primary metric, I eliminate all that aren’t actionable.
Being prepared for statistical questions about A/B testing and usage experiments helped me tackle the rare curveball. I read Lean Analytics (by Alistair Croll and Benjamin Yoskovitz) and PM Interview Questions to have a strong understanding of product metrics. I also spent time on SQL for questions pertaining to the actual computation.
Problem Solving Questions
I practiced for these by breaking the problem into smaller problems and solving for each subpart separately to come up with the overall solution. I developed a framework to fall back on for problem-solving questions. The examples in the book PM Interview Questions are a good representation of what to expect.
Be prepared for typical technical questions such as ‘What happens when you type google.com in the browser?’ and ‘How would you explain machine learning to a 5-year-old?’. You could also be asked system design questions like ‘How would you go about designing Twitter?’ and ‘How would you design a Google search type-ahead?’. I also studied how scalability is ensured by different companies on highscalability.com and practiced questions on Gainlo and Interview Bit. For coding questions, I studied Leetcode and did a few mock interviews on Pramp.
The most critical piece of advice I got was from a friend of mine who told me to not just be prepared but to be over-prepared. I have now realized that is what gives you confidence during the interview. As Louis Pasteur said ‘luck favors the prepared mind’!
Rohan Katyal is an incoming product manager at Yelp in the data products team. Presently, he is a human-computer interaction graduate student at Georgia Institute of Technology. Previously, Rohan worked as a product management intern at Yahoo (now Oath), as a research associate at INRIA Sophia Antipolis Méditerranée and as a mentor at Google Summer of Code. He holds a degree in computer science from IIIT Delhi.