RevOps Analyst JD teardown
If you ask for analysis but do not define the decision loop, you are hiring a report generator.
What this JD is really asking for (in outcomes)
- One operating dashboard leadership uses
- A weekly cadence that turns signal into action
- Clean definitions so analysis is not debated
Common failure modes (patterns)
- “Build dashboards” without defining the operating meetings they serve
- “Improve attribution” without a data model scope
- “Support teams” without an interface contract
- KPI lists without ownership or targets
- No mention of data sources / quality constraints
Fixes (paste-ready)
Add:
- “Own the weekly operating dashboard used in the revenue review”
- “Own KPI definitions and data quality checks”
- “Own the ‘decision memo’ format: what changed, why, what we do next”
Interview plan preview (3 exercises)
- KPI tree reasoning: pick 3 KPIs and map upstream inputs
- Data QA: find failure points in a mock funnel dataset
- Decision memo: turn a weekly performance snapshot into actions