Product managers, I'm about to say something that might frustrate you. Frameworks don't get you offers. I know, you spent weeks studying STAR.
You've got circles memorized for product sense. You can rattle off rice for prioritization, ARR for metrics. You have a library of acronyms ready to deploy at any moment, and you're still not converting your interviews.
Meanwhile, someone else, someone less prepared than you, sometimes with less experience, walks into a room, same interview, and gets the offer. And you're left thinking, "Hey, what framework are they using that I'm not? " And here's the answer.
It's not a framework, it's a frame, and there's a massive difference. Look, I've coached over a thousand product managers through job searches, career transitions, and on average, our clients get anywhere from 35% to 85% compensation increases. And previously, I was a product manager at Google for years, and before that, led product at three startups.
And the single biggest unlock that I see, bigger than any framework, bigger than any storytelling technique, bigger than any amount of mock interviews, is the moment a product manager stops performing and starts showing up with the right frame. Today, I'm going to break down what a frame actually is, why it matters more than any framework, and how to build one that makes interviewers lean forward before you even get to your first answer. So, let's dig into it.
Let's start with the first really critical point, the 90 second verdict. Here's something I need you to understand, and it might be uncomfortable. The interviewer has largely decided how they feel about you within the first 90 seconds of the interview.
Not after your best STAR story. Not after your product sense walk-through. Not after the case study.
In the first 90 seconds. This is not just my opinion. This is psychology.
Research on thin slicing. Look it up. The work from Nalini Ambady at Harvard shows that people form pretty reliable judgments about competence, confidence, and likeability within seconds of meeting someone.
And in high-stakes evaluations like interviews, those initial impressions don't just influence the rest of the conversation, they shape it entirely. Now, once the interviewer forms the first impression, everything that follows gets filtered through it. If they read you as a peer, someone calm, authoritative, someone they could see leading a product team, then your answers get the benefit of the doubt.
They lean in. They ask follow-ups because they're genuinely curious. They mentally start making the case for why you should get hired.
But if they read you as a candidate, someone nervous, overeager, someone who really needs this job, then the exact same answers get heard differently. The interviewer's polite, look, they nod, but they're evaluating, not engaging. They're looking for reasons to confirm what they've already sensed.
Same person, same resume, same stories, completely different outcome because of the first 90 seconds. And here's what matters. Those 90 seconds have almost nothing to do with any of the frameworks you're going to use.
They have everything to do with the frame you walk in with. So, let's talk about what is a frame and exactly why it eats frameworks for breakfast. Let me define this because I see this word used a lot, like the frame word, and I want you to really understand it.
A framework is a structure for organizing your thinking and your answer. STAR is all about situation, task, action, result. CIRCLES gives you a framework for product sense.
These are tools. They're useful, and I'm not telling you to throw them away. Look, they are required, but a frame is a psychological container you bring into the room.
It's the invisible posture underneath everything you say. It determines whether your star answer sounds like a senior leader reflecting on a hard-won lesson or nervous candidate hoping that they, you know, gave the right response. And here's the simplest way I can explain it.
Two directors walk into the same interview. Same company, same role, same interviewer. First person opens like this.
The interviewer says, "Tell me about yourself. " Director A takes a breath, their energy shifts slightly forward, they speak too fast, they start listing their resume. So, I've been in product for 12 years.
I was at company X where I did this, then company Y where I did that. They're thorough, they're accurate. They're signaling one unmistakable thing.
I need this to go well. Please like me. Director B opens differently.
Same question. Tell me about yourself. But Director B pauses for a second.
Not a long pause, just enough to signal that they're choosing what to say, not scrambling to say any everything or anything. They open with a hook. One sentence that frames their entire career around the problem this company is trying to solve.
Their voice is steady. Their pace is measured. They make eye contact.
Everything about their energy says, "I'm here because I think this could be a great fit for both of us. Let's find that out. " Same question, same amount of experience, wildly different frame.
Director A is in a supplicant frame. They're auditioning. The interviewer is the judge and they're the performer.
The power sits entirely on one side of the table. Director B is in a mutual evaluation frame. They're having a conversation between two professionals exploring whether this is the right match.
Their power is shared. And here's the thing that really kills me. Director A might actually have better answers, better frameworks, their star stories might be more polished, their product sense structure might be tighter, but it's just not going to matter because the frame ate the framework.
The stronger frame always absorbs the weaker frame, always. If you walk in with a weak frame and a perfect framework, the framework gets undermined. If you walk in with a strong frame and an okay framework, the frame carries you through.
Such is life. And this is exactly why some people get hired and can't explain exactly what they did differently. It's why other people prefer 200 hours and can't figure out why it's not working.
Now, let me get specific. I see three frames over and over in the product managers who come to me after failing to convert. And I want you to check yourself against each one.
Let's start with the first one, the audition frame. This is the most common one. You walk in thinking this is a test, I need to prove myself, they're going to evaluate me, and I need to pass this.
I really need to pass this. When you're in the audition frame, everything you do is oriented towards one thing, getting the interviewer's approval. You watch their face for micro reactions.
You adjust your answer mid-sentence if they look a little confused. You add extra content because you're not sure if you've said enough. You overexplain because your survival brain is telling you that more information equals more safety.
Justin came to me after 9 months of interviews. Senior PM, 7 years of experience, strong companies on his resume. He'd made it to the final rounds at four companies, had been rejected for all of them.
And you know what the feedback always was? We went with someone who was a stronger fit. Not you gave wrong experience, not that you lacked experience, stronger fit, which is the code for someone else felt more like one of us.
Justin's frameworks were fine. His stories were competent, but his frame was audition. He was performing for the panel instead of talking with them like you would talk with a colleague.
Every answer had the subtle energy of, "Did I get this right? " And that energy made him forgettable. And in a competitive process, forgettable loses.
When we rebuilt the approach, the tactical work mattered, you know, structuring the stories, adding drama, elevating the language to principle level, but the frame shift was what made it all work. He stopped auditioning and started leading the conversation. He owned his accomplishments instead of rushing through them like he was embarrassed.
Three offers in six weeks, all at principal level, 41% compensation increase. The company that hired him said he was the most compelling candidate we've ever interviewed. That's what the right frame produces.
Not just competent answers, compelling presence. But that also brings me to frame number two, the impostor frame. This one is quieter but just as destructive.
The impostor frame isn't about nervousness. It's about a deep belief that you don't belong in the room. Maybe you don't have Fang on your resume and everyone else does, or you think everyone else does.
Maybe you've pivoted from engineering and you're not sure if you're a real PM yet. Maybe you were laid off and you've internalized that as a judgment on your ability. Whatever the source, the impostor frame produces a specific behavior, hedging.
I think we could maybe consider doing this. I would probably suggest, in my experience which is somewhat limited in this area, this is what we should do. You're hedging your communication.
Every edge is your frame leaking into the conversation. The interviewer doesn't hear humility, they hear uncertainty. And uncertainty at those senior levels, that's disqualifying.
Nora was a strong product manager who'd been laid off from a startup. She had the experience for staff level, but she was applying for senior roles because her impostor frame was telling her she wasn't ready for staff. Think about that.
She was literally targeting a lower level because her frame, not her framework, not her experience, told her she didn't deserve more. When we challenge that and started she started interviewing at the staff level with a frame that said I belong here, she landed a staff PM role in less than three months. The skills were always there, the frame was the blocker.
And then there's the pleaser frame. This is the one that senior PMs are most susceptible to and least likely to recognize. The pleaser frame is when you unconsciously or subconsciously orient every answer towards what you think they want to hear.
The interviewer mentions they care about data-driven decisions, suddenly every one of your stories become about data, even the ones that were actually about intuition and judgment. The interviewer asks about a failure, you give them a failure that's really a success in disguise, because your pleaser frame can't tolerate the vulnerability of an actual failure. You know, I work too hard, I care too much, those sort of things.
The problem with the pleaser frame isn't that it feels spectacularly, it's that it produces answers that are technically fine, but they seem to lack that conviction. The interviewer can sense that you're in some sense shape-shifting. You're not telling them what you actually think.
You're giving them a version of yourself calibrated to what you think they think they want. And that at the senior level, that reads like a lack of leadership. Leaders have a point of view.
They listen, they adapt, but they walk in with a perspective. The pleaser frame walks in with a mirror. What do you want?
I'll give you exactly that. And look, if you're watching this and recognizing yourself in one of those frames, I want you to know something. The frame is not who you are.
It's a pattern, and patterns can be changed. That's exactly what we do, starting with a strategy session with my team. We diagnose the frame that you're operating in, show you what it's costing you, and help you figure out how to get past that.
Click the link below, book a call with my team, and then continue watching the rest of the video. Now, let me tell you how to actually build the right frame, because knowing about frames isn't the same as having one and getting to the right one. I need to be clear about something.
I'm not telling you to pretend to be confident, to fake it till you make it. I'm not telling you to act like you don't care about the outcome. That's a different kind of performance, and interviewers can also smell that instantly.
Building a real frame is structural, not theatrical. It's about creating the conditions where confidence is a natural output, not something that you have to like manufacture. There are three things that build a real frame, and they happen before you walk into the interview.
First, your hook. This is where the frame starts. Not with a deep breath, not with a power pose, but with the first sentence of your mouth where they say, "Tell me about yourself.
" Most PMs answer that question like they're reading a timeline. "I did my undergrad in engineering. I started company X where I did this.
Then I went to this company. " And they're going on for 15 minutes. It's accurate.
And it's the single worst way to start an interview because it puts the interview in the position of trying to figure out why the hell should they care in the first place. A hook flips that. A hook is one sentence that tells the interviewer exactly what you are about and why it matters to them.
It's the thesis statement of your candidacy. Here's a difference. Timeline opening.
"I've been in product management for 12 years. I started in Oracle in the enterprise platform team. Then I moved to series B startup where I ran the core product.
And most recently, I was director of product at a mid-size SaaS company. " Okay. Hook opening.
"I'm a product leader. My specialty is turning around struggling B2B product. I've done that three times in my career.
Last time was a product that was losing market share and I rebuilt the strategy to get it growing again. Let me walk you through one of those examples. " Now you walk them through that example.
Now I suddenly care about it because you're talking about it in my terms. What problems do I have and how you can help solve those? It's just look, it's the same person, same experience, but the hook opening does something that timeline can't.
It tells the interviewer what to listen for. It creates a frame. This is someone who solves hard problems.
This is someone who works with struggling teams. This is someone who solves a real problem that I care about. every that follows gets heard through that lens.
Your hook is not just an introduction. It's a frame-setting device. It's the first move in establishing that you're a peer, not an applicant.
If you get it right, the rest of the interview is simpler because the interviewer is no longer evaluating whether you're qualified. They're exploring whether you're the right fit. And those are very different conversations, by the way.
Second, your conviction stories. Most PMs prepare stories to answer questions. That's the framework approach.
You have a bank of star stories organized by category, you know, leadership, conflict, failure, data-driven decisions, and you pull the right one for each prompt. Cool. You've learned those answers, you deliver it.
The frame approach is different. Instead of stories that answer questions, you prepare stories that demonstrate who you are as a leader. Stories where you had a strong point of view, you made decisions where you being there mattered, where you made a call that wasn't obvious and it worked, where you disagreed with someone powerful and held your ground.
These are conviction stories. They do something frameworks can't. They show the interviewer that you have a spine, that you're not going to be a PM who just executes what they tell you to do, that you think independently, you act decisively, and you can react to data, you can react to changing situations.
When one of my clients, Justin, rebuilt his stories, you know, he had to add specificity, he had to add drama, but the work around the frame was choosing stories where he led, not where he executed, not where he shipped a feature, but he influenced the CEO to change company strategy, where he built a team from the ground up, where he made the hard call. It was all about choosing the right stories first and foremost so that his frame would get established. Because look, the stories you choose signal the frame you want to operate in.
If every story positions you as the one who did the work, you're in a contributor frame. That's okay. But if your stories position you as the one who made the decision and shaped the direction, you're in a leadership frame.
Same experience, different frame. And third is the mutual evaluation mindset. This is the deepest one, and this is the one that makes the other two work.
Most product managers walk into interviews with the asymmetric power dynamic in their head. They have something I want. I need to convince them to give it to me.
That's the default frame, and it poisons everything. The mutual evaluation mindset says, "We're both here to figure out if this is the right match. I'm interviewing them as much as they're interviewing me.
I want this to work, but I don't need it to work. And if it doesn't, well, that's information. That's redirection.
That's a temporary failure if you even want to call it that. Now, I know what you're thinking. Easy to say when you have options.
I've been searching for 6 months and this is the only real interview I've got. Look, I hear you and I'm going to be real with you, especially because I've seen the situation so many times with so many of my clients. This is where the mindset work is hardest and this is where it matters the most because the mutual evaluation frame is easy when you have a lot of options, but it's actually not about having options.
It's about knowing your value independent of any single company's decision. It's about understanding that your career is a long game and no single interview is the whole story. One of my clients, Deepak, came to me 5 months into the search.
Savings running low. He told me flat out, "I'll take anything at this point. " And that frame was destroying him.
We worked on shifting from I need them to I'm mutually evaluating. That wasn't just a mindset exercise. We rebuilt his relationship with his own accomplishment.
We reminded him of the real value he brought. We created actual options, pushing multiple conversations forward simultaneously so no one single interview carried the weight of his entire career. Multiple offers later, 25% higher comp later, he stopped reaching things out in desperation, you know, he Compensation was 25% higher than what he would have accepted in desperation.
Same person, same experience, different frame. Now, here's why I'm so adamant about all of this. Your frame is not one piece of your interview performance.
It's the container for every other piece. Your hook only works if it comes from a place of authority, not anxiety. You deliver a perfectly crafted hook with a pleaser frame, it sounds rehearsed.
If you deliver it from a mutual evaluation frame, it sounds like a leader introducing themselves. Your stories only land if you tell them with conviction. The same story told from audition frame sounds like you are hoping the interviewer is impressed.
Told from a leadership frame, it sounds like you're sharing a lesson you learned. Even your questions at the end, those are frame signal. In a audition frame, you ask questions designed to show the interview that you did your research.
In a mutual evaluation frame, you ask questions because you genuinely need the answers to make your decision. The interviewer can feel the difference. Think of it this way, your framework is the sheet music.
Your frame is how you play it. And anyone who's ever been to a concert knows that you can have two musicians with exactly the same piece. One makes you feel something and the other one it's like, yeah, they're going through the motions.
They're okay. It's not the notes, it's the presence behind the notes. See, very importantly, fix the frame first, then the frameworks have something solid to sit on.
Let me bring this together for you. If you've been prepping for interviews and the results aren't matching the effort, I want you to consider something. It might not be a framework problem.
It might not even be interview skills problem. The interviewer decides in the first 90 seconds whether you're a peer or a candidate. That decision gets made by your frame.
Not your star story, not your product sense structure, not the number of mock interviews you've done. Three frames that get product managers rejected. The audition frame, the imposter frame, and the pleaser frame.
Each one undermines everything that comes after it, no matter how polished your answers are. Three things that build the right frame, your hook, the first sentence that tells the interviewer who you are and why that matters to the interviewer, your conviction stories, narratives that demonstrate leadership, not just execution, and the mutual evaluation mindset, the deep understanding that you are assessing them as much as they're assessing you. Your frame is the container, your framework is what goes inside it.
And the PMs who understand this, the ones who fix the frame first, they're the ones who walk out of interviews and hear, "You're the most compelling candidate we spoke with. " Not the most prepared, not the most experienced, the most compelling. And that's what the right frame produces.
If you want help building your frame, this is core to what we do. Book a strategy session with my team now, the link's in in description. We'll diagnose the frame you're operating in right now, show you what it's costing you, help you figure out how do you get to that next level to show up as the leader you already are.
We've helped over 1,000 product managers land roles at Google, Meta, Salesforce, Amazon, Stripe, Coinbase, and beyond. Average compensation increases 35% or more. Book your session now, and if you want to go deeper on neuroscience behind why your brain defaults to survival mode in interviews, watch this next video where I break down exactly what's happening to your nervous system and how to fix it.