Job Description

A document outlining a role's responsibilities, qualifications, and expectations — more useful as a strategic tool than most candidates realize.

A job description is the official document that defines a position: its title, reporting structure, key responsibilities, required and preferred qualifications, and increasingly its compensation range. Job descriptions serve multiple purposes simultaneously: externally, they attract candidates; internally, they define the performance expectations, leveling criteria, and scope of the role; legally, they establish what a job entails for compliance, accommodation, and classification purposes. The same document serves different masters, which is part of why it's rarely a perfectly accurate representation of what the job actually is.

The gap between a job description and the actual role is often significant. JDs are written at a point in time, frequently by HR in consultation with a hiring manager who is busy, and they're rarely updated when the role evolves. A JD written six months before a hire may reflect the team's needs at a different size, stage, or strategic priority. Requirements marked as 'required' are frequently aspirational wish lists rather than genuine minimums — particularly the year-of-experience requirements that research shows have weak empirical basis in predicting job performance.

Job seekers routinely under-apply because of how they read job descriptions. Candidates — disproportionately women and underrepresented groups, according to research — often interpret 'required' qualifications as hard minimums and self-screen out if they don't meet every criterion. In practice, requirements exist on a spectrum: some are genuine non-negotiables (an active CPA license for a Controller role), and most are rough guidelines where a strong relevant background compensates for gaps. If you meet 60–70% of the listed requirements and the role is genuinely relevant to your background, applying is worth the time.

The JD is also a strategic document to use throughout your interview process, not just at the application stage. The language, emphasis, and ordering of responsibilities reveal what the team cares about most. The qualifications section signals what the hiring manager believes is necessary vs. ideal. The tone indicates the culture. And if a salary range is listed, it's your primary data point for anchoring a negotiation. Candidates who read a JD once and move on leave significant information on the table.

How to Read a Job Description Strategically

  • Lead responsibilities (top 3 bullets) are what the role actually does — the rest is context. Orient your resume and interview prep around the top priorities.
  • Year requirements are guidelines: strong, directly relevant experience frequently substitutes for formal years. Apply if you meet 60–70% of criteria.
  • The tone of the JD signals culture: formal bureaucratic language vs. casual conversational language, 'you will' vs. 'we're looking for someone who' — these are real signals.
  • Salary ranges, when included, are your anchoring data for negotiation — the midpoint is roughly where they expect to land.
  • Mirror JD language in your resume — ATS systems keyword-match directly from the job description text.
  • Research whether the role is a backfill (someone left) or newly created — backfills have clearer requirements; new roles often have more flexibility on scope.

Red Flags in a Job Description

  • Laundry list of requirements: an excessive list of specific tools and technologies often means the JD was written by committee and no one prioritized.
  • Vague responsibilities: 'other duties as assigned' or extremely generic bullet points may indicate a poorly defined role or one that changes frequently.
  • Mismatched level and compensation: a director-level JD with individual contributor pay suggests the company hasn't resolved what they actually need.
  • Requirement inflation: asking for 10 years of experience in a technology that's been widely available for 5 years — signals either a copy-paste JD or a screening mechanism unrelated to actual need.
  • No mention of team or reporting structure: a JD that doesn't describe the team context or who the role reports to is worth questioning in the screening call.

Example

A job seeker sees a posting requiring '5+ years of Python experience.' She has 3.5 years but has used Python across complex ML and data pipeline projects. Knowing that specific year requirements are frequently guidelines and that her project depth is strong, she applies with a tailored resume that mirrors the JD's language. She lands the role — the hiring manager later says the year requirement was a rough signal, not a hard cutoff.