Library
Cracking the PM Interview: How to Land a Product Manager Job in Technology · 8 of 11
Cracking the PM Interview: How to Land a Product Manager Job in Technology
Entrepreneurship HIGH

Company Research and Self-Presentation

Cracking the PM Interview: How to Land a Product Manager Job in Technology Gayle Laakmann McDowell & Jackie Bavaro
interview-prep company-research self-introduction pitch

Problem This Solves

Candidates often walk into PM interviews with surface-level company knowledge and generic self-presentations. This leads to answers that fail to differentiate them, questions that waste interview time, and an inability to assess whether the role is actually a good fit. Chapters 10-12 provide a systematic approach to researching a company and structuring every self-presentation question into an active sales pitch.

Key Principle

Research and self-presentation are both sales activities. Company research is not performed to impress interviewers with trivia — it is internalized so answers become more insightful, questions become more meaningful, and mutual fit can be genuinely assessed. Self-presentation answers are not summaries of a resume — each is a structured pitch that connects your background to the specific company and role.

Good Examples

Company research depth (The Role domain): A candidate applying to Amazon researches its frugality value and low-margin business model, then connects these to the PM role by preparing ideas around cost-efficient feature delivery rather than feature volume. This shows integration across the four research domains (product, strategy, culture, role).

Self-introduction pitch: "After three years as a backend engineer I noticed I spent most of my energy convincing the team which features to build, not building them. I moved into APM at [Company], where I launched a map-sharing feature from a hackathon idea that resulted in about a 15% increase in paying users. Outside work I run a tech blog — 200,000 monthly visits, team of ten writers — which keeps me sharp on product trends. I'm here because your mobile growth challenge is exactly the kind of 0-to-1 problem I want to own."

"Why hire you?" using three-part structure: "Three things: I've launched four critical features from scratch, so I know end-to-end PM execution. Second, I've spent five years in fintech, which maps directly to your core user problem. Third, I've read your engineering blog and design principles — the way your teams operate is how I prefer to work."

Spare time answer with concrete evidence: "I run a volunteer program called Teens 4 Animals — I built it from scratch six months ago. We've recruited 50 high school volunteers and helped save over 100 dogs from being euthanized." Concrete outcome, shows initiative and execution, relevant to PM skills.

"Why are you leaving?" — forward-looking framing: "After several years as a development manager I've built deep technology and leadership experience. I now want to take those skills to the product management side, because I really love the experience of launching a new product."

Bad Examples

Surface-level company knowledge: Describing a company as "it makes home automation tools" — this level of understanding is explicitly called out as insufficient. An interviewer expects you to know the product's user sentiment, revenue model, key metrics, and competitors.

Generic "Why do you want to work here?" at a large company: "Google is such an innovative company and I've always admired the culture." Large companies assume candidates want to work there. This answer signals nothing differentiating. Better: passion for the specific team or a concrete experience that makes you a fit.

Disguised-positive weakness: "I work too hard" or "I'm a perfectionist." The book is direct: "The old trick of disguising a positive attribute as a weakness does not work — and probably never has." Interviewers recognize this pattern and it signals either poor self-awareness or dishonesty.

Spare time non-answer: "I'm not sure. I guess I don't really have a ton of true hobbies since I work a lot." Adds no dimension to your profile; misses a brand-building opportunity.

Money or complaint framing for leaving: Citing compensation or criticizing your current employer triggers three concerns — chronic dissatisfaction, disloyalty, and lack of passion.

Interviewer over-research: Referencing a personal detail found online (congratulating an interviewer on a recent marriage) "comes off stalker-ish." Research professional information only.

Key Quotes

  • "A cursory 'it makes home automation tools' level of understanding is not sufficient."
  • "Don't just read this stuff. Formulate an opinion on it." (on company news and rumors)
  • "The point of this knowledge is not to whip it out to impress the interviewer, but to use this information to get a feel for what the company is really like."
  • "Your pitch should be a cohesive story about how you got from then to now."
  • "Don't speak too abstractly. Instead of just saying you did customer research and wrote specs, talk about an example of something important you learned and how you changed the product design based on that."
  • "In general, big companies will be less impressed by your having researched the company... It's better to show a passion for the role/team, or some experience that makes you a good fit."
  • "If you're prepared for it, this question can be a great opportunity. You can use it to tell the interviewer whatever you want about yourself." (on the five-year question)
  • "Sometimes candidates are so focused on landing the job that they forget to make sure the job is really right for them."

Rules of Thumb

  • Research four domains before every interview: product, strategy, culture, and the PM role specifically. All four must be covered — candidates who skip culture or role specifics fail to assess fit and miss behavioral question setup.
  • Use the product yourself. If it has free and paid tiers, try both. Pay attention to anything that would have turned you off as a regular user.
  • The self-introduction pitch should run approximately two minutes (or 1-2x the length of the interviewer's own introduction). Practice out loud, not just in your head.
  • For "Why hire you?", structure the answer explicitly: "Three things..." — this signals strong communication and improves interviewer retention.
  • Prepare exactly three strengths and three weaknesses before any PM interview. Weaknesses must follow the formula: name the real weakness, acknowledge the impact, describe how you compensate or are improving.
  • Prepare enough questions for the interviewer — many candidates run out. Sort them into Useful (role-specific intelligence), Passion (shows research), and Expertise (demonstrates business depth).
  • Never cite money as a reason for leaving or joining. Never complain about a current employer.
  • For the five-year question, use it to volunteer what you are good at and what excites you — treat it as the most open-ended marketing opportunity in the interview.

Related References