Why Most Job Descriptions Fail
The average job description on any job portal is a copy-paste of last year's version with a salary range deleted and a new requirement for "5 years of experience with a 3-year-old technology" tacked on. Top candidates read three lines and close the tab.
The Anatomy of a Job Description That Works
1. Start With the Problem, Not the Title
Open with one paragraph describing the challenge the new hire will solve. "We are building a multi-tenant SaaS platform for recruitment agencies and we need a backend engineer to design the subscription and billing engine" is infinitely more compelling than "We are looking for a Software Engineer."
2. Describe the Day-to-Day Reality
Be specific: "You will spend about 60% of your time writing PHP/Laravel code, 20% in design discussions, and 20% in code reviews and mentoring a junior engineer." Candidates self-select into roles that match how they actually want to spend their time.
3. Separate Must-Haves From Nice-to-Haves
The research is clear: men apply when they meet 60% of requirements; women and underrepresented candidates apply only when they meet nearly 100%. Keeping your must-have list to five or fewer concrete skills opens your pipeline to better candidates.
4. Be Transparent About Salary
Job listings on JOBNT with salary ranges visible receive 47% more qualified applications. Post a range. It saves everyone's time and signals organisational respect for candidates.
5. Describe Your Culture Concretely
Avoid "fast-paced, collaborative environment." Instead say "We do weekly planning, async standups on Slack, and one team offsite per quarter. Everyone ships to production."
A Template You Can Use Today
Role: [Title] | Team: [Team Name] | Location: [Remote / City] | Salary: [Range]
The Problem You'll Solve: [One paragraph]
Your Day-to-Day: [Bullet list of 4–5 real tasks]
Must Have: [3–5 items]
Nice to Have: [2–3 items]
What We Offer: [Salary, remote policy, leave, growth]
Recent Jobs For You
Add Comment
Login to leave a comment.