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.