A job description that attracts the right candidates leads with what the role must achieve rather than the job title, and it states a real salary range instead of hiding behind "competitive." The strongest postings get built backwards from a hiring scorecard's outcomes instead of typed out from a template. That one shift usually turns a flood of mismatched applicants into a short list of people who actually fit.

For DACH employers, the stakes are higher than wording alone. Gender-neutral phrasing under the AGG, a stated salary band under the incoming EU Pay Transparency Directive, and works-council posting rights all sit inside the same document, so a job description that skips them creates legal exposure long before it creates a bad hire.

Most job postings fail on a handful of predictable points, and fixing them changes who applies before you change anything else.

What Makes a Job Description Attract the Right Candidates?

A job description attracts the right candidates when it leads with the outcomes the role must produce and lets the wrong applicants self-select out within the first three lines. That means starting with what the person in this seat needs to have accomplished a year from now, not with a job title and a wall of duties that could describe five different companies.

This matters more because a human is rarely the first reader anymore. ATS platforms and AI matching tools now filter up to 75% of applications before a person opens them, scanning for structured, keyword-clear requirements rather than tone. A posting written as a mission statement instead of a specification loses to that filter before a hiring manager ever sees it, which matters even more given the volume of AI-assisted applications now hitting most open roles.

The fix starts earlier than the writing itself. A job description that reads clearly to both a machine and a person is usually one built from a short, specific list of outcomes rather than assembled duty by duty, which is exactly what a hiring scorecard forces you to do before you write a single line of copy.

What Are the 10 Rules for Writing a Job Description That Converts?

Ten rules cover almost every reason a job description underperforms, from a buried salary line to a requirements list copied from three postings ago. Apply them in order and most of the rewrite work below becomes mechanical.

Common mistake: teams over-correct on rule 3 by assuming women only apply when they meet every listed requirement. Controlled research from the Behavioural Insights Team found women apply at roughly 56% of stated requirements met, against about 52% for men, a real but far smaller gap than the "100% versus 60%" claim usually cited. The actual lever is a shorter, cleaner must-have list for everyone, not a separate message aimed at one group.

Why Write the Hiring Scorecard Before the Job Description?

A hiring scorecard should exist before a single word of the job description does, because its outcomes are what the responsibilities section is supposed to describe. Writing the JD first almost always produces a duty list borrowed from the last posting, while writing the scorecard first forces a specific answer to what this hire needs to deliver in the first six to twelve months.

The clearest version comes from Geoff Smart and Randy Street's Who method, built from more than 1,300 hours of interviews with company founders and CEOs. It defines a role through a one-line mission, three to eight measurable outcomes, and the competencies needed to hit them, all decided before sourcing starts.

The scorecard-to-JD link, in practice: the mission line becomes your opening sentence. Turn each measurable outcome into one bullet in the responsibilities section, phrased as a result you want rather than a task to perform. Your must-have list, meanwhile, is just the competencies section written out for a candidate audience. Smart and Street report a roughly 90% hiring-success rate for teams using this method, against roughly 50% for typical unstructured hiring.

Once outcomes exist on paper, "three responsibilities, not fifteen" stops being a style preference and becomes a transcription job. That is also why the five rewrites below all read shorter after editing: cutting duties down to outcomes removes the padding rather than compressing good content.

What Must a DACH Job Description Get Right on AGG, Pay Transparency and Works Councils?

A DACH job description has to be worded gender-neutrally under the AGG, disclose an honest salary indication under the incoming EU pay-transparency rules, and respect any works council's right to see the role posted internally first. Get any of these three wrong and the cost shows up as a fine or a blocked hire, not as a slightly weaker read.

Germany's AGG requires postings to address all three legally recognized genders and bans wording that effectively excludes any of them, with non-compliant ads exposed to compensation claims of up to three months' salary. Once discriminatory wording is shown, courts apply a reversed burden of proof, so the employer, not the rejected applicant, has to prove the rejection wasn't discriminatory. That is the practical reason the "m/w/d" suffix shows up on almost every German-language posting: no single law spells out the exact abbreviation, but a Hamburg labour court has confirmed it satisfies the neutrality requirement, and skipping any gender-neutral marker is treated in practice as a live AGG risk.

The EU Pay Transparency Directive adds a second layer: employers must disclose an initial salary or salary range before or in the job posting, and can no longer ask candidates about their salary history. It aims to close a gender pay gap the European Commission still puts at 11.1% EU-wide, but transposition has been uneven. Member states had until 7 June 2026 to implement it, and by that deadline only Slovakia, Italy, Lithuania and Malta had full legislation in force, with Germany and Austria still not fully transposed. Writing a real range now is still the safer bet, since the obligation is arriving regardless of the exact timeline in your market.

Good to know: German works councils can require that open roles be posted internally before external hiring, under §93 BetrVG, and can refuse to approve a hire under §99 Abs. 2 Nr. 5 BetrVG if that internal posting was skipped or used different requirements than the external one. The Federal Labour Court confirmed in 2022 that this internal posting cannot be made up for retroactively once a consent dispute is already underway, so it has to happen before you draft the external ad, not alongside it.

Dense legal boilerplate copied wholesale from a template law firm's sample text is the last conversion killer, and it is avoidable. Nothing above requires paragraphs of legalese: "m/w/d" in the title, one sentence naming the salary band, and a note that the role was posted internally per works-council policy cover the compliance ground without turning the posting into a contract. Compliance and candidate experience aren't separate workstreams either, since a posting that reads as evasive or bureaucratic damages the same trust that candidate-experience friction points chip away at later in the process.

What Do Five Real Job Description Rewrites Look Like?

Five worked examples show the same pattern across very different roles: cutting the duty list to outcomes, splitting must-haves from nice-to-haves, and naming a real number instead of a placeholder. Each rewrite below applies specific rules from the list above, tagged so you can trace which change did the work.

Software Engineer: From Stack List to Outcome-Led Pitch

A typical bad posting opens with a technology inventory and a request for "5+ years of experience," a phrasing that is fading fast: only around 30% of US postings still require a specific number of years, down from about 40% in 2022, as hiring shifts toward proof of skill over tenure.

Rules applied: 1, 4, and the years-to-evidence shift behind rule 2. Salary band: €44,000-49,000 mid-level, €56,000-71,500+ with technical leadership scope.

Sales (Account Executive): From Quota Threat to Compensation Clarity

Sales postings bury pay structure most often, which backfires with a candidate pool that reads comp mix as a signal of how the company treats revenue generators. Standard structures exist and naming them builds trust: SDR and BDR roles typically run 60/40 to 70/30 base-to-variable, full-cycle Account Executive roles sit at 50/50, with quota commonly set at 4-6x on-target earnings. That's a US-market benchmark, so borrow the ratio, not the euro amount.

Rules applied: 4, 5 and 10. Base range benchmarked against the €2,493-4,155/month Austrian Sales Manager anchor, before variable pay layers on top.

Product Manager: From Buzzword Bingo to Scorecard Outcomes

Product Manager postings make the strongest case for writing the scorecard first, since "strategic," "cross-functional" and "roadmap owner" describe almost every PM job ever posted without describing this one.

Rules applied: 1 and 3, plus rule 6, naming the hiring manager and interview stages right after. We're deliberately skipping a salary figure here: publish the real internal band, whatever it is, rather than a scraped average that may not match your actual pay structure.

Frontline / Retail Ops: From Duty List to Honest Shift and Pay Reality

Frontline and operations postings tend to over-list duties while under-specifying the one variable candidates actually plan their lives around: the shift pattern and the real pay floor.

Rules applied: 2, 5 and 8, real range and real schedule instead of "fast-paced" doing the work of both. The €2,090-6,022/month range set by Austria's Handel-Kollektivvertrag is the legally binding floor to quote from, not a job-board average.

Marketing Manager: From Rocket-Ship Clichés to Specific Wins

Marketing postings collect almost every cliché at once: "passionate storyteller," "data-driven," "wears many hats," none of which tells a strong marketer what they'd actually be measured on.

Rules applied: 1 and 4, plus a 2026-specific addition, naming AI-tool comfort as a nice-to-have rather than assuming it. Salary band: €2,349-3,915 gross/month, benchmarked against karriere.at's Austrian Marketing Manager figures.

Where a Better Job Description Actually Pays Off

The real return on a rewritten job description shows up before the first interview, in who applies at all. A posting built from scorecard outcomes, an honest range and a short must-have list reads better, sure, but the bigger effect is on who actually shows up in your pipeline on day two.

That payoff depends on where the posting itself lives, though. A rewrite does little good if it sits disconnected from how candidates actually apply. That's why we built Sprad as an AI-first ATS with a free career page and built-in multiposting, so the job description you just rewrote gets out, gets distributed, and hooks straight into your candidate pipeline in one workflow, not three disconnected tools.

So next time, open the scorecard before the old job ad. Write down the three outcomes and the responsibilities section mostly writes itself.

Frequently Asked Questions

How long should a job description be?

Response rates peak for postings around 500-749 characters, roughly 300-700 words, and drop sharply once a posting passes roughly 4,000 characters. Separate LinkedIn data shows postings under 300 words convert 8.4% more applicants than average, so trimming duty lists down to real outcomes tends to land you in the sweet spot automatically.

Do job postings in Austria and Germany legally need to include "m/w/d"?

No single law mandates that exact abbreviation, but it functions as the de facto standard for AGG compliance. A Hamburg labour court has confirmed "m/w/d" wording is read as inclusive of all three legally recognized genders, and omitting any gender-neutral marker is treated in practice as a discrimination risk.

Can a works council block a job posting or a hire in Germany?

Yes, under §93 and §99 BetrVG a works council can require internal postings before external hiring and refuse to approve a hire if that step was skipped. Germany's Federal Labour Court has confirmed the internal posting cannot be added retroactively once a consent dispute is already underway.

Is a salary range legally required in job ads under the EU Pay Transparency Directive yet?

Not uniformly. The directive required member states to transpose it into national law by 7 June 2026, but only Slovakia, Italy, Lithuania and Malta had full legislation in force by that deadline, with Germany and Austria still not fully transposed. Posting a real range now is still the safer, lower-friction path regardless of the exact legal timeline in your market.

Should a job description still ask for years of experience?

It's increasingly optional rather than default. Only around 30% of US postings still require a specific number of years, down from about 40% in 2022, as employers shift toward describing measurable outcomes and skills instead of tenure thresholds.