A job description template is a reusable skeleton that turns an open role into a clear, fair posting in minutes instead of a blank-page struggle. You get 12 free job description templates here, one per common role type, as ready-to-copy Word and Google Docs files with a DACH-compliant variant built in.

Search for a job description example or a sample job description and you mostly find one generic template, a library of a thousand roles gated behind a lead form, or an AI generator that writes something forgettable. None of that here. Every outcome sentence comes from a hiring scorecard, and every DACH variant strips out the language that creates AGG liability. The role details also reflect how candidates actually read a job ad in 2026, favoring proof of skill over a headcount of years.

What Belongs in a Job Description Template That Recruiters Actually Reuse?

A job description template that gets reused, not abandoned after one posting, follows one repeatable skeleton instead of a blank page every time a role opens. SHRM's own job description toolkit confirms that this same structure shows up across nearly every strong job description example, and it holds together because each part answers a different question a candidate is silently asking before they click apply.

How long should a sample job description actually run? The best-performing postings land between 300 and 700 words, and Ongig's word-count analysis shows postings past 600 words earn slightly more applications per view, not fewer, because the extra length keeps qualified readers engaged rather than scaring them off. A 12-role template set only works inside that range: once a role's write-up runs longer, it usually means the responsibility list got padded with tasks the scorecard never actually flagged as outcomes.

This is not an arbitrary house style. It matches SHRM's job description guide almost field for field, which is exactly why the same six-part shape works underneath all 12 templates below, whether you paste it into Google Docs or a job description template Word file.

How Does a Hiring Scorecard Become the Job Description's Outcome Sentence?

The outcome sentence in a job description template should be a near-direct copy of the scorecard's mission line, and each of the three core responsibilities should restate one of the scorecard's top-ranked outcomes as a duty rather than the other way around.

Geoff Smart and Randy Street's "Who" hiring method builds every role around a scorecard with three parts: a mission (a one to five sentence executive summary of why the role exists), typically three to eight ranked, measurable outcomes, and a set of behavioral competencies. The method treats a task-list job description as the weaker document. A traditional posting just lists activities like calling on customers and selling. A scorecard names the number the person has to move, say growing revenue from $25M to $50M by year three. A hiring manager can actually defend the scorecard version in a debrief. With a generic task list, you rarely have anything solid to point to.

In practice, the swap takes three steps. Pull the scorecard's mission line and drop it in almost verbatim as the opening outcome sentence. Take the top three of the scorecard's ranked outcomes, usually the three with the highest business weight, and reword each into a present-tense responsibility. Leave the remaining outcomes and the competencies out of the posting entirely, since they belong in the interview scorecard, not the public job ad.

The 12 Free Job Description Templates: One Word + Google Docs Download per Role Type

Each of the 12 templates below follows the same six-part structure from the first section, pre-filled with a role-specific outcome sentence, a must-have signal, and an AI-tool clause matched to what 2026 postings in that function actually ask for.

Take the Software Engineer template as a worked example of how the fields fill in. The outcome sentence, pulled straight from a scorecard mission line, might read: "Ship reliable product features that take the team from three releases a quarter to one every two weeks." The three responsibilities restate the scorecard's top-ranked outcomes. One is owning a feature area end to end. Another is cutting production incidents traced back to the team's own code. The third is mentoring two engineers toward their first shipped feature. The must-have is a proven shipping history in the actual stack, not a minimum-years threshold, and the nice-to-have line covers comfort with an AI pair-programming tool, since roughly a third of tech postings now name AI-tool fluency as a skill.

To turn any row into a finished document, duplicate the six-part structure once and paste in that role's outcome sentence, must-have signal, and AI-tool clause. If your team standardizes on a job description template Word file rather than Google Docs, the same six fields carry over identically, only the file extension changes.

How Do You Make a DACH Job Description Template AGG-Compliant?

A DACH-compliant job description template needs four fixed elements. The abbreviation "m/w/d" belongs directly after every job title. Gender-inclusive noun forms need to carry through the entire body text. A stated salary range or minimum has to appear. Any sentence referencing age, marital status, or physical traits has to come out.

German labor courts have already tested the first element. A Landesarbeitsgericht Hamburg ruling confirmed that "m/w/d" is a legally sufficient, gender-neutral way to write a job title, but the safeguard only holds if the rest of the posting also stays neutral. A title that reads "Softwareentwickler (m/w/d)" next to body copy full of masculine-only nouns and phrases like "junges, dynamisches Team" does not meet that bar, so a neutral title over masculine-heavy body copy still leaves you exposed. The same discipline pays off outside Germany too: LinkedIn's own talent data found that masculine-coded words such as "aggressive," "dominant," or "rock star" measurably reduce how many women apply, with men applying 13% more often after seeing the same posting.

Salary disclosure sits on two different legal tracks in DACH. Austria's Gleichbehandlungsgesetz has required every job posting to state the applicable collective-bargaining or statutory minimum salary since 2011, independent of any EU timeline, and violations carry fines. Germany's obligation is still catching up: the EU Pay Transparency Directive bans asking about salary history and pushes toward disclosing a range before the first interview, but transposition into national law is incomplete in several member states, Germany among them, so a German template should treat a stated range as best practice rather than a single settled national rule.

What one bad sentence can cost. Under Germany's AGG, a rejected applicant can claim up to three months' gross salary if a posting was not gender-neutral, and they only have to show facts suggesting discrimination, not prove they would have gotten the job otherwise. Haufe's legal analysis lays out exactly how that burden shifts to the employer. IHK Wiesbaden has worked the math on a worst case: 50 rejected applicants at three months of a €3,000 salary works out to roughly €45,000 in potential exposure from one poorly worded ad, before legal costs. A recognized pattern known as "AGG-Hopper" describes applicants who apply with no real interest specifically to collect that compensation after a foreseeable rejection, which is the main reason careful, documented wording matters more than it looks.

A friction-heavy or non-compliant posting does not just create legal exposure. It also shapes how candidates talk about your company afterward, which is exactly what our guide to DACH candidate-experience friction points digs into. Teams evaluating AI screening or interview tools alongside their job descriptions should also check the GDPR and EU AI Act angle covered in our AI recruiting compliance guide.

Sentences to Strip Out of Any DACH Template

What 2026 Candidate Expectations Should Every Template Reflect?

Three shifts change what belongs in a 2026 job description template: a remote or hybrid signal now stands out precisely because it is rarer, an AI-tool literacy line matched to the specific function, and requirements framed around outcomes instead of a years-of-experience threshold.

Advertised flexibility has compressed sharply rather than expanded. Robert Half's Q2 2026 analysis found 87% of postings fully on-site versus 65% just two quarters earlier, with hybrid and fully remote roles shrinking to a combined 13%. That figure is US-sourced and other trackers show a less severe drop, but the direction is consistent enough that stating a genuine remote or hybrid option in a template is now a real differentiator for desk-based roles such as Software Engineer or Data Analyst.

AI fluency is growing faster than any other requirement. The number of workers in occupations where AI fluency is explicitly required grew roughly sevenfold in two years, from about 1 million in 2023 to around 7 million in 2025. That growth is not evenly spread: it shows up in close to half of data and analytics postings but under 10% of HR and finance postings today, which is exactly why each of the 12 templates above carries its own AI-tool clause instead of one generic line.

The years-of-experience threshold is also fading from postings that want to compete for skilled applicants. SHRM research finds recruiters are now 50% more likely to search for candidates by skill than by years of experience, and the share of US postings requiring a specific number of years fell from 40% in October 2022 to 32.6% two years later. Every outcome sentence here does the same thing on purpose. "Grow revenue from a named territory" tells you whether someone can do the actual work. "3+ years in sales" just tells you how long they've been around, which tells you nothing about whether they can do it.

An application form can undo all of that groundwork in seconds. SHRM reports that 92% of candidates who click "Apply" never finish the application, with well-designed forms completing in under five minutes. That is the entire argument for keeping the application step in every template to one sentence. It is also part of why application volume itself has become harder to manage, a problem covered in more depth in our piece on handling the AI-applicant flood before it buries your team.

How Do You Adapt a Template in 15 Minutes Without Breaking It?

Adapting one of these templates to your own company takes about 15 minutes as long as you touch only four fields. Everything else can stay as your standing corporate default.

The two most common editing mistakes both happen fast, and both quietly undo the template's value. The first is copying an outcome sentence from a similar but different role's scorecard, so the responsibilities drift back into a generic task list within a paragraph or two. The second is reusing a Germany-vetted AGG paragraph in an Austria posting without adding the GlBG's mandatory minimum-salary line, or the reverse, which leaves a compliance gap that reads as copied rather than tailored.

A finished template only becomes useful once it is live somewhere candidates can actually find it. An AI-first ATS like Sprad's free applicant tracking system changes what happens next: publish the finished job description to a hosted career page, multipost it straight to DACH job boards, and connect it to the same pipeline that tracks every applicant, all from one workflow. Then the template does more than sit in a shared folder, it kicks off the actual hire.

The Real Win Comes the Second Time You Open the Template

It pays off most the second time you use it. Once a role's scorecard mission line, must-have signal, and AGG wording are set, reopening that role next quarter takes minutes, and the posting is already tighter than anything written from a blank page.

Start with the role you are hiring for next. Confirm its scorecard mission line before you touch the template, then fill in the matching outcome sentence and must-haves from the table above. Run the DACH-compliance checklist if the posting is for Germany or Austria, and publish it somewhere the pipeline is already tracking applicants.

Frequently Asked Questions

How long should a job description example be before it starts hurting application rates?

Between 300 and 700 words performs best across most roles, according to Ongig's analysis of job posting length. Postings past 600 words can even earn slightly more applications per view, since the extra detail helps qualified candidates stay engaged rather than losing interest early.

Do you still need "m/w/d" if the rest of the job description is already gender-neutral?

Yes, keep "m/w/d" directly after the job title regardless of how neutral the body text already reads. German courts have upheld it as the standard safe form for the title itself, but that protection only applies when the surrounding text stays neutral too, so both parts have to be checked together.

Can one hiring scorecard support more than one job description template?

Only when two openings genuinely share the same mission and ranked outcomes, such as two Account Executive roles covering similar territories. Otherwise, no. Most roles need their own scorecard, because the specific revenue target, deadline, or output number in the mission line rarely transfers cleanly from one opening to another.

What's the biggest legal difference between a DACH and a US-style job description template?

Austria's requirement to state the applicable minimum or collective-bargaining salary has applied since 2011, independent of any EU deadline, while most US templates carry no equivalent mandate yet. Germany sits in between: no finalized national salary-disclosure law yet, but AGG liability already makes gender-neutral wording a hard requirement.

Why do 2026 job descriptions skip "years of experience" more often than older templates?

Recruiters increasingly search and screen by skill rather than tenure, with SHRM research showing they are now 50% more likely to search by skill. The share of postings requiring a specific number of years also fell from 40% to 32.6% over two years, so outcome-based requirements now read as more current to candidates.