Что такое performance-специалист?

Performance specialist (PM мира): определение и контекст

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

"Performance specialist" в контексте PM может означать несколько вещей. Объясню каждое:

Определение 1: Performance marketing specialist

Это не PM.

Это маркетолог, который фокусируется на:

• Cost per acquisition (CAC)
• Return on ad spend (ROAS)
• Conversion optimization
• A/B тестирование campaigns

Как PM взаимодействует:

• Они оптимизируют traffic acquisition
• Я оптимизирую продукт (из этого traffic)
• Вместе добиваемся роста

Определение 2: Performance optimization PM

Это специализированный PM.

Focus на:

• Скорость приложения (page load, API latency)
• Стабильность (uptime, errors)
• Scalability (как много users может handle)
• Resource optimization (CPU, memory, database)

Пример роли: "Senior PM, Performance" — отвечает за то чтобы сервис fast и reliable.

Мой experience: Одна из моих инициатив была improve performance:

• Page load: 3s → 1.2s
• API latency: 500ms → 150ms
• Result: +15% conversion rate (people don't leave slow sites)

Определение 3: High performer (человек)

Не специалист, а человек.

Business context: "Она performance-specialist на нашей team" = "Она best performer".

Значит:

• Delivers results consistently
• Exceed targets
• Reliable team member

Определение 4: Performance metrics specialist

PM, фокусирующийся на metrics.

Это я отчасти:

• Deep analysis retention, churn, LTV
• Cohort analysis, funnel analysis
• Performance tuning (какие levers move metrics)
• Experimentation (A/B tests to improve metrics)

Контекст в разных industires

в SaaS: Performance specialist = PM who owns key metrics (DAU, retention, revenue)

в e-commerce: Performance specialist = optimize conversion rate, AOV, repeat purchase

в FinTech: Performance specialist = speed to trade execution, transaction success rate

Мой вклад в performance

1. Performance optimization (infrastructure)

Project: Database query optimization

Ситуация: Dashboard loading в 3 seconds, users complained.

Мой role:

• Identified that 50% of load time is one query
• Worked with engineering to optimize
• Added caching layer
• Result: 1.2s (60% improvement)

Impact: +8% feature adoption (people use faster feature more)

2. Performance monitoring

Что я делаю:

• Daily check: Page load, API latency, error rate
• Weekly: Trend analysis (getting faster or slower?)
• Monthly: Cohort performance (iOS vs Android, new vs old users)

Example finding: Android users experience 2x slower app than iOS. Fix: Optimize for Android, now equal. Result: Android DAU +15%.

3. Performance as differentiator

Мой thinking: Speed это feature, не technical detail.

Marketing message: "Fastest platform in the market"

Data: Load time vs competitors

• Us: 1.2s
• Competitor A: 2.5s
• Competitor B: 3.1s

Sales enablement: "When speed matters, we win"

Result: Sales team reports 25% higher closing rate when performance highlighted.

Когда performance matters (или нет)

Cases where performance critical

1. High-frequency usage: Day traders, stock market apps

   • 100ms difference = money (literally)
   • Performance is life or death

2. Mobile-first markets: India, Southeast Asia

   • Many users on 3G
   • Slow sites = churn
   • Performance determines success

3. Competitive markets: Taxi apps, job sites, dating apps

   • Everyone has same features
   • Differentiator is speed/UX
   • Performance = competitive advantage

Cases where performance less critical

1. Niche products: Specialized tools

   • Users need it, willing to wait
   • Example: Scientific research tool

2. Async-friendly: Batch processing

   • Waiting a few seconds is OK
   • Example: Video rendering tool

3. Low-frequency usage: Tools used once a quarter

   • Speed doesn't impact engagement
   • Example: Tax filing software

Performance vs other priorities trade-off

Scenario: Engineering team can either:

• Build 2 new features, OR
• Optimize performance (make app 2x faster)

Decision framework:

My approach: I don't choose. I analyze:

• How much would performance improvement impact retention? (measure)
• How much would new feature impact engagement? (measure)
• Which ROI higher? (choose that)

Example: Performance improvement: +5% retention × 10k users = 500 users New feature: +3% activation × 2k new signups = 60 users Performance wins.

Performance metrics I track

Infrastructure level:

• Page load time (<1.5s target)
• API latency (<200ms target)
• Error rate (<0.1% target)
• Database query time (<100ms p95 target)

User experience level:

• Time to first interaction (<2s)
• Time to ready (fully loaded)
• Cumulative layout shift (visual stability)

Business level:

• Correlation: page speed → conversion rate
• Correlation: API latency → engagement
• Performance regression: Is it getting slower?

Performance monitoring tools

Я use:

• DataDog (infrastructure monitoring)
• Segment (user analytics, with latency)
• Lighthouse (page speed)
• Custom dashboards (track correlations)

Главное

Performance specialist может быть:

1. Marketing role (paid acquisition optimization)
2. PM specialization (optimize performance metrics)
3. Infrastructure/engineering role (optimize system performance)
4. HR term (best performer)

В контексте интервью для IT PM, если вас спрашивают, вероятно имеют в виду:

• Умение я optimize ключевые metrics
• Понимаю что performance matters
• Can measure impact

Мой ответ: Я не performance specialist в смысле narrow specialization. Но я care deeply about performance (both technical и business). I measure impact of speed on user behavior. I prioritize performance work when ROI высокий.

Это part of being well-rounded PM, не specialize роль.