Как пройти собес с PM

Зачем это знать

PM — your primary stakeholder как product analyst. Interview с PM тests fit — how вы'd partner. Technical skills matter less; product thinking + collaboration — more.

На product analyst собесах PM round — common.

What PM оценивает

1. Product thinking

Understand users, features, metrics.

2. Collaboration potential

Would вы be good teammate?

3. Communication

Clear explanations к non-analysts.

4. Initiative

Passive «do what told» vs proactive partner?

5. Push-back

Respectful challenge когда needed.

Типичные questions

1. Favorite product / why?

Tests product appreciation.

Structure:

• Name product
• Why love it
• One thing you'd change и why

Show analytical thinking.

2. Investigate metric drop

«CR упал 20%. Walk me through investigation».

Framework-driven answer:

• Verify data
• Timeline
• Scope (segments)
• Correlate events
• Hypothesize
• Validate

3. Feature success

«We launched feature X. How measure?»

Consider:

• Primary: adoption rate
• Secondary: engagement impact, revenue
• Guardrails: not breaking other metrics
• Timeline: short vs long-term

4. Prioritization

«Two features. Which ship first?»

Show framework:

• Impact (reach × impact)
• Effort (engineering cost)
• Risk
• Strategic fit

Not «ship both» — prioritize.

5. Decision support

«I want ship X. Data supports?»

Challenge respectfully:

• «Let me check metrics»
• «Need more data to confirm»
• Suggest additional experiment
• Каusal vs correlational

6. User research

«Where your data shows but qualitative differs?»

Show integration:

• Don't only trust numbers
• User interviews valuable
• Triangulate insights

7. Experimentation

«Favorite experiment? Run myself or studied?»

Structure:

• Situation
• Hypothesis
• Setup
• Results
• Learning

8. Challenging decisions

«Manager decided ship despite your data. What do?»

Show maturity:

• Make argument
• Don't belabor
• Accept decision (manager's prerogative)
• Learn из outcome

Not: «I would refuse».

Product sense questions

Spotify autoplay

«Should Spotify ship autoplay? Pros / cons».

Walk through:

• Pros: more time, exploratory, passive listening
• Cons: less control, discovery hampered
• Measure: time listening, user complaints, retention
• Test: A/B с opt-out
• Conclusion: depends на goals

Shows structured thinking.

New feature

«Design experiment для X new feature».

• Hypothesis
• Metrics (primary, guardrail)
• Sample size estimation
• Duration
• Analysis plan
• Decision framework

Behavioral

Collaboration

Time worked closely с PM. Specific.

Stakeholder managing

Multiple demands. Negotiated.

Own decisions

«PM said ship — you felt risky. What did?»

Disagreement

Handled professionally. Data-based argument.

Prepare примеры

Have ready:

• 1 favorite product
• 1 favorite experiment
• 1 product insight
• 1 time disagreed
• 1 time helped PM decide
• 1 failed analysis
• 1 time pushed back successfully

Что показать

Curiosity

«I wonder if...»

Product-minded.

Humility

«Let me dig to confirm»

Not overstate.

Ownership

«I owned this metric...»

Not passive.

Collaboration

«Worked с PM к ship...»

Partnership.

Что избегать

Data purism

«I only trust numbers» → not flexible.

Over-analyzing

«I'd need 20 more dashboards before deciding»

PM wants progress.

Dismissive

«That's wrong» — disrespectful.

Collaborate.

Passive

«I just do what told» → no initiative.

During interview

Listen

PM explains context. Don't interrupt.

Clarify

«Can you tell me more about...»

Shows engagement.

Structure

Give answers structured. Not random thoughts.

Confidence + humility

Strong opinions, held loosely.

После interview

Reflect

What went well? Questions stumbled on?

Follow-up

Thank-you note (optional).

Mention specific topic заинтересовавший.

В Russia контексте

Russian PMs

Often similar к US style. Some более corporate (Sber, Газпром) — structured processes.

Startups

Informal, product-heavy.

Tech giants (Yandex, Тинькофф)

Framework-driven questions, rigorous.

Senior PMs

В больше companies — multiple PMs. Senior — strategic, junior — feature.

Senior PMs test

• Strategic thinking
• Cross-team work
• Vision

Junior PMs test

• Execution
• Framework knowledge
• Detail

Adjust answers.

Different roles

Growth PM

Experiment-heavy. A/B knowledge.

Platform PM

Infrastructure, developer experience.

Product ops

Processes, efficiency.

Different focus interview.

На собесе

Opening

Warm, brief introduction.

Mid

Thoughtful, structured answers.

Closing

Your questions для PM:

• «What make великий product analyst в вашей команде?»
• «Current top product challenge?»
• «Как вы measure success?»

Связанные темы

• Как работать с PM эффективно
• Продуктовое мышление
• Как готовиться к senior собесу
• Как отвечать на кейсы

FAQ

Надо быть PM'ом чтобы знать?

No. But read «Inspired», use products analytically.

Technical deep?

Less technical, more product-thinking.

Нервничать?

Normal. Practice reduces.

---

Готовьтесь — откройте тренажёр с 1500+ вопросами для собесов.