How do you write a job description that actually attracts senior talent?

Senior candidates evaluate job descriptions differently than junior candidates do — they're reading for specific signals about scope, autonomy, and whether the role is well-defined, not just scanning a skills checklist. The postings that attract strong senior applicants are specific in exactly the places most postings default to generic language.

Describe the problem, not just the title

"VP of Engineering to lead our platform team" tells a senior candidate almost nothing. "VP of Engineering to rebuild our platform architecture ahead of a 10x scale target over 18 months" tells them exactly what they'd be walking into, and lets the right candidates self-select in — and the wrong ones self-select out — before you ever see an application.

Be honest about what's unresolved

If the reporting structure, budget, or team size isn't finalized yet, say so directly rather than presenting a settled picture that turns out to be aspirational. Senior candidates have generally been burned by this before, and honesty about what's still being figured out builds more trust than a polished but inaccurate description.

Name the actual decision-making authority

"You will own X" is a common phrase that senior candidates have learned to read skeptically, because "own" often means something different in practice than in the job posting. Being specific about what decisions the role can make unilaterally versus what requires sign-off tells a much more accurate story than the word "own" alone ever will.

Skip the skills checklist for genuine senior roles

A long list of specific tools and frameworks is far less useful at senior levels than a clear description of outcomes the role is accountable for. The best senior candidates are evaluating whether the problem is interesting and the scope is real — not whether they've used your exact tech stack before.