Netflix Senior Revenue Operations Manager - Interview Preparation Guide

Overview / goal
Design a RevOps org to scale ARR from $1M → $10M in 24 months, aligning Sales, Marketing, CS. I’ll present roles, quarterly headcount plan, responsibilities, first three hires, and hire triggers.

Roles & responsibilities

• Head of Revenue Operations (HoRevOps): strategy, cross-functional alignment, forecasting cadence, tech roadmap, hiring.
• Revenue Operations Manager: day-to-day ops, analytics, dashboards, process optimization, CRM admin.
• Sales Operations: quota setup, comp, deal desk, pipeline hygiene.
• Marketing Operations: lead flows, MQL→SQL conversion, attribution, MAP/CRM integration.
• Customer Success Operations: health scoring, expansion motions, churn analytics.
• RevOps Analyst/BI: data models, ETL, reports.
• Revenue Systems Admin: automation, integrations, API work.

Headcount by quarter (Q1 = now)

• Q1: HoRevOps (contract/part-time) + RevOps Manager (1) — 1 FTE + HoRevOps (pm)
• Q2: + Sales Ops (1) — total 2
• Q3: + Marketing Ops (1) — total 3
• Q4: + RevOps Analyst (1) — total 4
• Year 2 Q1: + Customer Success Ops (1) — 5
• Q2: + Systems Admin (1) — 6
• Q3: Scale hires (Analyst x1, Ops x1) based on volume — target 8–10 by end of year 2

First three hires

1. RevOps Manager — central executor: CRM, dashboards, forecasting, lead routing.
2. Sales Operations — close support for reps, comp, deal desk, pipeline hygiene.
3. Marketing Operations — MAP/CRM, attribution, lead quality.

Hire triggers / metrics

• Hire Sales Ops when SDR+AE headcount or opportunities grow 2x from baseline or weekly forecast error >10% and pipeline hygiene tasks backlog >10 items/week.
• Hire Marketing Ops when MQL volume >1,000/month or lead-to-opportunity conversion drops >20% or attribution needs multi-touch modeling.
• Hire RevOps Analyst when reporting requests exceed 10/week, average report latency >48 hours, or data reconciliation time >20% of RevOps time.
• Hire Systems Admin when integrations >5, webhook failures >3/week, or automation backlog delays >2 sprints.

Why this structure: early central operator (RevOps Manager) creates repeatable processes; function-specific ops scale with GTM complexity; data & systems hires reduce manual work and enable predictable forecasting.

Direct answer
Before treating a shift from 45 to 60 days as a real bottleneck, rule out three cheaper explanations first: a metric-definition or mix change, a small-sample statistical fluke, and a data-pipeline artifact. Only once those are ruled out does it make sense to dig into stage-level dwell times and recent process changes as the likely real cause.

Structured elaboration

1. Verify the metric and timeframe: confirm "opportunity-to-close" is defined the same way in both periods, same stage set counted, same won/lost inclusion rule, pulled from the same CRM (customer relationship management)-to-warehouse source, over at least the last 6 months.
2. Check sample size and whether the shift could be noise: compare deal counts and run a simple significance check, for example a two-sample comparison of means, between last quarter and the prior quarter. A shift built on a small number of deals should be treated as provisionally noise until confirmed.
3. Segment by deal attributes: break the average out by stage-progression path, lead source, deal size (ARR, annual recurring revenue), product, region, and account executive (AE) to see whether the 15-day shift is company-wide or concentrated in one segment.
4. Inspect stage-level dwell time: look at time spent in each individual stage rather than only the end-to-end average, since a single stage disproportionately ballooning, commonly legal or procurement, can move the whole average without every stage actually being slower.
5. Check for recent operational changes: a new approval step, a CPQ (configure, price, quote) tool change, an integration outage, or a pricing and discount policy change within the window; interview sales ops and the account executives closest to the affected segment rather than relying on the dashboard alone.

Worked example
Suppose last quarter had 200 closed-won opportunities averaging 45 days, and this quarter has 180 closed-won opportunities averaging 60 days overall. Segmenting by deal size shows enterprise deals, which grew from 30% to 45% of the closed-won mix quarter over quarter, average 85 days, while SMB (small and midsize business) deals still average 40 days, roughly unchanged from last quarter. A quick mix-adjusted check: applying this quarter's segment mix, 55% SMB at 40 days and 45% enterprise at 85 days, gives a blended average of 0.55 x 40 + 0.45 x 85 = 22 + 38.25 = 60.25 days, which matches the observed 60-day overall average almost exactly. That's a strong signal the apparent bottleneck is actually a mix shift, more enterprise deals, which have always taken longer, rather than every deal getting slower, and it tells you where to look next: what changed enterprise's SHARE of the pipeline, not what changed everyone's process.

Trade-offs and pitfalls
Jumping straight to "sales got slower" and mandating a company-wide process fix when the real driver is a segment mix shift wastes a quarter of change-management effort on the wrong lever. Treating the end-to-end average as the diagnostic instead of stage-level dwell time can miss that one stage, legal review for example, is driving the whole number while every other stage is fine. Declaring the shift "real" off a single quarter of data without checking against the prior 2-3 quarters risks reacting to ordinary quarter-to-quarter variance, especially for segments with smaller deal counts where averages are naturally noisier.

Example queries

A first query against the CRM-to-warehouse data supports step 2's noise check by pulling deal counts and average days-to-close side by side for both quarters:
SELECT quarter, COUNT(*) AS closed_won_count, AVG(days_to_close) AS avg_days_to_close FROM opportunities WHERE stage = 'closed_won' AND close_date >= DATEADD(quarter, -2, CURRENT_DATE) GROUP BY quarter;

A second query supports step 3's segmentation by breaking the same numbers out by deal size and account executive, which is what would surface a segment-level shift (like the enterprise-mix change in the worked example below) rather than only the blended average:
SELECT quarter, deal_size_band, account_executive, COUNT(*) AS deal_count, AVG(days_to_close) AS avg_days_to_close FROM opportunities WHERE stage = 'closed_won' AND close_date >= DATEADD(quarter, -2, CURRENT_DATE) GROUP BY quarter, deal_size_band, account_executive ORDER BY quarter, deal_size_band;

Overview
I would implement a simple rule-based lead routing + SLA that prioritizes speed for high-value leads while ensuring qualification for efficiency.

Routing criteria

• MQL scoring: Score ≥ 80 → High priority (immediate sales handoff)
• Firmographic fit (industry, ARR), intent signals (demo request, pricing page) → Medium priority
• Low intent/marketing nurture → Low priority (SDR nurture or drip)

SLA times

• First contact (phone/email): High = 15 minutes, Medium = 2 hours, Low = 24 hours
• Follow-up cadence: High = 3 more touches within 72 hours; Medium = 5 touches across 7 days; Low = automated nurture + quarterly review

Ownership rules

• SDR owns initial outreach and qualification within SLA; when qualified (BANT/CAN criteria) SDR converts to AE and assigns owner in CRM. Ownership timestamps recorded.

Escalation path

• Missed first-contact SLA → automated Slack + email alert to SDR lead; 30 minutes later escalate to SDR manager; 3 hours → Ops notification for case review and process fix.
• Repeated misses by same rep → performance review with manager and retraining.

Measurement & adherence

• Dashboards in CRM/BI showing: % first-contact within SLA by priority, average time-to-first-contact, follow-up completion rate, conversion from lead → SQL within X days.
• Automated weekly SL A report, monthly trend review, and a quick pulse alert for SLA breaches > 5% by segment.
• Use objectives: target 90% first-contact SLA for High, 80% for Medium.

This balances speed for revenue-critical leads with efficient use of reps through qualification and automation; tracked with clear ownership and escalation.

60-Day Plan (Revenue Operations Manager)

Days 0–14 — Rapid Diagnosis

• Data checks: validate ETL timestamps, dedupe leads/opps, compare CRM vs. billing (sample 3 months); profile missingness, stale stages, closed-lost reasons.
• Model diagnostics: compare recent forecast vs. actual by cohort, product, rep; re-run residual analysis, calibration (P50/P80), and feature drift (lead source, conversion time).
• Stakeholder audit: 1:1s with Sales, CS, Marketing ops to map inputs (override rules, commit process, quota changes); observe weekly forecast meeting.

Days 15–30 — Short-term Fixes & Hypotheses Testing

• Fix data: patch mapping errors, standardize stage definitions, reclassify multipath opps.
• Model tweaks: retrain with recent data, add lead-velocity or PD indicators, implement simple bias-correction factor per rep/segment.
• Behavioral fixes: enforce staging discipline, tighten commit criteria, introduce one-week lookback accountability.
• Metrics: target 10% accuracy lift measured on MAPE/MAE; run A/B on corrected vs. legacy forecasts.

Days 31–60 — Embed & Scale

• Process: formalize forecast governance (data owner, SLA, weekly audit checklist).
• Tech: automate data quality alerts, versioned model deployment, forecast lineage in BI.
• People: create forecast scorecards per rep/segment, quarterly calibration workshops, tie forecast hygiene to ops/compensation levers.
• Review: 60-day post-mortem with KPIs (accuracy, bias, data latency); roadmap for advanced models (ML ensemble, survival analysis) if baseline uplift <10%.

Rationale: combine immediate data fixes and bias correction for quick gains, plus governance and automation to sustain accuracy.

Situation & framing (one line)
As Revenue Operations Manager, I’d map Lewin (Unfreeze → Change → Refreeze) to Bridges (Ending → Neutral Zone → New Beginning) and run coordinated tactics across CS, pricing, product, and comms to minimize churn and protect NPS.

Unfreeze / Ending (create readiness, acknowledge loss)

• Tactics: segment impacted customers; proactive outreach from CSMs with targeted FAQs; grandfathering options for high-risk cohorts; transparent email + in-app notices with timeline and rationale; build escalation path for billing concerns.
• Measurement: baseline churn rate and NPS by cohort; track early cancellation intent (support tickets, downgrade requests), open/CTR on comms, and qualitative feedback themes weekly.

Neutral Zone / Transition (support, test alternatives)

• Tactics: offer temporary credits, tailored migration plans, A/B test price-communication language and packaging, run win-back campaigns for soft churn, equip CS with objection scripts and ROI calculators.
• Measurement: week-by-week cohort churn, conversion to new plans, sentiment in CSAT and NPS pulse surveys, A/B lift on retention and downgrade rates.

Refreeze / New Beginning (stabilize new state)

• Tactics: formalize new onboarding for pricing, update docs, lock in preferred offers, celebrate success stories publicly, align incentives for sales/CS to new model.
• Measurement: post-change 30/60/90-day churn comparison to baseline, NPS trend stabilization, LTV and ARR retention metrics, and audit of support volume reduction.

Why this works
Combines behavioral acceptance with tactical revenue ops: segmentation + experiments reduce reactive churn, while clear measurement (cohorts, A/B, NPS pulses) shows causal impact and guides iterative adjustments.

Overview (role lens)
As a Revenue Operations Manager I’d run this migration as a risk-managed program to preserve pipeline integrity, forecasting, and marketing operations while upgrading CRM capabilities.

Phase 1 — Discovery (2–4 weeks)

• Inventory objects, custom fields, attachments, workflows, integrations, report logic, and SLAs.
• Stakeholder map: Sales, SDR, Marketing Ops, CS, Finance. Define must-have vs nice-to-have.
• Define success metrics: record counts, data quality thresholds, zero-loss of open opportunities, reporting parity.

Phase 2 — Mapping & Design (2–3 weeks)

• Field-by-field canonical mapping; document transformations, lookup relationships, and retention policy for attachments.
• Design data model in Salesforce/HubSpot and middleware (Mulesoft/Workato/DTM).

Phase 3 — Extraction (1 week)

• Export snapshots with immutable IDs, metadata, and binary attachments; use incremental CDC for recent changes.

Phase 4 — Transformation (2 weeks)

• Cleanse, dedupe, normalize stage values, convert legacy picklists, rehydrate activity timestamps.
• Hash-match for dedupe; convert attachment links to cloud storage with references.

Phase 5 — Pilot (2 weeks)

• Load subset (accounts + active opportunities + 90d activities) into sandbox.
• Validate key reports, pipeline, email integrations, automation. Collect user feedback.

Phase 6 — Cutover (weekend/overnight)

• Freeze writes (short maintenance window), run final CDC, load delta, switch integrations DNS/webhooks to new instance.
• Communicate runbook and rollback triggers.

Phase 7 — Verification & Reconciliation (1 week)

• Reconcile counts, open pipeline amounts, activity volumes; run smoke tests for workflows and dashboards.
• Owners sign-off.

Rollback Plan

• Keep legacy read-only for 7 days; snapshot backups; automated script to re-point integrations back and re-enable writes if critical divergence detected.

Post-migration & Training

• Phased training: bite-sized role-based sessions, playbooks, and support channels.
• 30/60/90 day data audits, report parity checks, and continuous cleanup sprints.

Minimize Disruption Strategies

• Parallel-run for reporting (dual-writing through middleware), limited write freeze, prioritize active pipeline and marketing leads, weekend cutover, and high-touch support for quota-carrying reps.

I’d drive this via a RACI, risk register, regular stakeholder demos, and daily cutover war room to ensure revenue continuity.

If I were onboarding a new Revenue Operations Manager focused on reporting & dashboards, my checklist would be:

First Week — Foundations

• Required access: CRM (SFDC), BI tool (Looker/Tableau/Mode), GA/Ad platforms, data warehouse, Jira, Slack, Google Drive, org chart, OKR tracker.
• Training: Security & data governance, BI tool basics, CRM data model overview, team introductions.
• Sample tasks: Run existing executive dashboard, validate 3 key reports for accuracy, attend weekly revenue meeting.
• Success metrics: Has all access; delivered report validation notes with 3 issues/fixes; completed onboarding trainings.

30 Days — Ownership

• Required access: SQL warehouse, ETL tool, sandboxes, report scheduling.
• Training: SQL refresher, ETL basics, forecasting model walkthrough.
• Sample tasks: Rebuild one high-priority dashboard end-to-end; document metrics definitions; automate one manual report.
• Success metrics: Dashboard rebuilt with stakeholder sign-off; data dictionary completed; report runtime reduced or automated.

90 Days — Impact

• Deliverables: Roadmap for dashboard improvements, governance playbook, 90-day analytics project (e.g., churn drivers, funnel leakage).
• Sample tasks: Lead cross-functional workshop, implement data quality alerts, present insights to leadership.
• Success metrics: Roadmap approved, measurable metric improvements (e.g., forecasting error ↓ X%), reusable templates and monitoring in place.

This plan balances access, training, early wins, and measurable impact.

Direct answer

Anchor the SLA (service-level agreement) between Marketing and Sales to a small number of measurable checkpoints: a lead-quality bar Marketing must hit and a response-time bar Sales must hit, both computed automatically from the customer relationship management (CRM) system rather than self-reported, with numeric targets that are agreed up front and re-baselined periodically, and an escalation path that fires on the data rather than on complaints.

Structured elaboration

Definitions, disambiguated. A marketing qualified lead (MQL) is a lead that has crossed an agreed scoring threshold and fits the target account profile. A sales qualified lead (SQL, in this handoff context; not to be confused with the SQL query language used in the examples below) is an MQL that Sales has validated as a real opportunity worth pursuing. The handoff SLA governs the gap between the two.

SLA metrics and targets. Time-to-contact: Sales engages a new MQL within an agreed window (for example 2 business hours), with a target share of MQLs meeting it (for example 90%). Qualification conversion rate: the share of MQLs that become SQLs within an agreed window (for example 7 days), with a target of 25-30% of MQLs converting within that window, the range the worked example below checks its 28% result against. Lead rejection rate: the share of MQLs Sales rejects as non-fit, with a target ceiling of under 15%, capped so it stays a signal of real mismatches rather than a sign Marketing is over-scoring leads; a rate meaningfully above that ceiling should trigger a review of the scoring model itself rather than more Sales headcount. Lead completeness: the share of MQLs arriving with every required field populated, with a target of at least 98%, so Sales is never blocked by missing data.

Data sources and queries. Marketing automation (for example Marketo or HubSpot) for campaign and scoring events, the CRM (for example Salesforce) for lead, contact, and opportunity records, and a shared warehouse for unified reporting. Time-to-contact:

SELECT
  l.id,
  l.created_at AS mql_time,
  MIN(a.created_at) FILTER (WHERE a.type IN ('outbound_activity', 'call')) AS first_contact_time,
  DATEDIFF('second', l.created_at, MIN(a.created_at) FILTER (WHERE a.type IN ('outbound_activity', 'call'))) / 3600.0 AS hours_to_contact
FROM salesforce.leads l
LEFT JOIN salesforce.activities a ON a.who_id = l.id
WHERE l.is_mql = TRUE AND l.created_at BETWEEN :start AND :end
GROUP BY l.id, l.created_at;

Conversion rate:

SELECT
  COUNT(DISTINCT CASE WHEN l.is_sql = TRUE THEN l.id END) * 1.0 / COUNT(DISTINCT l.id) AS mql_to_sql_rate
FROM salesforce.leads l
WHERE l.is_mql = TRUE AND l.created_at BETWEEN :start AND :end;

Reporting cadence. A daily operational view of time-to-contact and any SLA breach for the SDR (sales development representative) and revenue operations (RevOps) teams, a weekly leadership view of conversion trends and lead-source performance, and a monthly joint review that includes root-cause analysis of any sustained miss.

Escalation path. An automated alert to the SDR manager and RevOps when the daily breach rate crosses an agreed threshold; a 48-hour window for the SDR manager to supply a remediation plan; escalation to VP-level sponsors if the breach persists past 2 weeks, with a joint corrective plan that can revisit the MQL scoring criteria itself, not just staffing.

Worked example

Suppose Marketing delivers 500 MQLs in a month and, applying the conversion-rate query above, 140 of them convert to an SQL within the 7-day window. The MQL-to-SQL conversion rate is 140 divided by 500, or 28%, which falls inside the illustrative 25-30% target stated above: this shows how the query's output ties directly back to a specific, checkable number and target range rather than a vague "conversion looks healthy" statement in a meeting.

Trade-offs and pitfalls

An SLA that measures only speed (time-to-contact) without also measuring quality (conversion) rewards Sales for touching leads fast and dismissively, since a fast, low-effort touch still counts as "contacted." A rejection-rate ceiling set too low pressures Marketing to under-report bad leads instead of fixing the scoring model that produced them. And SLA metrics computed from a manually logged field, like a rep typing in "first contact made," rather than an actual system event, will drift from reality over time unless someone periodically audits the instrumentation itself against real activity logs.

Approach summary (role lens)
As Revenue Operations Manager I’d build a layered attribution framework: start with rules-based for quick insights and governance, then move to algorithmic (Shapley / data-driven) for optimized investment decisions. Use experiments where possible and tie outputs to financial KPIs (pipeline, ARR, CAC, LTV).

Model comparisons

1. First-/Last-Touch / Linear / Time-decay (rules-based)

• Data required: unified contact/account timeline (touch timestamps, channel, campaign, lead→opportunity→won link), revenue timestamps.
• Pros: simple, explainable, fast to implement, aligns to specific business rules.
• Cons: over/under-credits channels, ignores synergy and sequence effects.
• Use-case: operational dashboards, channel-level health checks.

2. Shapley Value (game-theoretic)

• Data required: same timeline + many conversion paths; need sufficient path variety and computing capacity. Account-level attribution preferred.
• Pros: fair credit allocation accounting for marginal contribution and interactions. Interpretable mathematically.
• Cons: computationally expensive for long paths; sensitive to path sampling and missing data.

3. Data-driven / Model-based (Markov chains, uplift, machine learning)

• Data required: granular path data, feature set (touch metadata, lead score, intent signals), negative examples, holdout periods.
• Pros: captures nonlinear effects, sequencing, can include covariates (account size). Scalable to predict incremental impact.
• Cons: requires stronger data quality, careful engineering, potential overfitting; less transparent without explanation tools (SHAP).

Validation vs financial outcomes

• Backtest: predict contributed pipeline/revenue on holdout and compare to observed using MAPE / R^2.
• Incrementality tests: run randomized spend shifts or geo tests; compare model-predicted lift to actual incremental revenue.
• ROI/CAC alignment: compute channel-level CAC and LTV using model credits; check changes in unit economics vs actual cohort performance.
• Sensitivity & sanity checks: simulate missing-touch scenarios; ensure model ranks channels sensibly and that spend reallocation improves pipeline quality in experiments.

Implementation note: start with rules-based for governance, parallel-run algorithmic model, validate with experiments, and operationalize the one that improves incremental revenue and unit economics.

48‑Hour 8‑Step Plan (prioritized)

1. Rapid sync: convene Sales, CS, Finance & Marketing for 60m data huddle — assign owners.
2. Verify data: reconcile CRM vs. billing vs. forecast model (deal stages, ARR, ACV).
3. Top‑down variance: quantify miss by cohort, product, region, rep — produce waterfall.
4. Bottom‑up audit: validate top 20 deals (close dates, risks, contract issues).
5. Pipeline health: check lead → opp conversion, aging, velocity; flag missing pipeline.
6. Contract/ops blockers: identify billing, legal, fulfillment delays; estimate $ impact.
7. Quick fixes: propose immediate actions (expedite approvals, offer short‑term discounts, extend PO deadlines).
8. Communicate & cadence: present findings + 30/60/90 day remediation plan, set daily standups and dashboard updates.

I’d deliver a one‑page executive summary with quantified impacts, owner assignments, and expected recovery by channel.