Create comprehensive PM interview preparation plan.
Target company: [FAANG/startup/specific company]
Interview timeline: [weeks until interview]
PM experience: [years, type of products]
Weak areas: [product sense/execution/estimation/behavioral]
Role level: [APM/PM/Senior PM/GPM]

Generate study plan with:
- Product sense case practice schedule
- Execution framework mastery
- Estimation problem practice
- Behavioral story preparation
- Company product research
- Metrics and analytics prep
- Technical knowledge review
- Week-by-week milestones

Structured PM prep roadmap.

My situation: [paste details]

Generate product sense interview question.
Difficulty: [APM/PM/Senior PM level]
Product type: [consumer/B2B/platform/marketplace]
Question style: [design/improve/new feature]

Provide product sense question:
- Problem statement (clear scenario)
- Context (company, users, goals)
- What interviewer wants to see
- Success criteria
- Common mistakes
- Framework to use
- Time allocation

Product thinking practice.

Level: [paste your level]

Review my product sense case answer.
Question: [problem given]
My answer: [approach I took]
Framework used: [if any]
Time spent: [actual time]

Critique covering:
- Problem clarification (did I ask right questions?)
- User understanding (empathy shown?)
- Solutions proposed (creativity and feasibility)
- Prioritization logic (sound reasoning?)
- Metrics defined (success measurement)
- Trade-offs considered (mature thinking?)
- What I missed
- How to improve answer

Improve product thinking.

Answer: [paste my response]

Generate PM execution/strategy case question.
Difficulty: [PM/Senior PM level]
Scenario type: [roadmap/metrics/go-to-market/growth]
Product context: [type of product]

Provide execution case:
- Situation description
- Business goals
- Constraints given
- What to deliver (roadmap/strategy/plan)
- Stakeholders involved
- Success metrics
- Evaluation criteria

Execution planning practice.

Focus area: [paste preference]

Generate estimation/analytical interview question.
Type: [market sizing/revenue/user growth/etc.]
Difficulty: [APM/PM/Senior PM]
Industry: [tech/consumer/B2B]

Provide estimation question:
- Problem statement
- What to estimate
- No calculator (mental math)
- Reasonable assumptions needed
- Order of magnitude acceptable
- What interviewer evaluates
- Common mistakes

Fermi problem practice.

Type: [paste preference]

Review my estimation problem approach.
Question: [problem to estimate]
My approach: [steps I took]
My answer: [final number]
Assumptions made: [what I assumed]

Critique covering:
- Approach structure (clear logic?)
- Assumptions reasonableness
- Math accuracy
- Order of magnitude check
- What I missed
- Better approach
- How to communicate in interview

Improve analytical thinking.

Solution: [paste my work]

Prepare to discuss product metrics in interview.
Product type: [consumer app/B2B SaaS/marketplace/etc.]
Metrics category: [growth/engagement/retention/monetization]
Role level: [PM/Senior PM]

Cover metrics thoroughly:
- North Star metric (what matters most)
- Supporting metrics (pyramid)
- How to measure (instrumentation)
- What good/bad looks like (benchmarks)
- Trade-offs between metrics
- How to diagnose issues
- A/B testing approach
- How to communicate with data

Metrics fluency demonstration.

Product: [paste context]

Prepare behavioral interview answers for PM role.
Role level: [APM/PM/Senior PM/GPM]
Company type: [FAANG/startup/enterprise]
My background: [PM experience summary]

Generate answers for:
- "Tell me about yourself"
- "Why PM? Why now?"
- "Describe a successful product launch"
- "Conflict with engineering/design/stakeholder"
- "Product failure and learning"
- "Influencing without authority"
- "Prioritization under constraints"
- "Data-driven decision example"

STAR method formatted.

Background: [paste details]

Prepare to discuss product strategy.
Product: [specific product or general]
Strategic question: [growth/competition/pivot/expansion]
Context: [market, competitors, constraints]

Strategy discussion covering:
- Market analysis (opportunity sizing)
- Competitive landscape
- User needs evolution
- Business model considerations
- Strategic options (multiple paths)
- Recommendation with rationale
- Risks and mitigation
- Success metrics

Strategic thinking demonstration.

Context: [paste scenario]

Prepare for technical PM interview questions.
Technical depth needed: [light/medium/deep]
Product type: [mobile/web/backend/ML/etc.]
My technical background: [CS degree/bootcamp/self-taught/non-technical]

Cover technical topics:
- APIs and system architecture (basic understanding)
- Database concepts (when to use what)
- Mobile vs web trade-offs
- Technical feasibility assessment
- Engineering collaboration
- Technical debt discussions
- How to prioritize technical work
- Communicating with engineers

Technical credibility building.

Background: [paste technical level]

Practice product critique for interview.
Product to critique: [app/feature/company]
Critique depth: [UX/business model/growth]
Role perspective: [PM viewpoint]

Structure critique covering:
- What the product does (understanding)
- Target user (who it's for)
- What works well (positive first)
- What could improve (constructive)
- Opportunities missed
- Competitive positioning
- Monetization assessment
- How you'd prioritize improvements

Thoughtful product analysis.

Product: [paste product name]

Practice prioritization framework explanation.
Framework: [RICE/Value vs Effort/Kano/ICE/other]
Context: [when you'd use it]
Example: [real scenario]

Explain framework thoroughly:
- What it is (framework description)
- When to use (appropriate situations)
- How to apply (step-by-step)
- Pros and cons (honest assessment)
- Real example (your experience)
- Stakeholder communication
- Adaptation for context

Framework fluency.

Framework: [paste which one]

Prepare to discuss product roadmap planning.
Product context: [what product]
Timeline: [quarterly/annual]
Stakeholders: [eng/design/leadership/customers]

Roadmap discussion covering:
- How you gather input (sources)
- Prioritization approach (framework)
- Timeline planning (sprints/quarters)
- Balancing new vs maintenance
- Technical debt allocation
- Stakeholder alignment process
- Communicating roadmap
- Adapting to changes

Roadmap planning mastery.

Context: [paste scenario]

Prepare GTM strategy discussion for interview.
Product: [what's launching]
Target market: [who we're selling to]
Competition: [market landscape]
Resources: [team size, budget]

GTM strategy covering:
- Target customer segments
- Positioning and messaging
- Launch channels (how to reach users)
- Pricing strategy (if applicable)
- Success metrics (what indicates success)
- Launch timeline (phases)
- Risk mitigation
- Post-launch plan

Launch strategy demonstration.

Product: [paste context]

Prepare to discuss user research approach.
Research question: [what you need to learn]
Product stage: [discovery/validation/optimization]
Resources: [researchers available/DIY]

Research discussion covering:
- Research goals (what to learn)
- Method selection (qual/quant/both)
- Participant recruitment
- Research execution
- Insight synthesis
- How insights influenced product
- Balancing research with speed
- When to skip research

Research-driven PM discussion.

Context: [paste scenario]

Prepare to discuss product failure or setback.
Failure: [what didn't work]
Context: [why it happened]
Learning: [what you learned]
Recovery: [what you did next]

Frame failure constructively:
- Honest acknowledgment (own it)
- Context and constraints
- What went wrong (analysis)
- What you learned (specific lessons)
- How you recovered (resilience)
- What you'd do differently
- Growth demonstrated

Failure as growth story.

Failure: [paste situation]

Prepare collaboration stories for PM interview.
Teams worked with: [eng/design/marketing/sales/etc.]
Challenge: [collaboration difficulty]
Approach: [how you handled it]
Outcome: [results achieved]

Collaboration stories about:
- Building consensus (getting alignment)
- Resolving conflict (disagreements)
- Influencing without authority
- Managing up (leadership alignment)
- Working with difficult stakeholders
- Unifying team around vision
- Celebrating team success

PM leadership demonstration.

Experience: [paste examples]

Prepare competitive analysis discussion.
Your product: [what you're building]
Competitors: [key players]
Market: [industry context]

Competitive analysis covering:
- Competitor strengths/weaknesses
- Your differentiation (what makes you different)
- Market positioning
- Feature parity assessment
- Strategic threats
- Opportunities in market
- How to win (competitive strategy)

Competitive awareness.

Market: [paste context]

Research [Company Name] products for interview.
Company: [target company]
Their products: [key products]
Your role: [which product you'd work on]

Research strategy:
- All products understanding (portfolio)
- Main product deep-dive (use it extensively)
- User reviews analysis (what users say)
- Competitive positioning
- Recent product changes (shows you're current)
- Improvement opportunities (your ideas)
- Questions about their roadmap
- Why you're excited about their product

Product knowledge demonstration.

Company: [paste name]

Practice articulating product vision.
Product: [what you're envisioning]
Timeline: [3-5 year vision]
Market: [who it serves]

Vision articulation covering:
- Current state (where we are)
- Vision state (where we're going)
- Why this matters (impact)
- How we'll get there (high-level strategy)
- Who it serves (users benefited)
- Success looks like (future state)
- Inspiring but realistic

Visionary leadership demonstration.

Product: [paste context]

Prepare data-driven decision story.
Decision: [what you decided]
Data used: [metrics/research/tests]
Analysis: [how you analyzed]
Outcome: [results of decision]

Data story covering:
- Problem identified (what needed solving)
- Hypotheses formed (possible solutions)
- Data gathered (what you measured)
- Analysis conducted (how you interpreted)
- Decision made (what you chose)
- Results achieved (outcome)
- Learning (what data revealed)

Data fluency demonstration.

Story: [paste example]

Generate smart questions to ask PM interviewer.
Company: [target company]
Role: [position]
Interview stage: [which round]
Interviewer role: [PM/engineer/leadership]

PM-specific questions showing:
- Product strategy curiosity
- Team dynamics interest
- Decision-making process questions
- Success metrics understanding
- Growth opportunities
- Product challenges exploration
- Customer obsession
- Culture of experimentation

Thoughtful PM questions.

Context: [paste details]

Prepare PM portfolio case study presentation.
Product: [product you PM'd]
Your role: [what you owned]
Problem: [what you solved]
Impact: [results achieved]

Case study structure:
- Product overview (what it is)
- Problem statement (why it mattered)
- Your role (what you owned)
- Process (how you approached it)
- Key decisions (critical choices made)
- Challenges overcome (obstacles)
- Results (metrics-driven outcomes)
- Learnings (what you'd do differently)

Compelling PM case study.

Product: [paste details]

Prepare to explain what PMs do (meta question).
Your PM philosophy: [your definition]
Your strengths: [what you're good at]
Your approach: [how you work]

PM role explanation covering:
- Core responsibilities (what PMs do)
- How you define success (metrics)
- Relationship with eng/design (collaboration)
- Decision-making approach (how you choose)
- Why you chose PM (career motivation)
- What makes great PM (your beliefs)
- Your PM style (how you operate)

Role understanding demonstration.

Philosophy: [paste your view]

Generate complete mock PM interview set.
Company: [target company]
Role level: [APM/PM/Senior PM]
Interview type: [product sense/execution/behavioral]

Create realistic interview:
- Warm-up questions (2-3)
- Main case question
- Follow-up questions
- Metrics discussion
- Trade-off exploration
- Behavioral questions
- Time estimates per section

Full interview simulation.

Interview: [paste details]