
Writing a job description is one of the most critical steps in the recruitment process. My approach focuses on making it clear, inclusive, and performance-driven so you attract the right candidates while weeding out mismatches.
Start with the core basics. The job title must be accurate and searchable—avoid internal jargon or creative fluff like "Rockstar Ninja." Use standard terms that candidates on Google or LinkedIn would actually search for.
Craft a compelling "About the Role" section. This is your elevator pitch. In 2-3 sentences, explain the purpose of the role, the team structure, and the immediate impact the hire will make. For example: "As our Senior Data Analyst, you will build dashboards that directly influence our quarterly product roadmap."
Define the "Must-Haves" vs. "Nice-to-Haves." This is where structured interview criteria starts. Clearly list 3-5 essential qualifications (e.g., "5+ years of Python experience") and separate them from preferred skills (e.g., "Experience with Snowflake is a plus"). This reduces bias and helps candidates self-select.
Be transparent about the salary range. Including a salary range is not just a legal requirement in many states; it builds trust. A 2025 study by SHRM found that job postings with salary ranges receive 40% more qualified applicants.
Focus on outcomes, not just tasks. Instead of saying "Manage social media accounts," say "Grow our LinkedIn following by 15% quarter-over-quarter while maintaining a 4.0 response rate." This attracts high-agency candidates who want to solve problems.
Include a clear "What Success Looks Like" section. Outline what the candidate will achieve in their first 30, 60, and 90 days. This sets expectations and demonstrates your company’s commitment to onboarding.
Use inclusive language. Run your description through a gender-neutral language checker. Avoid words like "aggressive" or "dominant" which can discourage female applicants. Use "results-driven" or "collaborative" instead.
Here is a quick comparison of an unclear vs. a clear job description:
| Feature | Unclear JD | Clear JD |
|---|---|---|
| Title | "Marketing Guru" | "Marketing Manager, Brand Strategy" |
| Requirements | "Must be a team player" | "3+ years of experience managing cross-functional campaigns" |
| Salary | Not listed | $85,000 – $105,000 |
| Success Metrics | "Help grow the company" | "Increase organic traffic by 20% within 6 months" |
Finally, use a simple, scannable format. Use bullet points, short paragraphs, and clear headers. A good job description is a marketing document, not a legal contract. It should excite the right person and respectfully inform the wrong person that this role isn't for them.

I always start with the "Why" before the "What." Why does this job exist? Who will this person work with daily? If I can’t explain that in one sentence, the description is too vague. I also cut the wishlist—listing 15 requirements is a red flag. I keep it to 5-7 total, mixing hard skills with soft skills. And I always test my own description by asking a friend unfamiliar with the role to read it and tell me what they think the job is. If they get it wrong, I rewrite it.

For me, it’s all about the candidate experience. I write the description as if I’m talking to a friend. I avoid buzzwords like "synergy" and "deep dive." I also add a "Who We Are" section that feels human, not corporate. And I never bury the salary. I put it right near the top. It saves everyone time. If a candidate doesn’t see their expected range, they move on, and I don’t waste an interview slot.

I focus on action verbs and measurable outcomes. I ask the hiring manager: "What’s the biggest challenge this person will solve in the first three months?" Then I write that into the description. I also standardize the structure across all our roles—same font, same section headers, same length. This consistency builds our employer brand. Candidates know what to expect from us, which builds trust. And I always include a link to a Glassdoor or a team video to humanize the company.

I take a data-driven approach. I look at our best-performing hires from the last two years and analyze what their job descriptions had in common. I check click-through rates on our job boards and application drop-off points. If 80% of people stop reading after the requirements section, my requirements are too long. I also A/B test different titles for the same role. A title like "Frontend Developer (React)" gets 30% more clicks than "Frontend Engineer" for our company. The data doesn't lie.


