Walking into a PM interview cold is how you get generic answers. Here's the pre-research I'd actually do.
What I'd study
- Product: core jobs-to-be-done, who pays, what "aha" looks like
- Business model: how they make money; what might be under pressure
- Recent changes: launches, pricing, org news—public info only
- Role clues: JD language about discovery vs delivery vs growth
- Interviewers: LinkedIn for context, not stalker energy
Artifacts I'd build (private notes)
| Note | Why |
|---|---|
| User + problem hypotheses | Fuel for product sense |
| 3 metrics that might matter | Avoid vanity defaults |
| 2 thoughtful questions | Show you're evaluating them too |
| Story bank mapped to JD | Faster behavioral answers |
What I wouldn't do
- Memorize every press release
- Pretend I have insider roadmaps
- Roast competitors with no nuance
- Ignore the company's stage (startup ≠ Big Tech)
Thirty minutes of sharp research beats three hours of shallow scrolling.
Pair prep with durable craft via a PM Certification. More interview hygiene in the newsletter.