Day 14: Write a Job Description That Attracts A-Players

The Point Of Today

A job description is a sales page for a career decision.

That does not mean it should be flashy or exaggerated. It means the post should help the right candidate understand why the role matters, what they will own, what success looks like, and whether the company is the right environment for their best work.

Most job descriptions do the opposite. They list responsibilities, requirements, and generic culture statements. They describe the company's needs but not the candidate's opportunity. Strong candidates, especially those already doing good work elsewhere, read that kind of post and move on.

Today you will create a job description that is clear, outcome-focused, and honest about the stage of the company.

Write For The Candidate You Want

The strongest candidates are usually evaluating risk.

They want to know:

• Is the company solving a meaningful problem?
• Is this role important or peripheral?
• Will I have ownership?
• What does success look like?
• Is leadership clear about priorities?
• Is the compensation and working model transparent?
• Will this role help my career grow?

Your job description should answer those questions directly.

Avoid language that sounds like every other startup. "Fast-paced environment," "wear many hats," and "rockstar" do not help serious candidates. If the work is ambiguous, say what kind of ambiguity. If the role requires building from zero, say what must be created first. If the company is early and messy, be honest, then explain why the opportunity is still compelling.

Replace Duties With Outcomes

Responsibilities describe activity. Outcomes describe success.

Instead of:

"Manage customer onboarding."

Write:

"In your first 90 days, you will reduce the time from signed contract to first value from 14 days to 7 days by redesigning the onboarding workflow."

The second version tells the candidate what matters. It also tells you how to evaluate performance.

For each role, define two to four 90-day outcomes. They should be specific enough that a candidate can picture the work and a hiring manager can assess progress.

Good outcomes often include:

• A workflow created or improved.
• A metric moved.
• A system built.
• A customer experience clarified.
• A recurring process owned.
• A strategic decision supported by evidence.

If you cannot define the outcomes, the role may not be ready to hire. That is useful information.

Be Honest About The Tradeoffs

Great candidates do not need a perfect role. They need a truthful one.

If the company is early-stage, there may be limited process, changing priorities, incomplete documentation, and decisions made with imperfect data. Some candidates love that environment. Others do not. Your job description should help both groups self-select.

Honesty saves time. A candidate who wants a mature operating system should not discover in week two that they were hired into a build-from-scratch environment. A candidate who wants ownership should see that the role offers real scope, not just a title.

You can write tradeoffs professionally:

"This role is best for someone who enjoys building the operating rhythm, not inheriting one. Some systems are still forming, and part of your work will be to make them clearer."

That sentence will attract the right person and repel the wrong one. That is good hiring.

Screening Questions Should Reveal Thinking

Screening questions are not paperwork. They are the first work sample.

Ask questions that reveal how the candidate thinks:

• "Describe a time you built a process from scratch. What made it work?"
• "What would you do in your first 30 days if hired for this role?"
• "Tell us about a decision you made with incomplete information."
• "What does excellent work look like in this function?"

Avoid questions that can be answered with generic enthusiasm. You are looking for specificity, judgment, and evidence of ownership.

Pair the questions with a simple scorecard. Decide in advance what strong, average, and weak answers look like. This reduces bias and prevents the hiring process from becoming a collection of vibes.

Compensation And Transparency

Include compensation information when possible.

Transparency saves time and builds trust. If the range is still being finalized, say so clearly and explain the components: salary, equity, bonus, benefits, location expectations, or contract terms. Avoid "competitive" unless you genuinely have a reason not to state a range.

High-quality candidates notice clarity. They also notice when companies avoid basic information. A transparent post signals operational maturity, even when the company is small.

Today's Practice

Run the prompt and generate the job description.

Then review it from the candidate's perspective:

• Would a strong candidate understand why this role matters?
• Are the first 90 days specific?
• Is the company honest about its stage?
• Are must-have skills truly required?
• Are nice-to-have skills clearly separate?
• Does the post help the wrong candidate self-select out?

Create the scorecard before publishing. The post attracts candidates; the scorecard protects the decision. Together, they turn hiring from a rushed search into a more thoughtful operating process.