Starting a job description from a blank page is slow, and copying a competitor's brings their problems with it. This page gives you four templates you can copy: a standard full version, a short one for small teams, a version for remote roles, and a version for entry-level and internship hires. Pick the one closest to your role, fill in the brackets, and delete anything that does not apply.
If you want the reasoning behind each section, or want to see a filled-in version, read our full guide on how to write a job description. This page is the toolbox; that one is the manual.
Which template should you use?
| Template | Best for | Typical length |
|---|---|---|
| 1. Standard | Most full-time roles in a team of any size | 400 to 600 words |
| 2. Short | Small businesses, quick hires, simple roles | 150 to 250 words |
| 3. Remote | Fully remote or hybrid roles | 450 to 650 words |
| 4. Entry-level | Graduates, interns and career changers | 300 to 450 words |
Template 1: Standard job description
Use this when you want to cover everything and the role is a normal full-time position.
[Job title]
[Team] | [Location] | [Full-time or part-time] | Reports to [manager's title]Summary
[Two or three sentences: why the role exists and what success looks like after the first year.]Responsibilities
- [Verb + outcome]
- [Verb + outcome]
- [Verb + outcome]
- [Verb + outcome]
- [Verb + outcome]
Requirements
- [Skill or experience you need on day one]
- [Skill or experience you need on day one]
- [Skill or experience you need on day one]
Nice to have
- [Skill that helps but can be learned]
- [Skill that helps but can be learned]
Pay and benefits
[Minimum] to [maximum] per [year or hour]. [Benefits: leave, health cover, equipment, learning budget.]How to apply
[Where to apply, what to include, and what happens next.]
Template 2: Short job description
A small business hiring its first receptionist or driver does not need a page of headings. Candidates for simple roles read a posting in under a minute, so say the important things quickly. Keep the pay line, because it matters more here than anywhere.
[Job title] at [Company name], [Location]
We are looking for a [job title] to [main purpose in one sentence]. You will [two or three main duties in one sentence]. Hours are [days and times], and the job is [on-site, remote or hybrid].
You should have: [two or three must-haves, in one sentence].
We offer: [pay range], [one or two main benefits].
To apply, [how to apply and by when].
Template 3: Remote job description
Remote roles raise questions that an office role never has to answer: which time zone, which hours, and how work gets seen. Candidates look for those answers first, so put them near the top.
[Job title] (Remote)
[Team] | Remote within [country, region or time zones] | [Full-time or part-time]Summary
[Why the role exists and what success looks like.]How we work
- Core overlap hours: [for example 10:00 to 14:00 Central European Time]
- Communication: [tools, and whether the team works mostly in writing or on calls]
- Meetings: [how many a week, and which are required]
- Equipment: [whether you provide a laptop or a home-office allowance]
Responsibilities
- [Verb + outcome]
- [Verb + outcome]
- [Verb + outcome]
- [Verb + outcome]
Requirements
- [Skill or experience]
- [Skill or experience]
- Experience working independently and communicating clearly in writing
Pay and benefits
[Range and currency.] [Say whether pay depends on the candidate's location.] [Benefits and any travel or in-person meetups.]
State clearly whether pay is the same for everyone or adjusted by location. Candidates in different countries will assume different things, and being vague about it is a common reason for dropped applications late in the process.
Template 4: Entry-level and internship job description
Early-career candidates often apply to roles they only partly match, and they are put off by a list of requirements that reads like a senior hire. Say what you will teach, not only what they must already know.
[Job title], [Junior, Associate or Intern]
[Team] | [Location] | [Duration if fixed-term] | [Paid, and how much]About the role
[What the person will work on, and who will guide them.]What you will do
- [Task, with who supports them]
- [Task]
- [Task]
What we are looking for
- [Education, course or equivalent practical experience]
- [Two or three skills or interests]
- Willingness to learn and to ask questions
What you will learn
- [Skill or tool they will gain]
- [Skill or tool they will gain]
Pay and support
[Pay or stipend.] [Mentoring, training, and whether the role can lead to a permanent job.]
How to fill in any template well
- Write the summary last. Once the responsibilities are on the page it is much easier to say what the job is for.
- Start every responsibility with a verb and an outcome. "Resolve customer questions within one business day" beats "Customer inquiries".
- Cut the requirements in half. Then put back only what a person genuinely cannot do the job without.
- Use numbers where you honestly can. "Manage a team of four" or "handle about 30 tickets a day" tells a candidate far more than "manage a team".
- Always include pay. It is a legal requirement in a growing number of places, and our guide to pay transparency in job descriptions explains what to put and when.
- Read it as a stranger would. If a word is internal jargon or an unexplained acronym, replace it.
Frequently asked questions
Can I use these templates for free?
Yes. Copy them, change them, and use them in your own postings and internal documents.
Should I use the same template for every role?
Use the same structure, so your postings feel consistent, but change the content for each role. The sections that matter most differ between a warehouse role and a software role.
What should I do after I fill in the template?
Check it against a list of best practices before posting. Our guide to writing a job description includes a checklist, and these examples for 10 common roles show finished versions.





Join the conversation
Discussion0
Join the conversation. Sign in to leave a response or reply to comments.