How to Write a Job Description That Attracts the Right Candidates
Most job descriptions are written for legal compliance, not for the candidates who will actually read them. The result is a flood of mismatched applications. Here is how to write one that filters for fit.
The job description is the first conversation a candidate has with your company. It runs every hour of every day, in front of every applicant, before anyone speaks to them. Most companies still treat it like a formality - a list of requirements copied from the previous posting, padded with corporate language about being "dynamic" and "results-oriented" - and then wonder why the resulting applicant pool is mostly mismatched. A job description that does its job filters out wrong-fit candidates before you spend an hour reviewing their CV.
Start with the actual work, not the company. The first paragraph should describe what the person hired into this role will spend their time doing in the first six months. Specific projects, the tools or stack they will use, the people they will work with, the problems they will own. Candidates skim - and what they want to know first is whether this job is the kind of work they want to do every day. Boilerplate about your mission can come later or be cut entirely.
Be honest about scope. If the role involves significant on-call rotations, customer support, or frequent context switching across products, say so. If 30 percent of the role is process and meetings, do not describe it as a "deep technical individual contributor role." Misleading descriptions waste your time at the interview stage and burn the candidate's trust if they take the job and discover the gap later. The best candidates have options - they will choose the company that was straight with them up front.
Separate must-haves from nice-to-haves clearly, and keep the must-haves short. A common mistake in Armenia is listing every technology the company has ever used in production as a requirement. Three or four genuine non-negotiables produce a better applicant pool than a list of fifteen. If you list React, TypeScript, GraphQL, AWS, Docker, Kubernetes, PostgreSQL, Redis, and "5+ years experience" as required, qualified mid-level candidates will skip the listing because they do not check every box. Write what you actually need; mark the rest as bonus.
Include the salary range if you can. Listings with a range get more applications and better-fit applications than listings without. Candidates who need more than your max do not waste your time; candidates whose expectations match self-select in. If your company is not yet ready to disclose ranges publicly, at least include them internally and tell recruiters to mention them in the first conversation. Hiding compensation until the offer stage produces drop-offs you could have avoided.
Finally, write the description for one specific person. Picture the kind of engineer or specialist you actually want to hire - their experience level, their motivations, what they would find boring or exciting - and write to them. A job description aimed at one specific archetype outperforms a generic posting aimed at "anyone vaguely qualified." That is true in San Francisco, Berlin, and Yerevan equally. The companies on workx.am that hire fastest are usually the ones whose job posts read like they were written for a specific human, because they were.
