How Customizing Your Interview Prep Gives You an Unfair Advantage
I embarrassed an interviewer and cleared a product interview. Not intentionally, of course.
TL;DR: Generic interview prep gets generic results. Before every interview, find out who the interviewer is, what skills will be evaluated, and how long the round is. Customizing your preparation to the context, the round, and the person gives you an edge that frameworks alone cannot.
The Story
Recently I was speaking with someone preparing for an upcoming product interview. They were doing the usual: practicing frameworks, revising concepts, preparing answers to common questions.
I asked them three questions:
- Who is the interviewer? What is their role?
- What skills will be evaluated in this round?
- How long is the round?
They did not know the answer to any of them.
This is surprisingly common. Most candidates treat every interview round the same way. But preparation changes dramatically when you know these details.
The Interview That Started with a Blush
At that point, I shared a story from one of my own interviews.
Before the interview, I looked up the interviewer on LinkedIn and found that she had presented at a global product conference a few months earlier. The talk was about building product culture in engineering-heavy organizations. It was actually quite good.
When the interview started, I casually mentioned: "I was just watching your conference presentation before this interview."
Her face immediately turned pink. With a slightly embarrassed smile she said, "Oh dear..." Apparently she did not like her own presentation very much.
We shared some chuckles and the atmosphere instantly became relaxed. Instead of a rigid Q&A session, we had a genuine discussion about product thinking. She asked me about my approach to building product culture, I referenced a point from her talk, and the conversation flowed naturally.
I cleared the round.
Now, I did not look up her profile to find a conversation starter. I looked it up to understand what she cares about, what her background is, and what lens she might use to evaluate me. The conversation starter was a bonus.
Why Generic Prep Falls Short
Interview preparation is often treated as something generic. Practice RICE, revise the double diamond, prepare your "tell me about a time" stories. These are necessary, but they are table stakes. Every other candidate is doing the same thing.
The problem with generic prep is that it optimizes for the average interview, not the specific one you are about to walk into. And interviews are never average. Each round has a different evaluator, a different focus, and a different dynamic.
Consider the difference:
Generic prep: "I should be ready for a product sense question."
Customized prep: "The interviewer is a Director of Engineering who moved into product two years ago. This is a 45-minute product sense round. They probably value technical depth and systems thinking more than market analysis. I should lead with how I think about technical trade-offs."
Same round, completely different preparation.
The Three Things to Learn Before Every Interview
1. Who is the interviewer?
Get their LinkedIn profile if possible. Look for:
- Their current role and how long they have been in it
- Their career path (engineering to product? consulting to product? lifelong PM?)
- Any public content they have created (talks, blog posts, podcasts)
- Shared connections who might give you context
This is not about stalking. It is about understanding the lens through which you will be evaluated. An engineering-background PM will notice different things than a business-background PM.
2. What skills will be evaluated?
Ask the recruiter directly. Most companies will tell you. Common round types:
- Product sense: How you think about user problems and solutions
- Execution: How you prioritize, plan, and ship
- Leadership: How you influence without authority, handle conflict, drive alignment
- Technical: How you work with engineering, understand systems, make trade-offs
- Strategy: How you think about market positioning, competitive dynamics, long-term vision
Knowing the round type lets you prepare the right stories and frameworks. Preparing a leadership story for a product sense round wastes your best material.
3. What is the duration?
A 30-minute round and a 60-minute round require completely different pacing. In 30 minutes, you need to be concise and structured from the first sentence. In 60 minutes, you have room to explore, ask clarifying questions, and build a narrative.
Duration also tells you the depth expected. A 30-minute product sense round probably wants a structured framework answer. A 60-minute one might want you to go deep on one aspect.
How to Use This Information
Once you have these three pieces, your preparation becomes targeted:
Tailor your stories. If the interviewer has a data science background, lead with how you use data in product decisions. If they are a designer turned PM, emphasize user research and design thinking.
Adjust your depth. For a technical round with an engineering manager, go deeper on architecture and trade-offs. For a strategy round with a VP, stay at the business level.
Prepare your opening. The first two minutes set the tone. A relevant comment about the interviewer's work, the company's recent launch, or the team's product area shows you did your homework. It also makes the conversation feel less like an interrogation.
Anticipate their questions. An interviewer who recently shipped a marketplace product will probably ask marketplace-related questions. An interviewer who writes about metrics will probably probe your measurement approach.
The Bigger Point
The best candidates do not just prepare better answers. They prepare for the specific conversation they are about to have. They walk in knowing the context, the evaluator, and the format. This lets them be genuinely present in the conversation instead of mentally cycling through rehearsed answers.
That is how you win against the odds. Not by knowing more frameworks, but by knowing more about the situation you are walking into.
And sometimes, you accidentally make the interviewer blush. That works too.
Your resume is the first thing interviewers see before the conversation starts. Make sure it tells the right story. Score your resume and see how it reads through a hiring manager's lens.