Что такое готовый молодой специалист?

Готовый молодой специалист: определение в контексте PM

Что это значит

"Готовый молодой специалист" в контексте Product Management это junior PM с:

1. Базовыми PM навыками (frameworks, metrics, communication)
2. Опыт работы (минимум 1-2 года)
3. Способность work independently (нужен minimal mentoring)
4. Track record успехов (доказал способность deliver)

Отличия от других уровней

"Готовый junior PM" это между Junior и Mid-level.

Признаки готового junior PM

1. Самостоятельность

Что это значит:

• Может write PRD без help
• Может run A/B test independently
• Может interview customers (may quality)
• Может present to stakeholders

Не значит:

• Не нужна feedback (feedback все еще важна)
• Не нужны mentor (mentor полезен)
• Не спрашивает вопросы (все еще спрашивает)

Пример: Junior PM (not ready): "Как мне write этот PRD?" Ready junior: "Вот мой PRD draft, feedback?"

2. Business thinking

Что это значит:

• Понимает business model
• Знает unit economics (CAC, LTV, margin)
• Может estimate impact (revenue/retention impact)
• Думает про sustainability

Не значит:

• Не зависит от CFO advice (нужна консультация)
• Не делает ошибок (делает, но учится на них)

Пример: Not ready: "Давайте build этот feature. Customers просят." Ready: "Customers просят. Это даст нам +5% conversion. ROI: $X за Y месяцев. Стоит ли?"

3. Data mindset

Что это значит:

• Не верит интуиции, верит data
• Может интерпретировать metrics
• Может design простой experiment
• Понимает когда data достаточна

Пример: Not ready: "Я думаю эта feature хорошая." Ready: "50% customers want это. Но только 20% активно просят. Нужна ли?"

4. Communication

Что это значит:

• Может explain decision ясно
• Может write clear PRD (не 50 pages)
• Может present к executives (without being nervous)
• Слушает feedback without defensiveness

Пример: Not ready: Презентация неорганизованная, много "um", не clear Ready: Презентация структурирована, говорит с confidence, data-backed

5. Ownership

Что это значит:

• Takes responsibility for feature success
• Не blames engineers/design if doesn't work
• Post-mortem after feature: что работало, что не
• Iterates based on learning

Пример: Not ready: "Этот feature не сработал потому что инженеры не implement правильно." Ready: "Feature не сработал потому что I didn't validate customer need хорошо. Не потому что technical issue."

Характеристики "готового" junior

Hard skills

✓ Knows frameworks (RICE, OKR, Jobs to be Done) ✓ Can read data (retention curves, cohort analysis) ✓ Can write spec (PRD, design doc) ✓ Basic technical knowledge (knows how APIs work) ✓ Can present (without script)

Soft skills

✓ Listens (to customers, team, feedback) ✓ Communicates clearly (no jargon, clear intent) ✓ Takes feedback (doesn't get defensive) ✓ Works collaboratively (not "my way or highway") ✓ Persistent (doesn't give up on ideas easy)

Mindset

✓ Customer-obsessed (not feature-obsessed) ✓ Data-driven (not gut-feel) ✓ Growth-oriented (wants to learn, improve) ✓ Humble (knows what they don't know) ✓ Ownership (takes responsibility)

Что я ищу когда hiring junior PM

Red flags (not ready)

❌ "Я think я know what customers want, no need to interview"

• Shows arrogance, lack of customer obsession

❌ "I'll decide features based on my intuition"

• Shows lack of data mindset

❌ "Engineering should just build it"

• Shows lack of respect for technical constraints

❌ "I've never done A/B test but it's easy"

• Shows lack of humility

❌ "My previous manager was terrible, that's why feature failed"

• Shows lack of ownership

Green flags (ready)

✓ "I've done 20+ customer interviews for this decision" ✓ "Here's my experiment design and hypothesis" ✓ "I worked with engineering to estimate effort before committing" ✓ "We shipped feature but adoption was low. Here's what I learned" ✓ "I'm not sure about X, who should I ask?"

Experience expectations

Minimum:

• 1-2 years PM experience
• 2-3 features shipped
• 1-2 projects led

Nice to have:

• Startup experience (fast-paced)
• Mentorship from senior PM
• Shipped features > $X MRR impact
• International or multi-market experience

Как я evaluate ready junior

Case study

"Describe a feature you shipped. What was your process?"

Bad answer: "I told engineers to build it. They did. Customers like it."

• No process, no thinking

Good answer: "Customers complained about X. I interviewed 10 to understand need. Validated with 20 more. Found pattern: 60% have this problem. Did RICE scoring, prioritized it. Worked with design on spec. Shipped MVP. Measured adoption (70%), NPS (+8), impact on retention (+5%). Based on learnings, iterated and added features."

• Shows process, thinking, ownership

Interview with potential junior

Question 1: "Tell me about a time metrics showed you were wrong?"

• Good answer: Shows data mindset + humility
• Bad answer: "I'm always right" or "I don't look at metrics"

Question 2: "How do you measure success of feature?"

• Good answer: Specific metrics, thoughtful about what's important
• Bad answer: "I know if it works" or vague

Question 3: "Describe conflict with engineer/designer. How did you resolve?"

• Good answer: Listened, collaborated, found win-win
• Bad answer: "I told them what to do" or "They were unreasonable"

Разница: Junior vs Ready junior

Junior PM (1 year exp):

• Needs help writing PRD (format, structure)
• Needs guidance on prioritization (how to score)
• Asks permission before interviewing customers
• Nervous presenting to executives
• Blames others when feature fails

Ready junior PM (2 years exp):

• Writes PRD independently (may need feedback)
• Prioritizes features using framework (sometimes debates result)
• Independently interviews customers (quality improving)
• Presents to executives with preparation
• Analyzes failures (what I could do better)

Развитие junior → ready junior

Что нужно:

1. Mentorship: Senior PM provides guidance (2-3 hours/week)
2. Projects: Lead multiple projects (3-5 features)
3. Responsibility: Own P&L for small product
4. Feedback: Regular 1-on-1, honest feedback
5. Stretch: Occasional task slightly beyond ability
6. Learning: Read books, learn frameworks, practice

Timeline: Usually 1-2 years с good mentorship.

Мой advice for junior PM becoming "ready"

1. Interview customers constantly (weekly, not monthly)
2. Learn data analysis (SQL, cohort analysis)
3. Ship features (get experience, fail, learn)
4. Get feedback (from mentor, team, boss)
5. Take ownership (even when scared)
6. Be humble (you don't know everything)
7. Read + learn (PM books, case studies)
8. Teach others (clarifies your thinking)

Итоговый definition

"Готовый молодой специалист" (Ready junior PM):

Это PM с 1-2 years experience, who can:

• Lead small projects independently
• Interview customers, analyze data, make decisions
• Communicate clearly with team and executives
• Own success and failure of their work
• Still learn from mentors but not dependent on them
• Think about business (not just features)

They're not yet senior (can't lead whole vertical), but they're no longer a junior that needs hand-holding.

They can be productive team member immediately with minimal supervision.