An effective job description includes the salary range, describes outcomes instead of tasks, anchors requirements to the first 90 days, and is easy to scan in under two minutes. At MJL Recruiting & Consulting we see these changes bring in more qualified applicants faster than any other edit to a posting.
Once the obvious mistakes are fixed, the next question is what a genuinely effective job description does differently: not just what it avoids, but what it actively does to bring in the right applicants faster.
Should you include the salary range in a job posting?
Yes. Research consistently shows job postings with salary ranges attract two to three times more applicants than ones without. That's not a small edge; it's often the single biggest lever available for improving application volume from qualified candidates.
Candidates don't want mystery around compensation. They want fairness, and a posted range is the clearest signal a company can send that it's operating in good faith before a candidate has invested any time in the process. Transparency reads as trust, and trust is what gets serious candidates to apply.
Should a job description list tasks or outcomes?
Outcomes. There's a meaningful difference between "will manage cross-functional teams" and "will lead two projects that improve X metric by Y% in the first year." The first is a responsibility. The second is a result a candidate can actually picture themselves achieving.
Outcomes create clarity. Clarity creates confidence. Confidence is what turns a passive scroll-past into an actual application. Every responsibility bullet in a job description is worth testing against this question: does this describe what the person does, or what changes because they did it?
What is the most important question when writing a job description?
When writing or revising a job description, the single most useful question to ask is: what must this person accomplish in their first 90 days? That question alone tends to tighten requirements and sharpen expectations more than almost any other editing exercise.
It also forces the description to be written for reality rather than an idealized version of the role that doesn't actually match what day one through ninety will look like.
How should a job description be formatted?
Make it easy to scan. A job posting that's hard to scan is functionally hard to apply to, even if the content itself is strong. Short bullets, clear headers, real white space, and active voice all reduce the cognitive load required just to understand what's being asked, before a candidate ever gets to deciding whether they're a fit.
Don't make candidates work to understand the job. That effort is exactly the kind of friction that causes a strong candidate to close the tab and move to the next listing instead.
Should job descriptions require years of experience?
Read it out loud first. Does it sound like a conversation, or like a compliance document? The tone of a job posting tells candidates more about the actual culture of a company than almost anything else in the hiring process, whether that's intentional or not.
Stop leaning on "5+ years of experience" as a stand-in for actual skill. Years aren't skills, and time isn't expertise. Phrases like "has successfully led a project from start to finish" or "can explain complex ideas to non-technical partners" describe real capability. Experience should show up as demonstrated impact, not a timestamp.
What story should a job description tell?
Job descriptions are telling a story, whether you mean to or not. They shouldn't oversell a role, but they should tell a real story: why the role exists, what success looks like, and why any of it matters to the business. People don't apply to jobs in the abstract. They apply to meaning, some sense that the role connects to something larger than a task list.
Job description checklist
Before your next posting goes live, run it through this checklist:
- Is the language human, not corporate?
- Is the tone welcoming rather than transactional?
- Are the requirements realistic for what the role actually needs?
- Is the salary range included?
- Can someone read the whole thing in under two minutes?
- Would you personally apply to this job, based on how it reads?
Better job descriptions lead to better candidates, and better candidates lead to better teams. It starts with the page most companies spend the least time on.
Frequently asked questions about effective job descriptions
Do salary ranges increase job applications? Yes. MJL Recruiting & Consulting points to research showing job postings with salary ranges attract two to three times more applicants than postings without them. A posted range signals fairness and good faith.
How long should a job description be? MJL Recruiting & Consulting recommends that someone can read the whole job description in under two minutes. Short bullets, clear headers, white space, and active voice make it easy to scan.
What should replace "5+ years of experience" in a job description? MJL Recruiting & Consulting recommends describing real capability instead, such as "has successfully led a project from start to finish" or "can explain complex ideas to non-technical partners." Years aren't skills.
How do you write job description responsibilities? MJL Recruiting & Consulting recommends writing outcomes, not tasks. Instead of "will manage cross-functional teams," describe what changes because the person did the work, like leading two projects that improve a specific metric in the first year.
Writing job descriptions that convert takes more than a checklist; it takes knowing what your market is actually responding to right now. See how MJL Recruiting & Consulting builds job descriptions that fill roles faster →