Best Practices for Job Post Templates

Datapeople Templates enable you to define and store default language and provide a structure for your job descriptions. You can use one default template for your entire organization or customize templates for special teams and functions. Only Admin users can create and edit templates.

Why Templates

Use templates to standardize the structure and content of your job posts.
Ensure compliance by baking in essential content like pay transparency language.
Avoid the complexities of setting up multiple ATS templates.
Increase efficiency for hiring teams--get to a higher score faster.
Create consistency across writers and geographies.
Streamline your recruiting process with scalable high-volume templates.
Lock down important company content that shouldn’t be changed.

Template Structure

Create your most general template first, then duplicate it to create additional templates
Common ways to structure templates:
- Locations
- Departments
- Business units
- High-volume roles

Creating a New Template

On the "Settings" menu, click "Templates."
Click "New Template".
Name your Template, and click "Create Template."

In the template library page, the default setting is to show active templates. However this can be toggled off. By default, templates are listed in alphabetical order and can be sorted, searched or filtered.

The Apply Template modal sorts templates in alphabetical order. Choosing appropriate template names can be helpful to ensure users find what they’re looking for.

Add Editable Content

Create your most general template first, then duplicate it and make any changes to create additional templates.
Templates are typically created for specific locations, departments, or business units, high volume roles, or anytime your boilerplate content needs to change.
Your template is not live until you toggle the publish on, which means you can make changes and updates without someone using your work in progress.
This also means that to update a template, you need to unpublish it.

Add Content & Placeholder Text

Use placeholders by ((double bracketing content)) to help users add the correct content.
Ensure you have positions for all critical content: Intro, About the Job, Qualifications, Benefits, Diversity/EEO, and About the Company.
Once your content and locks are final, you and your team can use this template on any new Datapeople Draft.
You may create as many templates as you need - for different job types, teams, or geographies with unique content.

NOTE: All users in your account have access to any published template you create.

Add Locked Content

Content that you don’t want to be edited can be placed in the purple shaded areas at the top or bottom of each section.

Create a Check-list

Use the commenting feature to create a check-list that is inherited on any job where a template is applied.

Job Post Template Example

Write two or three sentences that describe the role (example below). Include information about the team the candidate will work on and to whom they will report.

Join ((insert company)) as a ((insert job title)) where you will ((insert a few key responsibilities)). You will also ((insert key projects)). As part of the ((insert team)), you will report to ((insert title)) and work with ((insert groups that you will be working with)) ((insert location remote/hybrid/onsite with city)).

You will:

((Add 4-5 key responsibilities of the job))

((List responsibilities in order of importance))

((This list does not need to be exhaustive, focus on the primary or essential responsibilities))

((Anticipated, day-to-day technical duties for RFE's - immigration purposes))

You have:

((List required professional experience))

((Add 1-2 specific technical requirements for the job))

((Avoid soft skills like "excellent written and verbal communication skills"))

((Avoid requirements that can be learned in less than a week, like "Ability to use Gmail"))

((About the Company, the Benefits and Diversity statement should always be included as well.))

Some job search engines won’t process your job with an external URL in it, so work to include only the key content in your job post and then share additional content during the interview process.

It’s important for candidates to include information about life and culture at the company, explicitly reporting structure, benefits, and diversity or EEO statement to see the “what’s in it for me”? Those items should be included in the job post and not linked.

Template Best Practices

Job Post Length

About the Job: 50%
About Perks: 15%
Diversity and Accommodation: 15%
About the Company: 20%

Template Tips

Optimize as much content as possible, especially in the locked sections that the editor can’t access themselves.
The closer to the score of 100 the template is, the easier the process of optimizing to 85 will be for the editor.
Aim to keep your boilerplate language to 200-250 words; anything more than that doesn’t leave much room for the editor to add important job-specific content like requirements and qualifications.

Template Management

Templates are alphabetical and can be searched

ATS Templates - For customers with a Lever or Greenhouse integration

Much like Datapeople Drafts, your Templates in Datapeople are not ATS-connected. So for Templates specifically (because they end up creating Datapeople Drafts), it is important that any templated text that your ATS will be adding be added to the intro/conclusion fields in the Template and locked.

Greenhouse

Available to add/optimize content: Description.
The Intro and Conclusion Template content is located in Greenhouse and can’t be edited/optimized on a job post.

Lever

Available to add/optimize content: Description, Lists (but only in a header/list format), and Closing.
The Intro and Closing Template content is located in Lever and can’t be edited/optimized on a job post.
The spacing between blocks might not be accurate, so if you have any issues, let support@datapeople.io know so we can help resolve them.