JD Teardowns (Growth & RevOps)
Most “bad hires” start earlier than the interview loop.
They start when the job description cannot answer four questions:
- What does this role own?
- Which KPIs prove it?
- Which interfaces/handoffs make it real?
- What constraints make it bounded? (time, budget, team, stack)
This library is a set of failure mode patterns and fix patterns for Growth + RevenueOps hiring.
Start with a role family
Pick the teardown closest to the hire you are making
These pages are generic on purpose. They are meant to be pasted into your hiring brief without copying a company JD.
RevenueOps Manager JD TeardownWhen the JD mixes ops, analytics, enablement, and leadership without ownership.
Head of Growth JD TeardownWhen a growth leader is asked to be an operator, a strategist, and a data team.
Demand Gen Manager JD TeardownWhen pipeline is owned, but instrumentation and handoffs are not.
Sales Ops Manager JD TeardownWhen forecasting discipline is asked for, but definitions and enforcement are missing.
RevOps Analyst JD TeardownWhen analysis is requested, but the decision loop is undefined.
Sales Manager JD TeardownWhen quota ownership is expected, but enablement and coverage math are absent.
The core truth
A vague JD is a symptom of a vague operating system
If you cannot specify ownership, KPIs, and interfaces, you do not have a stable system to hire into yet.
- If the JD mixes levels, the interview loop will drift.
- If KPIs are missing, ownership will be argued later.
- If interfaces are missing, the hire will become the glue.
Rewrite the brief, yes. But treat it as a systems audit signal.
Want the audit-grade scorecard on your actual JD?
- Run the tool: Job Description Analyzer →
- Book the audit: Book Growth Team Audit →