
A job description is rarely the work of a single person. In my experience, the most effective descriptions are written by a core team: the hiring manager, a recruiter, and sometimes a senior team member. The hiring manager knows the daily tasks, technical requirements, and team culture. The recruiter understands market trends, salary range benchmarks, and how to phrase requirements to attract a diverse candidate pool.
However, the final "author" is often the recruiter or HR generalist who compiles everyone’s input. I’ve seen many companies make the mistake of letting a busy manager write it alone. That approach often leads to a "wish list" of qualifications that are unrealistic, which hurts the candidate screening process.
Here is a quick breakdown of common pitfalls I’ve observed in job descriptions and who typically causes them:
| Common Mistake | Typical Source | Impact |
|---|---|---|
| Unrealistic qualification list | Hiring Manager | Reduces applicant volume by 40% |
| Vague or generic company culture | Recruiter | Lowers employer brand credibility |
| Missing salary range | HR Generalist | Decreases application completion rate |
| Technical jargon no one uses | Senior Team Member | Confuses passive candidates |
The best practice is a structured review process. The hiring manager drafts the "must-haves" and skills. The recruiter rewrites it for clarity and includes a salary range to comply with pay transparency laws. The team then reviews it for unconscious bias. It’s a collaborative document, not a solo act. The person who "wrote" the job is the one who ensures it is accurate, inclusive, and appealing—that’s usually the recruiter who finalizes it.

Honestly, it’s usually the hiring manager first, but they often mess it up. They write a list of everything they want, which is basically a unicorn. Then the recruiter has to cut it down to something realistic. I’ve seen managers write "must have 10 years of experience" for a tool that’s only been out for five years. That’s a red flag to me as a candidate. The talent retention rate suffers when the job description doesn’t match the actual job.

I think the recruiter writes it, but they’re just copying a template. Every job at my company looks the same. "We’re looking for a passionate, self-starter." It’s meaningless. The real author should be the person who does the job, not HR. If the structured interviews are based on a bad description, the whole hiring process is flawed from the start. It’s just a box-ticking exercise.

From my perspective, a good job description is written by a data analyst. I’m serious. The best ones I’ve seen used data from past hires to find patterns. They looked at which skills actually predicted success, not just what the manager wanted. They focused on candidate experience and used plain language. The "author" wasn’t one person—it was a process of analyzing performance reviews and exit interviews to write something that actually works.

In my niche, the hiring manager writes the technical parts, but the recruiter is the real author. They translate the jargon into English. The manager says "must know Python and SQL." The recruiter rephrases it to "comfortable working with data analysis tools." This improves the candidate screening process because it attracts more generalists who can learn. The recruiter also ensures the employer brand is consistent. It’s a partnership, but the recruiter types the final draft.


