How to write a job post that gets qualified applicants
A job post structure that attracts the people you want and screens out the ones you do not: title, summary, requirements, salary and the apply link.
October 25, 2026. 6 min read.
A job post is read in seconds, mostly on a phone, by someone deciding whether to spend twenty minutes applying. Write for that reader.
The title is the search term
Use the title people search for: “Senior Backend Engineer”, not “Code Ninja” or “Engineer III”. Put the level in the title if it matters. One role per post.
Open with the work, not the company
The first paragraph should say what the person will do and what it changes. Your company story belongs further down; the reader decides in the first three lines.
Separate must-haves from nice-to-haves
- Keep the must-haves to what you would truly reject someone for. Five is plenty.
- Put the rest under “nice to have”. Long requirement lists discourage qualified people from applying at all.
- Prefer outcomes to years: “has run a product launch end to end” says more than “5+ years of experience”.
Publish the salary range
In several US states it is required. Everywhere else, posts with a range attract applicants who already accept it, and save both sides a call that ends at the number.
Say how you work
Remote, hybrid or on-site; time zones; travel; what the interview process looks like and how long it takes. These answer the questions that otherwise arrive by email.
Check the words
Some words read as coded to one gender and can narrow who applies. Our free job post checker marks them and suggests neutral alternatives.
Make applying short
Link straight to the application, not to a careers home page. Ask only screening questions you will actually use; see screening questions that work.
Post it
Posting on Joblex costs 50¢ a day, 5 days at least: live at once, and every applicant arrives with how well they match.