A job description is the first filter in your hiring process. Here is how to write one that describes real outcomes, separates must-haves from nice-to-haves, and sets up fair evaluation later.

The job description is your first filter

Most teams treat the job description as paperwork. Someone copies last year's posting, swaps the title, adds a few buzzwords, and publishes it.

That is a costly habit. The description decides who applies, who does not bother, and what every later step is measured against. A vague one fills your inbox with people who could be anything. A precise one sends a smaller, better-matched group your way, and gives your team something concrete to evaluate them against.

Think of it as the first and cheapest screening step you have. Everything below is about making it do that job properly.

Start with outcomes, not duties

The weakest descriptions open with a list of duties: "responsible for managing", "assist with", "support the team in". Duties describe activity. Strong candidates want to know what the work is for.

Try this instead. Finish the sentence: "A year from now, this hire has succeeded if..." Write two to four answers.

Weak: "Responsible for managing the onboarding process."
Stronger: "New customers reach their first successful project within two weeks, and the onboarding handoff no longer needs founder involvement."

The second version tells a candidate what good looks like, tells a weak fit that this is not for them, and gives your interviewers a standard to test against. It also forces you, the hiring team, to agree on what the role is actually for, which is often the real problem.

Separate must-haves from nice-to-haves

The classic mistake is a requirements list of fifteen bullets, each written as if it were essential. Nobody has all fifteen, so candidates either self-select out for the wrong reasons or apply anyway and the list stops meaning anything.

Use a simple test for every requirement: "Would we reject an otherwise strong candidate for lacking this?"

If yes, it is a must-have. Keep this list short, usually three to six items.
If no, it is a nice-to-have. Put it in a separate, clearly labeled list.
If you are unsure, it is probably a nice-to-have.

Be especially careful with years of experience. "Five or more years" is usually a stand-in for something else: judgment, independence, familiarity with a tool. Say the real thing. "Has led a migration without a senior engineer's help" is more honest, and more useful, than a number.

This split pays off later too. When you evaluate applicants, the must-haves carry the most weight and the nice-to-haves break ties. Writing them down now means you do not invent the weighting after seeing the first strong resume.

Write the way people actually talk

Job posts drift into a dialect nobody uses. "Rockstar", "ninja", "fast-paced environment", "self-starter", "wear many hats". These phrases carry almost no information, and some quietly signal things you may not intend, such as long hours or a culture that rewards a narrow personality type.

Replace them with specifics:

Instead of "fast-paced", say what changes quickly: "We ship weekly and priorities are reviewed every two weeks."
Instead of "wear many hats", name the hats: "You will own support triage, onboarding calls, and the help center."
Instead of "competitive salary", give a range if you can. Pay transparency saves everyone time and is now expected or required in a growing number of places.

Aim for plain, direct sentences. A candidate should be able to read the post once and explain the job to a friend.

Use inclusive wording without overdoing it

You want the widest pool of people who can do the work. A few habits help:

Use "you" rather than gendered pronouns.
Avoid wording that implies an age, such as "digital native" or "recent graduate", unless it is a genuine entry-level program.
Only require a degree if the work truly requires it. Otherwise say "or equivalent experience".
State your accommodations and flexibility plainly, for example remote policy, working hours, and how to request adjustments in the process.

Research on job ad language suggests that wording can change who applies, but treat that as a reason to be thoughtful, not as a formula. The goal is clarity, not clever phrasing.

Be honest about the hard parts

Candidates talk to each other and read reviews. A description that hides the difficult parts of a role produces early resignations and wasted interview time.

Include one short paragraph on the challenges: a messy legacy codebase, a team that is still being built, a territory with no existing pipeline. People who are energized by that will lean in. People who would have quit in month three will opt out now, and that is a good outcome for both sides.

A simple structure that works

You do not need a creative format. A reliable order is:

Title and level. Use the title the market uses, not an internal one. "Customer Success Manager" will be searched; "Happiness Architect" will not.
One paragraph on the company and the team. What you do, how big the team is, who the role reports to.
What you will do and achieve. Three to five outcomes, as above.
Must-haves. Three to six items, written as evidence of capability.
Nice-to-haves. A short, separate list.
How we hire. The steps, rough timing, and what to expect. Candidates relax when the process is visible.
Compensation, location, and logistics. Range, remote or office, start date.

The "how we hire" section is underrated. Telling candidates there will be a short screening, a structured interview, and a decision within a stated timeframe sets expectations and reduces the silent drop-off that frustrates both sides.

Connect the description to how you evaluate

Here is the point that most guides skip. A good description is also an evaluation plan. The must-haves you list are the criteria you will score against. The outcomes you describe become the questions in your interviews.

If your evaluation later ignores what the post promised, you will end up selecting on gut feel and then rationalizing. If the same requirements flow through the posting, the scoring, and the interview, you get consistency almost for free. We cover that second half in how to evaluate candidates fairly and consistently.

A quick checklist before you publish

Does it describe outcomes, not just duties?
Is the must-have list short enough to be believable?
Would a stranger understand the job after one read?
Have you removed jargon, clichés, and age or gender signals?
Is there a pay range and a clear description of the process?
Could two interviewers use this to agree on what "good" means?

If you can answer yes to all six, you have done more than most postings manage.

Where a tool can help

Drafting is the slow, blank-page part of this. A writing assistant can turn your rough notes about outcomes and requirements into a clean first draft that you then edit, which is how the job description assistant in Align works: you stay in charge of what the role needs, and the draft saves you the formatting and phrasing. The thinking in this article is what makes the draft good, with or without software.

Write it once, carefully, and reuse the structure for every role. Your future shortlists will thank you.

Job descriptions that bring in the people you actually want to hire