How to write a job post that attracts good candidates
You are competing for attention with every other post on the page. The posts that fill well are the ones a reader can understand in thirty seconds.
Include all of these
- Job title — the name people actually search for, not an internal grade
- Summary — two or three sentences on what the role is for
- Responsibilities — five to eight bullets, each starting with a verb
- Requirements — split into must-have and nice-to-have
- Salary — a range, and whether it is gross or net
- Location — and whether remote or hybrid is possible
- Deadline — a real date
On salary: posts with a range get noticeably more applications than posts that say "negotiable". If you cannot publish a figure, publish the band. Saying nothing does not save you the conversation, it just moves it to the end, after both sides have spent time.
Keep requirements honest. A list of fifteen essentials produces two kinds of applicant: the one who ignores lists, and the one who was already overqualified. Strong candidates who meet eight of ten often do not apply at all. Ask for what the job needs in the first six months.
Write to a person
- "You will own the monthly reconciliation" reads better than "the successful candidate shall be responsible for..."
- Cut anything you would not say out loud in an interview.
Before you publish
- Would someone outside your organisation understand every acronym?
- Is the deadline real, and will you actually reply by then?
- Does the post say what happens next after applying?
On ONFIVEE the posting form has separate boxes for Summary, Responsibilities, Requirements, Benefits and How to apply, with a live preview. Fill each one. A post built from those sections displays properly on the public page and in Google's job results — a single block of text does neither.