In my last post I described the map I use with PMs to decide what to get better at next. A natural follow-up question is whether getting better on that map also makes it easier to find a good job.
The honest answer is that it only partly does. Being strong across the map makes you a good PM, but interviewing is a separate skill, and a job search involves several things the map doesn’t cover at all. Plenty of excellent PMs interview poorly, and some average PMs interview very well. If you have been doing good work and your search still feels unfair, this gap is usually the reason.
A job search has three parts
I find it helpful to split a job search into three separate questions.
The first part is skill, which is simply how good a PM you are. This is what the mastery map describes.
The second part is visibility, which is how much of that skill a hiring team can actually see during a few hours of interviews.
The third part is access, which is whether you are in front of the right teams, for the right roles, at the right time.
These three multiply rather than add up. A brilliant PM who tells vague interview stories will come across as average, and a strong interviewer who only applies to roles that don’t fit them will collect a lot of polite rejections. So when a search stalls, the most useful question is which of the three is close to zero right now.
Visibility: making your skill easy to see
An interview squeezes months of real work into 45 minutes with a stranger. A product design question tests your product sense out loud and under time pressure, which is very different from making a good decision with weeks of context, data, and colleagues to talk it through with.
The most important thing to understand is that interviewers can only score what you show them. If your stories sound like “we launched X and it went well,” your real skill stays hidden, however good the work was. Candidates who do well have a specific story ready for each part of the map, and in each story it is clear what the situation was, what they personally did, what got in the way, and what changed as a result.
Before the PMs I coach start interviewing, I ask them to build a small story bank. One solid story for each row below is enough to cover most interview loops.
| On the map | A story to have ready | What the interviewer listens for |
|---|---|---|
| Product sense | A time you decided not to build something | How you weighed the user need against other options |
| Execution | A launch that nearly slipped | What you noticed early and what you changed |
| Analytical sense | A metric that moved the wrong way | How you found the real cause |
| Technical sense | A tradeoff you worked out with engineering | Whether you understood the constraint |
| Strategy | A bet you argued for, or against | What you chose and what you gave up |
| Influence | A time you changed someone’s mind | What you said and why it worked |
| Agency | A problem that nobody owned | Whether you waited, or found a way |
The last row deserves more attention than it usually gets. Shreyas Doshi has spoken often about high agency, which he describes as finding a way to get the outcome without waiting for conditions to be perfect. It is hard to claim in an interview, but it is easy to show through a good story.
Telling these stories well is a skill in its own right. It is close to what the map calls influential communication, but it only improves when you practice out loud. You need a clear structure, the right amount of detail, and the ability to notice when the interviewer wants you to go deeper or move on.
There are two more things worth knowing about interviews today. The first is that polished structure counts for less than it used to. In What PM Hiring Managers Actually Screen For, Nikhyl Singhal reports that hiring managers at Netflix, Rippling, and EvenUp now pay less attention to neat case study frameworks, because AI makes them easy to produce. What stands out instead is real research into users, and how well you respond when someone challenges your thinking. The second is that interview loops are noisy. Different interviewers weigh things differently, so a single rejection is rarely a clear verdict on your skills.
Access: getting in front of the right teams
Even with strong skills and good stories, you still need to be in the right conversations. Six things matter most here.
Positioning
Your resume and LinkedIn profile should answer one question clearly: what kind of PM are you? A long list of everything you have done makes you easy to forget. Shreyas Doshi’s 10-30-50 idea is a helpful way to find your answer. He suggests aiming to be in the top 10% in one of the core PM skills, the top 30% in another, and the top 50% in a third.
Your top 10% skill should be your headline. If it is product sense, for example, your resume should open with the product decisions you got right, rather than a list of the meetings and rituals you ran. This connects to Ravi Mehta’s idea of PM shapes: an uneven profile is normal, and a clear one is much easier to hire.
Fit
A great B2B platform PM may struggle on a consumer growth team, and the reverse is just as true. The domain, the company’s stage, and what the team needs right now often decide the outcome more than raw skill does. Singhal makes a similar point in his piece: hiring managers increasingly care about your career path and whether you have worked at a similar stage, sometimes more than direct experience in their domain.
Choosing the role
Taking the wrong job can set you back more than missing the right one. Before you start applying, it helps to write down what you need from your next role, such as the scope, the kind of manager, the stage of the company, and the pay, and then decide which of those you would be willing to trade away. That short list will narrow your search more than any number of extra applications.
Referrals
A warm introduction gets you past the resume screen and usually leads to a friendlier first conversation. According to Singhal, a strong referral works almost like an early reference check, while a weak one counts for about as much as applying through the website. If you don’t have a strong referral, a short note to the hiring manager with a specific, thoughtful opinion about their product is the next best option.
Timing
Hiring cycles, headcount freezes, and how crowded your niche is are all outside your control. Applying steadily over several weeks, rather than all at once, helps even out some of that luck.
Negotiation
Getting the offer is only half the work. Your level, scope, and pay are often negotiable, and the level you start at shapes the next few years of your career. Haseeb Qureshi’s Ten Rules for Negotiating a Job Offer is the most practical guide I know.
Where are you dropping out?
The most useful way to diagnose a job search is to look at where things stop. Each stage points to a different part of the problem.
If you are not getting replies to your applications, the problem is almost never your skill. It is more likely to be how you are positioned, or which roles you are applying for, so start by reworking your headline and asking for referrals.
If you get past screening but keep stopping after the first rounds, your stories probably aren’t showing what you can do. Build the story bank above and practice telling the stories out loud with someone who is willing to interrupt you.
If you reach the final rounds but don’t get offers, that is where depth and fit are tested, and it is also where luck plays the biggest role. Ask for feedback when you can, and look for a pattern across several interviews before you change anything.
If you are getting offers, but for roles you don’t really want, the search itself is working and it is the targeting that needs attention. Go back to your list of what you need from the next role.
A common mistake is to fix the wrong part. People who aren’t getting replies spend weeks practicing case questions, while people who fail in the final rounds rewrite their resume yet again.
Putting it together
The skills map describes how good a PM you are. Your interviewing decides how much of that a hiring team can see, and your search strategy decides whether you are talking to the right teams at all. All three can be learned, and each one deserves its own practice.
If you are in the middle of a search and want help working out which part is stuck, you can book a session with me on ADPList.
References
- Shreyas Doshi, thread of PM frameworks including the 10-30-50 PM (May 2021).
- Shreyas Doshi on Lenny’s Podcast: pre-mortems, LNO, three levels of product work, and high agency (June 2022).
- Shreyas Doshi, Managing Your PM Career, a course on Maven for senior PMs.
- Nikhyl Singhal, What PM Hiring Managers Actually Screen For, Lenny’s Newsletter (April 2026).
- Lenny Rachitsky, How to Interview Product Managers. The hiring side of the table.
- Gayle Laakmann McDowell and Jackie Bavaro, Cracking the PM Interview and Cracking the PM Career.
- Lewis C. Lin, Decode and Conquer: Answers to Product Management Interviews. Useful for practice questions, and best used alongside real mock interviews.
- Ravi Mehta, What’s Your Shape?
- Haseeb Qureshi, Ten Rules for Negotiating a Job Offer.
- My previous post, A Mastery Map for Product Managers.