Job interview preparation system with mock questions and scoring

# Interview Preparation System ## Target: Senior Product Manager at a Series B-D SaaS Startup --- ## Phase 1 — Company Research Checklist (Do This First) Before practicing a single answer, complete this research. It will inform every answer you give. - [ ] Read the company's last 3 blog posts or press releases - [ ] Find the product on G2/Capterra — read 10 recent reviews (note complaints) - [ ] Look up the interviewer on LinkedIn — find shared connections or interests - [ ] Identify their top 3 competitors and what differentiates them - [ ] Check their job postings — what other roles are open? This reveals priorities - [ ] Find their pricing page — understand their monetization model - [ ] Look for the CEO/CPO on podcasts or conference talks (usually on YouTube) - [ ] Read their Glassdoor reviews, especially from PMs — look for patterns - [ ] Check Crunchbase for funding stage, investors, and growth signals - [ ] Try the product yourself — sign up for a free trial or demo **Write a 3-sentence company summary:** What they do, who they serve, and what strategic challenge they're likely facing right now. You'll use this in your answers. --- ## Phase 2 — Behavioral Questions (STAR Format) ### Question 1: "Tell me about a time you had to make a product decision with incomplete data." **Why they ask:** PMs at startups can't wait for perfect data. They want to see your judgment framework. **STAR Template:** - **Situation:** Set the scene in 2 sentences. Name the product, the decision, and the stakes. "At [Company], we were deciding whether to build [Feature X] for our enterprise tier. We had conflicting signals — customer interviews said yes, but usage data on similar features was flat." - **Task:** What was your specific responsibility? "As the PM owning the enterprise roadmap, I needed to make a go/no-go recommendation to the VP of Product within one week." - **Action:** Walk through your decision framework step by step. "I ran a lightweight analysis: 1) Segmented the usage data by company size and found enterprise accounts actually did engage 3x more with similar features. 2) Ran 5 quick calls with churned enterprise accounts to validate the need. 3) Built a one-page business case showing potential ARR impact." - **Result:** Quantify the outcome. "We shipped a scoped v1 in 6 weeks. It became the #2 reason enterprise prospects cited in closed-won deals that quarter, contributing to $340K in new ARR." ### Question 2: "How do you prioritize when everything is urgent?" **Why they ask:** Startups have infinite demands and finite resources. Your prioritization framework reveals how you think. **Template approach:** Describe your actual framework. Good answers reference specific frameworks (RICE, ICE, opportunity scoring) but then explain how you adapt them. Mention stakeholder alignment — great PMs don't just prioritize alone, they build consensus. **Key phrases to include:** - "I separate urgent from important first" - "I align on criteria with stakeholders before scoring" - "I communicate trade-offs transparently — saying no to X means we can ship Y faster" ### Question 3: "Describe a time you disagreed with an engineering lead." **Why they ask:** PM-engineering conflict is inevitable. They want to see you navigate it without pulling rank or caving. **Answer structure:** Show empathy for the engineering perspective, explain how you found common ground through data or customer evidence, and end with a result where the relationship was stronger after. ### Question 4: "What product would you improve at our company, and how?" **Why they ask:** This tests your product thinking AND whether you did your homework. **Preparation:** Actually use the product. Find one real friction point. Structure your answer as: 1. What I observed (specific UX issue or gap) 2. Who it affects (user segment) 3. What I'd propose (solution) 4. How I'd validate before building (experiment or research) 5. How I'd measure success (metric) ### Question 5: "Why this company? Why now?" **Why they ask:** They want to know you're intentional, not spray-and-pray applying. **Answer structure:** Connect your career trajectory to their mission. Reference something specific you found in your research. Show that you understand their stage and challenges. --- ## Phase 3 — Technical / Domain Questions For a Senior PM at a B2B SaaS startup, expect: 1. **Metrics:** "How would you measure the success of [Feature]?" — Always answer with a primary metric, 2-3 supporting metrics, and one guardrail metric. 2. **Estimation:** "How many daily active users does [Competitor Product] have?" — Walk through your logic out loud. The answer matters less than the reasoning. 3. **SQL/Data:** "If I gave you access to our database, how would you find out which users are at risk of churning?" — Describe the query logic conceptually. Mention cohort analysis, engagement frequency decay, and feature adoption patterns. 4. **Roadmap:** "Walk me through how you'd build a roadmap for Q3." — Describe your input-gathering process, stakeholder alignment, and how you balance new features vs. tech debt vs. quick wins. 5. **Pricing:** "We're considering adding a new pricing tier. How would you approach this?" — Mention willingness-to-pay research, competitive analysis, value metric identification, and A/B testing the pricing page. --- ## Phase 4 — Questions to Ask the Interviewer These are ranked by how much they reveal and how much they impress: 1. "What does the product development process look like from idea to shipped feature? Where does it break down?" — Shows you care about the system, not just the role. 2. "If I were to start this role on Monday, what would be the most important thing to ship in my first 90 days?" — Shows you're already thinking about impact. 3. "What's one thing about the product strategy that the team disagrees on right now?" — Shows you're comfortable with ambiguity and conflict. 4. "How does the PM team interact with customer-facing teams like sales and support? Is there a structured feedback loop?" — Shows you think about the full information ecosystem. 5. "What does the ideal candidate for this role look like? What would make someone wildly successful vs. just good?" — Lets you address any gaps in real-time. **Never ask:** Salary (save for HR/recruiter), "What does the company do?" (you should know), vacation policy (looks like you're planning time off already). --- ## Phase 5 — Common Mistakes at Senior PM Level 1. **Talking about features instead of outcomes.** Junior PMs say "I built X." Senior PMs say "I drove Y result by shipping X." 2. **Not quantifying impact.** Every story needs a number. Revenue, conversion rate, time saved, NPS change — something concrete. 3. **Rambling past 2 minutes per answer.** The STAR format should take 90-120 seconds. If the interviewer's eyes glaze over, you've gone too long. 4. **Being too humble about your role.** "The team did it" is generous but unhelpful. Be clear about YOUR specific contribution. 5. **Not asking clarifying questions.** When given an ambiguous prompt, asking "Can I clarify a few things first?" shows PM instincts. --- ## Self-Evaluation Rubric (Score Each Mock Answer 1-5) | Criteria | 1 (Weak) | 3 (Adequate) | 5 (Strong) | |----------|----------|---------------|------------| | **Structure** | Rambling, no clear format | Has a beginning and end | Clean STAR, concise, logical | | **Specificity** | Vague, hypothetical | Some details, some vague | Named the product, team, metric | | **Quantified Impact** | No numbers at all | One soft metric | 2+ hard metrics with context | | **Role Clarity** | Unclear what you did vs. team | Somewhat clear | "I specifically did X" | | **Relevance** | Doesn't connect to the role | Somewhat relevant | Directly maps to their needs | | **Time** | Over 3 minutes | 2-3 minutes | 90-120 seconds | **Scoring:** 24-30 = Ready to interview. 18-23 = Practice more with a friend. Under 18 = Rework your stories from scratch. Record yourself answering each question. Listen back. You'll catch filler words, tangents, and moments where you lose confidence. Fix those before the real interview.