How to Write a Job Posting That Attracts Good Applicants

A job posting that draws strong, well-matched applicants looks different from a generic one. Here are the elements that matter most, from structure to the mistakes that quietly scare good candidates away.

The six elements every posting needs

Applicants look for six things first: the job title, the actual responsibilities, the required qualifications, preferred (nice-to-have) qualifications, work conditions (employment type, location, pay range), and the hiring process itself. Leaving any of these out either scares off applicants early or causes them to drop out later when they finally learn the real conditions. Pay and process, in particular, should be easy to find near the top of the posting.

Write the title as a search term, not a slogan

Job seekers search platforms using concrete role names like "frontend developer" or "logistics coordinator," not company slogans like "join our growing team." A vague, inspirational title simply doesn't get found. Use the industry-standard title candidates would recognize, and add a short qualifier in parentheses if it helps, such as "Backend Developer (Payments Team)."

Make responsibilities concrete, not vague

Phrases like "general marketing duties" or "a variety of projects" force applicants to guess what the job actually involves, which is a common reason new hires quit within months. List 3 to 6 concrete, verb-led responsibilities instead, such as "prospect and meet new client accounts" or "prepare monthly sales reports." It also helps to separate what the person will do in the first few months from how the role may grow later.

Separate must-haves from nice-to-haves

A common mistake is stuffing every desirable trait into "requirements," which shrinks your applicant pool to only people who check every box. A certification or a second language is often genuinely nice to have rather than mandatory. Keep requirements limited to what truly makes the job impossible without it, and move everything else into a preferred-qualifications section to keep the door open to strong candidates.

Make the company and benefits pitch specific

Phrases like "great benefits" or "casual culture" don't build trust because they say nothing concrete. Specific details land much better: "two remote days a week," "meal stipend," "annual learning budget," "extra paid time off." The same goes for describing the company itself β€” founding year, team size, what you actually build, and any recent growth milestones give candidates something real to evaluate.

Common mistakes to avoid

The recurring problems are: using age, gender, or similarly discriminatory language (check your local employment laws, since many countries restrict this explicitly); overstating pay or perks compared to reality, which damages trust once someone is hired; omitting key conditions like location, hours, or contract type until after candidates have already applied; and leaving out the deadline or hiring steps, which floods you with avoidable questions.

Treat the first draft as a draft

Few job postings work perfectly the first time. If applications are slow, the title and required-qualifications section are usually the first things worth revisiting β€” a title that doesn't match how candidates actually search, or a qualifications list that's stricter than it needs to be, quietly filters out people who would have been a great fit. Track how each version performs and adjust before assuming the role itself is the problem.

A job posting is your first promise to a candidate

Everything in the posting sets expectations that the hiring process and the job itself then have to live up to. When the description, pay, or conditions don't match reality, new hires notice quickly and trust erodes from day one β€” sometimes leading to early resignations. Having both HR and the hiring manager review the posting against the actual role before it goes live is a small step that prevents a lot of downstream friction.

Frequently Asked Questions

Should I disclose the salary range in a job posting?

It isn't always legally required, but postings that list a concrete salary range tend to draw more, and often more qualified, applicants. In some countries and states, salary disclosure is now legally mandatory, so check your local requirements. If you're not ready to share an exact figure, even a rough range or a note that pay is negotiable builds more trust than leaving it blank.

How often should I refresh a job posting?

Most job platforms lower the visibility of a posting over time, so if a role stays open indefinitely, refreshing or reposting every two to four weeks is a good habit. If you're getting fewer applicants than expected, that's also a good moment to revisit the title, the scope of the requirements, and how appealing the preferred-qualifications and benefits sections actually read.