I write a job description for the person who must decide whether to apply, not for an internal committee trying to include every possible responsibility. Clarity improves both candidate quality and trust.
I begin with why the role exists
I write two or three sentences explaining the team, the problem, and the outcome the hire will own. I avoid broad company marketing that hides the actual work.
I prioritize responsibilities
I list the five to eight most important duties in approximate order of time or importance. I use direct verbs and describe decisions, stakeholders, and outputs.
I separate requirements from preferences
I include only qualifications that are genuinely needed. If equivalent experience is acceptable, I say so. Inflated years, unnecessary degrees, and long tool lists can exclude capable applicants without improving selection.
I provide practical conditions
I state location, remote or hybrid expectations, schedule, travel, physical requirements where relevant, employment type, reporting line, and compensation range when required or available. “Flexible” should have an operational meaning.
I use inclusive, normal language
I remove coded claims such as “digital native,” “rock star,” or “must thrive under constant pressure.” I focus on behaviors and work requirements.
My final review
- Can a candidate picture a normal week?
- Are the first priorities obvious?
- Does every requirement affect successful performance?
- Are location and schedule clear?
- Does the title match the actual level?
- Would current employees recognize the role?
A job description is also an early promise. If the hiring process later reveals a different job, the employer begins the relationship with avoidable mistrust.