How to Write a Job Description Candidates Actually Read

A good job description tells a qualified stranger, in under two minutes, what they would own, what evidence of experience you need, how and where they would work, and what it pays. Most descriptions fail because they list everything the team could want instead of what the job actually requires. Write the outcomes first, then the must-haves, then everything else.

This guide is for hiring managers and HR teams who write their own postings, and for anyone whose last posting brought in hundreds of applicants and no one right.

Why most job descriptions don’t work

Most weak postings share a few patterns. They are copied from the last opening, so they describe the previous person rather than the current need. They list fifteen “requirements” that are really preferences. They describe the company at length before saying anything about the job. And they leave out the details candidates check first: pay, location, schedule and employment type.

Strong candidates are usually employed and busy. They skim a posting looking for reasons to keep reading or to stop. Every vague line gives them a reason to stop.

Before you write: agree on the job

The description is the last step, not the first. Spend 20 minutes with the actual decision-makers and answer these questions in writing:

1. What problem is this role solving, and why now?
2. What does success look like at 90 days and at one year?
3. Which skills must the person already have, and which can they learn on the job?
4. Who is the manager, and who has a say in the decision?
5. What is the approved pay range, employment type and work model?
6. What made the last search for this role hard, if there was one?

If the group can’t agree on these answers, the posting will be vague no matter how well it’s written. Our hiring guides include a role intake worksheet built around these questions.

The structure that works

1. A plain, searchable job title

Use the title people in that field actually search for. “Senior Data Engineer” beats “Data Ninja” or an internal grade like “Analyst III”. If the internal title differs, put the common one in the posting and explain the internal one later.

2. A two- or three-sentence summary

Say what the team does, what this person will own and why the role is open. Example: “You’ll own our month-end close for three entities and help move reporting into a new ERP. The role is new because the finance team has doubled.”

3. What you’ll do (outcomes, not chores)

List four to six responsibilities, starting with the most important. Write them as results where you can: “Reduce the time to produce monthly reports” says more than “Prepare reports”. Avoid catch-alls like “other duties as assigned” at the top of the list.

4. What you need (must-haves)

Keep this to three to five items you would genuinely reject someone for missing. Describe evidence, not just years: “You’ve built and maintained data pipelines in production” is clearer than “5+ years of experience”. If a degree isn’t truly required, don’t list it as required.

5. Nice to have

Put preferences here, clearly labelled. Tools a capable person can learn in a few weeks belong here, not in the must-haves.

6. The practical details

The figures in the table are placeholders to show the format, not market rates for any role.

7. What happens after someone applies

A single line on the interview steps and timing builds trust: “Two video interviews and a short work sample; we aim to decide within three weeks.”

Pay ranges and legal basics

New Jersey pay transparency. Since June 1, 2025, New Jersey’s pay and benefits transparency law has required covered employers to include the hourly wage or salary (or a range), a general description of benefits and any other compensation programs in postings for new jobs and transfer opportunities. NJDOL says a range should have a starting and ending point, and warns against phrases like “up to $35 per hour”, “$70,000 per year and up” or “great benefits offered”. Covered employers have 10 or more employees over 20 calendar weeks and do business, employ people or take applications in New Jersey. NJDOL also notes that temporary help and consulting firms may instead give the information at interview or hire (all as of November 2026).

Fair wording. The EEOC states that it is illegal to publish a job advertisement that shows a preference for, or discourages someone from applying because of, race, color, religion, sex (including transgender status, sexual orientation and pregnancy), national origin, age (40 or older), disability or genetic information. Its own example: an ad seeking “females” or “recent college graduates”. Words like “digital native” or “young team” raise the same concern. Describe the work and the skills instead.

To set a range you can defend, see our salary and market insights.

Common mistakes to cut

• A wish list of requirements that no real candidate meets.
• Three paragraphs about the company before the job appears.
• Internal jargon, acronyms and team names outsiders won’t know.
• “Rockstar”, “ninja” and similar labels that tell candidates nothing.
• Copying a competitor’s posting and changing the logo.
• Hiding pay or the work model until the third interview.

If you wouldn’t reject a candidate for missing it, it isn’t a requirement.

How we use the job description at Entrustech

We treat the description as the output of the intake conversation, not a document we receive and post. Before outreach, we confirm the outcomes, the must-have evidence, the range, the work model and the interview path with the hiring manager. When the description and the manager’s expectations describe different jobs, we raise it before the search starts, because that mismatch is one of the most common reasons searches stall. If you’re still choosing between permanent and contract help, our staffing solutions page compares the options.

Hiring for a technical team? Our guide to staff augmentation vs outsourcing helps you decide whether you need a hire at all, or added capacity for a project.

Frequently asked questions