Building Better Job Descriptions

Why job descriptions often fail before the vacancy is even advertised

Many job descriptions are written as a compromise: a bit of the old role, a few new tasks, a long list of desirable traits and a title that sounds better than the work actually is. The result is predictable. Strong candidates self-select out because the role looks unclear or overloaded. Others apply because the wording is broad enough to fit almost anyone. Hiring teams then spend time interviewing people against an unspoken version of the job that was never written down.

When building better job descriptions, the first task is to make the role usable. A good description should help three groups at once:

• Recruiters need a clear basis for sourcing, screening and explaining the role.
• Employers need a realistic picture of what success looks like in the first 6 to 12 months.
• Careers advisers need a reliable reference point to help candidates judge fit and prepare evidence.

If the description cannot support those decisions, it is not yet ready for market.

Start with the job, not the person

A common mistake is to write the job description from the shape of the ideal candidate rather than the needs of the role. That leads to inflated requirements such as “must have sector experience”, “degree preferred”, “excellent communicator” and “team player” without any explanation of why those traits matter.

Instead, define the role in this order:

1. Purpose: What is this job for?
2. Outputs: What must the person deliver?
3. Context: Who do they work with, what systems do they use and what constraints exist?
4. Success measures: How will you know the hire is working?
5. Capabilities: What knowledge, skills and behaviours are truly needed?

This sequence keeps the description anchored in evidence. It also makes later assessment easier because each interview question or test can be tied back to a real job need.

A simple role-definition template

Use these prompts before drafting the advert:

• What problem does this role solve?
• Which tasks happen weekly, monthly and occasionally?
• Which tasks are essential on day one, and which can be learned?
• What does good performance look like after 3 months?
• What would make someone fail in this role?

If the answers are vague, the job description will be vague too.

Separate essentials from preferences

One of the most useful habits in building better job descriptions is to split requirements into three categories:

• Must have: Without this, the person cannot do the job safely or effectively.
• Should have: Strongly helpful, but trainable or transferable.
• Nice to have: Useful if present, but not a reason to reject a capable candidate.

This is where many roles become more inclusive and more accurate. For example, a customer operations role may not need “3 years in the same sector”; it may need evidence of handling complaints, using a CRM and working to service levels. A project support role may not need a specific degree; it may need planning, prioritisation and written communication.

Decision question: if a candidate lacked this requirement but could learn it quickly, should it really be a barrier?

That question helps teams avoid turning preferences into hidden exclusions.

Write for evidence, not aspiration

Job descriptions often contain broad claims such as “excellent stakeholder management” or “strong commercial awareness”. These phrases sound polished but do not tell candidates what evidence they need to show. Stronger wording is more concrete.

Compare:

• Weak: excellent communication skills
• Better: able to explain technical information clearly to non-specialists in meetings and written updates
• Weak: strong leadership potential
• Better: able to coordinate work across a small team, set priorities and follow through on deadlines
• Weak: good attention to detail
• Better: able to check data, spot inconsistencies and correct errors before submission

This kind of wording helps candidates prepare better examples and helps interviewers assess the same thing consistently.

Use the job description to design fairer assessment

A clear job description is not just an attraction tool; it is the foundation for fair assessment. If the role definition is weak, interviewers tend to improvise. That usually means they ask different questions, value different experiences and make decisions on instinct rather than evidence.

A better approach is to build an assessment map from the job description:

1. List the 5 to 7 capabilities that matter most.
2. Decide how each capability will be evidenced.
3. Match each evidence source to the stage of the process.
4. Use the same criteria for every candidate.

For example:

• CV analysis can help identify whether the candidate has relevant experience, progression, transferable skills and stable patterns of responsibility.
• Role-based tests can check practical ability, such as written communication, numerical reasoning, prioritisation or task handling.
• Interview preparation can be guided by the role’s key outputs so candidates know what kind of examples to prepare.
• One-to-one interview reports can capture structured evidence from each conversation, reducing the risk of relying on memory or first impressions.
• Work style assessment can add context around how someone prefers to work, which may be useful when the role involves pace, autonomy or collaboration.
• Employer candidate overview can bring together the evidence in one place so hiring teams compare like with like.

CareerMapper should be used here as a decision-support and candidate-development platform, not as a replacement for judgement. The value is in making the evidence easier to see, compare and discuss.

A practical framework for deciding what to assess

When building better job descriptions, use a simple three-part filter for every requirement:

1. Is it job-critical?

If the requirement is missing, would the person be unable to do the role properly? If yes, it belongs in the must-have column.

2. Is it observable?

Can you see or test it through a CV, task, interview answer or work sample? If not, the wording may be too vague.

3. Is it proportionate?

Does the requirement reflect the level of the role, or is it borrowed from a more senior post? Over-specifying a role often narrows the pool unnecessarily.

This framework is especially useful for advisers helping candidates interpret adverts. If a requirement is not job-critical, not observable or not proportionate, it should not dominate the decision.

Example: turning a messy vacancy into a usable role profile

Imagine a growing business wants to hire a “dynamic all-rounder” for a small office. The draft advert asks for administration, customer service, social media, event support, finance tasks and “someone who can do a bit of everything”.

That is not a role definition; it is a collection of hopes. A better approach would be to ask:

• Which tasks take most time?
• Which tasks need specialist knowledge?
• Which tasks can be trained?
• What is the real priority in the first six months?

After review, the role may turn out to be primarily office coordination with some customer contact and occasional marketing support. That changes the title, the wording, the salary benchmark and the assessment criteria. It may also change the candidate pool from “generalists who can do everything” to people with strong coordination, service and prioritisation skills.

That is the practical value of building better job descriptions: you stop advertising a fantasy and start hiring for a real job.

How to use CV analysis without over-reading the CV

CVs are useful, but they are not the whole story. A good job description helps recruiters and employers use CV analysis more intelligently.

Look for:

• Evidence of relevant responsibilities, not just job titles
• Progression in scope, pace or complexity
• Transferable experience from adjacent sectors
• Gaps that may need context rather than assumption
• Achievements that link to the role’s outputs

Do not over-weight formatting, length or whether the candidate has used the same language as the advert. A candidate may have the right experience but describe it differently. CareerMapper’s CV analysis can help surface the relevant evidence more consistently, which is especially useful when recruiters are handling high volumes or when advisers are helping candidates translate experience into role language.

Interview questions should follow the job, not the interviewer’s curiosity

Once the role is defined, interview questions should be built around the same evidence points. That keeps interviews focused and fair.

For each key capability, ask:

• What did the candidate do?
• What was the context?
• What was the result?
• What would they do differently next time?

For example, if the role requires prioritising competing deadlines, ask for a time when the candidate had to manage multiple urgent tasks. If the role requires stakeholder communication, ask for an example of explaining a difficult issue to someone with different priorities.

CareerMapper’s interview preparation tools can help candidates practise this kind of structured evidence, while one-to-one interview reports can help employers compare answers against the same criteria after the conversation. That makes it easier to distinguish between a confident speaker and a candidate who can actually do the work.

Where work style assessment fits

Work style matters, but it should be used carefully. A role may require a fast pace, frequent collaboration, a high degree of independence or a strong tolerance for change. If that is true, say so in the job description. Candidates can then judge whether the environment suits them.

Work style assessment can add useful context when used alongside job evidence. For example, a candidate may have the right technical experience but prefer highly structured work. That does not automatically rule them out, but it may prompt a better conversation about support, onboarding and team fit.

The key is not to use work style as a shortcut for personality judgement. Use it to understand how someone is likely to operate in the role, then compare that with the actual demands of the job.

Questions employers should ask before publishing

Before a job description goes live, run it through these checks:

• Could a strong candidate understand what success looks like from this description alone?
• Have we separated essential requirements from preferences?
• Are we asking for experience we actually need, rather than experience we are used to seeing?
• Does the salary and level match the scope of the role?
• Would the same criteria be used in interview, or are we likely to improvise later?
• Have we written the role in a way that supports fair comparison between candidates?

If the answer to several of these is no, the description needs another pass.

How careers advisers can use better job descriptions with candidates

For careers advisers, a well-written job description is a coaching tool. It helps candidates move from “I think I could do this” to “I can evidence this”. Advisers can help candidates:

• Identify the must-have criteria and map them to their experience
• Translate informal or part-time work into relevant evidence
• Spot where a requirement is desirable rather than essential
• Prepare examples for interview using the role’s actual outputs
• Use role-based tests and interview preparation to build confidence

CareerMapper can support that process by giving candidates a clearer view of how their CV, work style and interview evidence align to the role. That does not remove the need for adviser judgement; it strengthens it.

What better job descriptions change in practice

When job descriptions are clearer, several things improve at once:

• Applicants understand the role more accurately
• Shortlists become easier to justify
• Interview questions become more consistent
• Hiring managers spend less time debating vague impressions
• Candidates are less likely to feel misled after appointment

Most importantly, the conversation shifts from “Who looks impressive?” to “Who can do this job well, and how do we know?” That is the standard recruitment teams should aim for.

Building better job descriptions is not about making vacancies longer or more polished. It is about making them more truthful, more usable and more aligned to the evidence you will later need to make a hiring decision.

If you get the role definition right, the rest of the process becomes easier: sourcing improves, assessment is clearer and candidates have a fairer chance to show what they can really do.

Frequently asked questions

What makes a job description “better” rather than just longer?

A better job description is clearer about purpose, outputs and essential requirements. It helps candidates understand the role and helps hiring teams assess evidence consistently. Length alone does not improve quality.

Should every requirement in a job description be treated as essential?

No. A useful job description separates must-haves from should-haves and nice-to-haves. That prevents strong candidates being rejected for preferences that are not truly job-critical.

How can recruiters use a job description to improve shortlisting?

Use the description to define the evidence you want to see in CVs, then compare candidates against the same criteria. CareerMapper’s CV analysis and employer candidate overview can help surface relevant experience more consistently.

How do role-based tests fit into the hiring process?

Role-based tests are most useful when they reflect real tasks from the job description. They can help check practical ability in a way that is more relevant than relying on claims alone.

Can work style assessment replace interview judgement?

No. Work style assessment should be used as supporting context, not as a decision on its own. It can help employers understand how a candidate may operate in the role, but it should sit alongside evidence from CVs, interviews and tasks.

How can careers advisers help candidates with job descriptions?

Advisers can help candidates decode the wording, identify the real essentials and prepare examples that match the role. Interview preparation and one-to-one interview reports can support that process by making the evidence more specific.