What Your Job Description Says to Candidates (Really)
Updated April 2026
You wrote the job description knowing the team, the culture, and what the role actually involves. A candidate reads it cold in two minutes and decides whether to apply. GapCheck reads it the way that candidate does and tells you where the perception gap is.
Why you are attracting the wrong candidates
The gap between the role you are trying to fill and the role your job description communicates is usually invisible to the people who wrote it. They know what the job actually involves. Every line they wrote made sense in that context. A candidate reading it cold does not have that context. They perceive the role from the copy alone, and if the copy communicates something different from what you intended, you attract a different candidate pool than you wanted.
The strong candidates you want to attract have options. They read job descriptions quickly and with a skeptical eye. A description that reads as generic, overloaded with requirements, or vague about what the role actually involves gives them no reason to apply over one that reads as specific and honest about the opportunity. The perception gap in your job description is part of why the pipeline looks the way it does.
What you get from a GapCheck analysis
- Gap Score (0-100): How close your job description is to communicating the role you intended to fill. Lower means wider gap.
- The one-liner: A blunt summary of how the description reads to a strong candidate seeing it for the first time.
- Specific callouts: 3-5 sections with an honest read on what each one communicates vs. what you intended.
- Intended vs. perceived: A side-by-side of the role you are trying to fill and what a candidate actually perceives from the description.
What a job description gap looks like
Realistic archetypes. Made-up scenarios that represent the patterns GapCheck finds most often in job descriptions.
Reads as a senior IC role dressed up as a leadership position to justify the compensation.
Intended: A high-impact technical leadership role for someone who wants to build and lead a team from the ground up.
Perceived: 12 bullet requirements including 5 years of management experience, plus hands-on coding expectations for a team of 3. Unclear whether this is a manager role or an IC role. Probably both, underpaid for either.
Reads as a generalist marketing role that uses 'Head of' in the title to attract someone more senior than the budget allows.
Intended: A strategic marketing leader who can own demand generation and brand from the ground up with real ownership and upside.
Perceived: Broad scope, unclear reporting structure, no mention of team size or budget. 'Competitive compensation' without a range reads as below-market. The role could be interesting but the description does not make the case.
Reads as a real role at a real company, but the culture section reads as a template that was never updated.
Intended: A closing role with strong comp, clear territory, and a collaborative sales culture for someone who wants to own an enterprise segment.
Perceived: Good comp range visible. Clear role. The 'we move fast and work hard' culture language reads as boilerplate and gives no real signal about what it is like to work there.
Check your job description for free
Paste your job description into GapCheck and get a candidate-cold read with a Gap Score, one-liner, and specific callouts in 30 seconds.
Try GapCheck free →Related
Common questions about job description gap analysis
What is a perception gap in a job description?
A job description perception gap is when the role you described reads differently to candidates than you intended. You wrote it knowing what the job actually involves, what success looks like, and what kind of person would thrive. A candidate reads it cold and may perceive the role as unclear, the requirements as intimidating, or the company as generic. That mismatch between your intention and their takeaway determines who applies and who does not.
Why am I getting the wrong candidates from my job description?
Because the job description is communicating a different role than the one you intended to fill. Job descriptions written by hiring managers are usually accurate about the requirements but vague about the reality of the role: what the day-to-day actually looks like, what kind of person succeeds here, and what makes this opportunity worth leaving a current job for. That gap between what you wrote and what a candidate perceives is why you get applications from people who technically qualify but are not actually the right fit.
What do job descriptions usually get wrong?
Three things. First, a requirements list that reads as a wish list rather than a real bar, causing qualified candidates to self-select out and unqualified ones to apply. Second, generic company culture language that reads as a template rather than a real description of the environment. Third, a role description that focuses on responsibilities rather than outcomes, so candidates cannot tell what success looks like or whether they would be good at it.
How does GapCheck analyze a job description?
Paste your job description into GapCheck and describe the type of candidate you intended it to attract. GapCheck reads it the way a strong candidate would, cold and with a skeptical eye for whether the role is real and the company is worth considering, and scores the gap between your intention and what the description actually communicates.
Can job descriptions with perception gaps discourage good candidates?
Yes. Strong candidates have options and read job descriptions quickly. A description that reads as unrealistic, generic, or unclear about what the role actually involves gives a good candidate no reason to apply over a description that reads as specific and honest. The candidates who do apply to a vague description are often the ones who apply to everything, not the ones you want.
How is GapCheck different from reviewing my job description with HR?
HR reads your job description knowing the company and the team. They review it with that context. GapCheck reads it the way a candidate who has never heard of your company does, cold, without any context, and looking for a reason to apply or move on. Those two reads are usually quite different, and the cold read is the one that determines whether strong candidates apply.
What should a job description actually communicate?
Four things clearly: what the role actually does day-to-day, what success looks like in the first 90 days, what kind of person genuinely thrives in this environment, and why this is a better opportunity than the three other offers a strong candidate is currently considering. Most job descriptions communicate zero of those four things with any specificity.
Does GapCheck work for remote job descriptions too?
Yes. Remote job descriptions have additional perception gaps because candidates are evaluating the remote culture and collaboration style from the description itself. A description that says 'remote-friendly' but gives no signal of what that means in practice reads as an in-person job that reluctantly allows remote. GapCheck will surface that gap specifically if it exists.
What is a good Gap Score for a job description?
A score above 70 means the description is communicating close to what you intended. Between 50 and 70 there is a moderate gap, often in the culture section or the requirements framing. Below 50 means the description reads quite differently from what you intended. Most job descriptions that are attracting the wrong candidates fall between 40 and 60.