How to Write Executive Job Descriptions That Attract Top Talent

80% of VP+ job descriptions are written by HR teams using templates designed for individual contributor roles. They list 20 requirements, include boilerplate about "fast-paced environments," and tell the candidate nothing about why the role exists. Then companies wonder why their top-choice candidates don't apply.

An executive job description isn't a compliance document. It's a sales pitch to a very specific audience: someone who is currently employed, well-compensated, and selectively considering what comes next. If the JD doesn't answer the question "why should I leave my current job for this one?" within the first paragraph, you've lost them.

Here's a framework for writing executive JDs that attract the candidates you want.

The Opening: Lead with the Business Problem

Executives are problem-solvers. They're drawn to challenges, not task lists. The opening paragraph of the JD should describe the business situation the company faces and why this role is being created or filled.

Weak opening: "We're looking for a VP Sales to join our growing team and lead our sales organization."

Strong opening: "We've grown from $8M to $22M ARR in 18 months with a founder-led sales motion. The board just approved our Series B. We need a VP Sales who has built the sales infrastructure at a company going from $20M to $75M because the CEO can't be the top closer anymore."

The strong version tells the candidate three critical things: the company's growth trajectory, why the role exists now, and what the first-year mandate looks like. A qualified VP Sales reads that and knows immediately whether this is the kind of challenge they want.

Requirements: Five That Matter, Not Fifteen That Don't

The standard JD lists 12-18 requirements and qualifications. At the executive level, this is counterproductive for two reasons. First, no real candidate matches all 18 requirements. Second, research consistently shows that diverse candidates (women, underrepresented minorities) are more likely to self-select out when they don't meet 100% of listed requirements, while others apply at 60% match.

Limit the requirements section to five items. Each should be non-negotiable. Everything else belongs in a "what success looks like" section or should be left for the interview process.

Example for a CTO role:

• Built and managed an engineering team of 30+ people through a period of 2x+ growth
• Hands-on experience with cloud-native architecture at production scale (millions of transactions per day)
• Led at least one major platform migration or re-architecture initiative
• Experience in a regulated industry (healthcare, financial services, or similar)
• Track record of shipping product on a cadence that a growth-stage company demands

Notice what's not on the list: specific degrees, specific years of experience, specific technologies, or vague qualities like "strong communicator." Every item is a capability that can be verified in the interview and that matters for this specific role.

Compensation: Put It in the JD

Pay transparency laws in California, New York, Colorado, Washington, and a growing list of states now require salary ranges on job postings. But beyond legal compliance, including compensation in the JD is good business at the executive level.

VP+ candidates interpret missing salary info negatively. They assume the company either pays below market or is hiding something. A clear comp range (e.g., "$250K-$310K base + 30% target bonus + equity") signals confidence, transparency, and professionalism. These are exactly the qualities that attract the best candidates.

Use current compensation data to set competitive ranges. And don't post a range so wide it's meaningless. "$150K-$400K" communicates nothing. "$250K-$310K depending on experience" communicates something real.

Reporting Structure and Team Context

Executives care deeply about who they report to and who reports to them. Include both in the JD. "Reports to the CEO" carries different weight than "Reports to the COO." A VP Marketing who reports to the CRO will be more revenue-focused than one who reports directly to the CEO. These aren't minor details. They define the role.

Similarly, describe the current team. "You'll inherit a team of 12 including two directors and a manager" is more useful than "You'll lead a growing team." Candidates need to assess whether the team composition matches their management style and the scope of change the company expects.

What to Cut: The Anti-Patterns

"Fast-paced environment." Every company says this. It communicates nothing. If your environment is demanding, describe it specifically: "You'll present to the board monthly and our planning cycles are quarterly, not annually."

"Rockstar" or "ninja" or "guru." Beyond being cliche, these terms actively repel senior candidates. No sitting VP wants to work at a company that uses the word "rockstar" unironically in a job description.

Long lists of "nice to haves." These dilute the requirements section and make the JD longer without adding value. If it's not required, don't list it. Discover it in the interview.

"Must have [specific degree]." Unless the role legally requires a specific license or certification, degree requirements at the VP+ level are outdated and exclusionary. The best executive candidates often have non-traditional educational backgrounds. A CTO with a physics degree who built three engineering organizations is a stronger candidate than a CTO with a CS degree who hasn't.

Writing for Different Audiences

A VP+ job description has multiple audiences, and the best JDs account for all of them. The primary audience is the candidate. But the JD is also read by the candidate's spouse or partner (who has input on life-changing career decisions), the candidate's current colleagues (who may see it on LinkedIn), and your own hiring team (who use it to evaluate candidates).

For the candidate: be specific about the opportunity and honest about the challenges. Executives respect transparency about what's hard. "The product-market fit is strong but the go-to-market motion is immature. You'll need to build the sales playbook from first principles" is more attractive to the right candidate than "exciting opportunity at a fast-growing company."

For the partner: include practical details about location flexibility, travel expectations, and the company's approach to work-life balance. At the VP+ level, these factors matter as much as compensation for the final decision.

For your hiring team: the JD should be the rubric. Every requirement listed should be something you plan to assess in the interview process. If it's in the JD but you're not screening for it, cut it.

Format and Distribution

Length: 600-900 words. This is enough for context without becoming a novel. The JD should take 3-4 minutes to read. If it takes longer, cut it.

Structure: Business context (2-3 paragraphs), the role (2-3 paragraphs), requirements (5 bullets), compensation and benefits (1 paragraph), how to apply (1-2 sentences).

Distribution: Don't just post on LinkedIn and your careers page. Executive JDs should be shared through recruiter networks, board member connections, and industry-specific channels. The passive sourcing playbook applies here: the best candidates won't find your posting. You need to put it in front of them.

Testing and Iterating Your Job Descriptions

Treat executive JDs like marketing copy. Test different versions and measure results. Post version A on LinkedIn and version B through your recruiter network. Track which generates more qualified responses (not just more responses, but responses from candidates who match the actual requirement).

The SHRM job description library provides templates and benchmarks for executive roles. Use these as a baseline, not a ceiling. The best-performing JDs go beyond SHRM's templates by including specific business context, growth metrics, and a clear articulation of what success looks like in the first 12 months.

One more thing: update your JDs every time you learn something new during the search. If the first three candidate conversations reveal that the role needs more technical depth than originally written, update the JD immediately. Stale JDs waste candidate time and yours. The EEOC's anti-discrimination guidelines should be reviewed before publishing any JD to ensure language doesn't inadvertently exclude protected groups.

Track response metrics over time. If your executive JDs consistently generate fewer than 5 qualified applicants within two weeks of posting, the problem is usually one of three things: the compensation is below market, the description is too generic to attract passive candidates, or the distribution channels are too narrow. Diagnosing which factor is the bottleneck requires the same analytical approach you'd bring to any pipeline problem. Treat JD performance as a measurable output, not a creative exercise. The data will tell you what needs to change.

Finally, save every executive JD you write in a central library organized by role type, stage, and industry. After 20-30 JDs, you'll have templates that cover most scenarios. New JDs become faster to write because you're adapting proven frameworks rather than starting from scratch each time. The best recruiting firms treat their JD library as a competitive advantage because it accelerates their search kickoff and ensures consistent quality across every engagement.

Review role-specific intelligence to benchmark how your JD compares to what the market is posting for similar positions.