Writing IT Job Descriptions That Actually Attract the Right Candidates

The "Laundry List" Problem

A systems engineer role that requires "AWS, Azure, GCP, Kubernetes, Terraform, Ansible, Puppet, Chef, Jenkins, GitHub Actions, Python, Go, and Rust" is not describing a role — it's describing four roles, or a unicorn. Requirements inflation is the most common failure mode in IT job descriptions, and it disproportionately deters qualified candidates (especially women, who studies show apply only when they meet ~90% of requirements, vs men at ~60%).

Must-Have vs Nice-to-Have

Every requirement in your job description should be classified as either essential (the person cannot do the job without it on day one) or desirable (useful, learnable on the job). List no more than 5–7 essential requirements. Everything else is desirable. Be honest with yourself: if someone has 4 of your 5 essentials and is a fast learner, will you actually reject them? Then those 5 items are not all genuinely essential.

Describe the Work, Not Just the Stack

Candidates — especially experienced ones — want to understand what the role actually involves day-to-day. Replace generic skills lists with specific responsibilities:

Weak: "Manage cloud infrastructure using AWS and Terraform."

Strong: "Maintain and evolve our 40-node AWS EKS cluster using Terraform. Own the IaC codebase in Git. Lead capacity planning conversations with the product team monthly."

Be Honest About Culture and Environment

If the role involves on-call rotation, say so — and say how frequent it is. If the team is small and candidates will wear multiple hats, describe that. If the tech stack is legacy, acknowledge it. Candidates who join under false pretences leave quickly, costing you a rehire.

Salary Transparency

The evidence is unambiguous: job postings with salary ranges receive more applications from better-qualified candidates and reduce time-to-hire. The talent market has shifted — experienced engineers with options routinely skip postings without salary information. Post a range. If your range is uncompetitive, that's a signal to address, not hide.

Interview Process Transparency

Describe your interview process in the job description: how many stages, what format (technical test, whiteboard, portfolio review), and expected timeline. Candidates are interviewing you as much as you're interviewing them. A clear, respectful process is itself a talent attraction signal.