What's the Difference between Templates and Flagship Jobs?

Datapeople offers two powerful tools to help teams write high-quality, consistent job posts: Templates and Flagship Jobs. While they may seem similar, they serve very different purposes. This guide will help you understand when to use each - and how to use them together.

At a Glance

What Are Templates?

Templates are reusable blocks of content designed to ensure consistency across all your job posts. They're ideal for company-specific information that doesn’t change from role to role.

Common Template use cases:

• About the Company
• Benefits and Perks
• Legal Statements like Equal Opportunity and Diversity Statements

Templates are applied to job drafts to ensure required information is always included.

Templates: Insert this block of approved language into my job post.

Not using Templates yet?

If you’re including benefits, perks, or other company-wide content directly in your Flagship Jobs, consider turning that content into a Template instead.

This makes it easier to update information in one place especially when policies or perks change. It also reduces editing work and ensures every post stays on-brand.

What Are Flagship Jobs?

Flagship Jobs are best-in-class job posts selected by Datapeople Admins as high-quality examples. They include full job-specific content, such as responsibilities, requirements, and descriptions - everything you'd expect in a real job post.

Common Flagship Job use cases:

• High-volume or evergreen roles (e.g., Software Engineer, Sales Associate)
• Job profile-based workflows
• TA-approved examples for quality and structure
• Launching a new function or team

Unlike Templates, Flagship Jobs are duplicated to start a new draft - they act like a model or blueprint for the full post.

Flagship Jobs: Start with this job as your reference or starting point.

How to Use Them Together

For the best results, combine the two:

1. Start with a Flagship Job:

   Use it to get the structure, tone, and job-specific content right.

2. Apply Templates:

   Add consistent, company-wide content like benefits or D&I statements.

This workflow helps you scale job creation without sacrificing quality. and ensures every post reflects both team-specific and company-wide standards.

Common Pitfalls to Avoid

• Don’t put benefits or company info in Flagship Jobs if you already use Templates: This creates duplication and inconsistencies and requires significant maintenance when you update company language.
• If you don’t use Templates, you can include perks/benefits in Flagship Jobs, just keep them aligned.
• Don’t use Templates for job responsibilities: They vary too much by role.
• Don’t over-flag jobs: Keep Flagship Jobs curated and high quality.
• Don’t confuse duplication with apply: Flagship Jobs are copied into drafts, while Templates are applied to existing ones.