Job Descriptions Are Mostly Useless If You Write Them Wrong
Most job descriptions I see are either wall-of-text resumes disguised as hiring documents or vague wish lists that attract the wrong candidates. The difference between a posting that brings in good applicants and one that brings in spam usually comes down to a handful of specific choices. I have written hundreds of these over the years, and the pattern is pretty consistent. A job description is a document that outlines the responsibilities, qualifications, and working conditions of a role. It serves two audiences simultaneously: candidates who need to decide whether they should apply, and hiring managers who need a reference point for evaluating people against the role. When you treat it as just a compliance document for HR, it fails. When you treat it as a filter and a promise at the same time, it works. The key elements that actually matter are narrower than most people think. Here is what belongs in one.
Role title. Use the standard industry title. If the role is a "Revenue Operations Manager," do not call it a "Growth Evangelist." Candidates search using existing terminology, not internal branding. I once spent six weeks trying to fill a position titled "Customer Success Wizard" and realized too late that nobody was finding the posting. We renamed it to "Account Manager" and received qualified applications within 48 hours. The content stayed the same. The title was the only thing that changed. Position summary. Three to five sentences explaining what the person will actually do day to day and why the role exists. Avoid corporate filler like "dynamic environment" or "fast-paced culture." These phrases add zero information and signal that the writer is padding space. A good summary answers: what problem does this role solve for the organization? Responsibilities. This is the core of the document. List the actual tasks. Not aspirational ones. I prefer the 5 to 8 bullet format, starting each with an action verb. Be specific about scope. "Manage social media accounts" is meaningless. "Manage the company's LinkedIn and Twitter accounts, producing three posts per week and monitoring engagement metrics" tells the candidate exactly what the work looks like. One mistake I keep seeing is listing 15 responsibilities for a mid-level role. Candidates read that and assume the title is inflated or the workload is unsustainable. Keep it tight.
Qualifications. Separate required qualifications from preferred qualifications. This distinction matters more than people realize. Required qualifications are hard filters. Preferred qualifications are nice-to-haves that help you rank candidates. When you merge them into one undifferentiated list, you either screen out good candidates who lack something minor or you attract unqualified applicants who check every box on paper. I once had a hiring manager reject a strong candidate because they did not have experience with a specific internal tool we used. That tool was never listed as a requirement. It took three more months to backfill the role. Compensation range. This is increasingly expected and in many locations legally required. Including a range upfront saves everyone time. Candidates who fall outside it will self-select out. Candidates who fall inside it will apply with more confidence. Omitting it tends to attract only the casual browsers and lose the candidates who have other offers on the table. Work arrangement. Remote, hybrid, or on-site. Be explicit about the expectations. "Hybrid" means different things to different people. Specify how many days in office, if any. This is one of the fastest sources of candidate dropout after an offer is extended. People discover the commute or office expectation too late and decline.
Get the Full Details
There is a common misconception that job descriptions need to be exhaustive. They do not. The goal is not to describe every possible task someone might encounter. The goal is to describe the role accurately enough that the right people self-select in and the wrong people self-select out. A job description that is too detailed becomes a constraint rather than a guide. I learned this the hard way when we posted a data analyst role with 22 responsibility bullets. We received 340 applications, and 90 percent of them were completely unsuited because they thought the role was more of a senior architect position than a mid-level analyst role. We rewrote it to 9 bullets and got 60 applications, half of which were genuine fits. Another counter-intuitive point: the qualifications section should often be shorter than the responsibilities section. Responsibilities paint the picture of the actual work. Qualifications are just the threshold. Lead with what the person will do, then state what they need to have done it before. Most postings get this backwards by leading with a long list of degree requirements and certification preferences before anyone knows what the job actually entails. There are also situations where the standard job description format fails completely. Contract roles, internships, and cross-functional positions often do not fit neatly into the responsibilities-qualifications structure. For a contract role, the timeline and deliverables matter more than the day-to-day tasks. For a cross-functional role, you need to explicitly acknowledge the reporting ambiguity rather than pretending a single manager owns the position. I handled one case where the role reported to both engineering and product leadership. We included a dedicated section explaining the dual-reporting structure and how decisions get made. It cut our interview cycle time in half because candidates understood the dynamics before they even entered the room.
If you want a practical template structure, this is what I fall back on without thinking: Role title at the top. A one-paragraph summary. A responsibilities section with 5 to 8 bullets. A qualifications section split into required and preferred. A compensation range. A work arrangement note. That is it. Anything beyond that is usually noise. Occasionally you add an benefits section or a company description, but those are secondary to the actual role content. The biggest bottleneck in writing good job descriptions is not knowing the role well enough. The best descriptions come from people who have worked in the role or closely observed someone doing it. When you write from a policy perspective rather than a practical one, the language drifts toward generic. You end up with phrases like "collaborate with stakeholders" and "drive results" because you do not know what the actual collaboration looks like or what measurable results are expected. Sit down with the person currently doing the job, or the person who will report into it, and ask what they actually spend their time on. Build the description from that answer.
