Job Profiles are reusable hiring setups designed for roles your team hires for repeatedly. Instead of rebuilding the same project structure, fields, and hiring information every time, you can create a Job Profile once and reuse it whenever needed. Note that only admins can create Job Profiles.

One of the biggest advantages of Job Profiles is that the same fields and information structure can be reused across different parts of Teamdash, such as Job Profiles, Requisitions, and Projects. This allows information to move smoothly through the hiring workflow without needing to recreate the same fields multiple times.

Job Profiles also work together with Project Templates. While a Project Template defines the project structure and workflow (such as automations and stages), a Job Profile stores the reusable hiring information and setup data specific to the role itself.

Navigate to Settings → Job Profiles and click Create Profile.

When creating a Job Profile, you can build a structured setup by adding sections, linking or creating new custom fields, and selecting which information should later appear in the project creation flow. The interface is designed to keep the initial view clean and easy to navigate, while still allowing detailed customization when needed.

Job Profiles are built using sections and draggable custom fields, allowing you to structure information in a way that makes sense for different hiring workflows and teams.

For example, you might create sections for:

Sections and fields can be reordered using drag-and-drop, making it easy to adjust the structure over time as your hiring needs evolve.

When adding fields to a Job Profile, you can either reuse existing custom fields or create completely new ones.

Linking a field means reusing a custom field that is already being used elsewhere in Teamdash, such as in Requisitions or Projects, and making it available for Job Profiles as well. This helps keep information consistent and avoids creating duplicate fields for the same purpose.

For example, if you already use a “Location” field in Requisitions, you can simply link that same field to Job Profiles instead of creating a new version of it.

One of the biggest advantages of linked fields is that the same fields can be reused throughout the hiring process, from Job Profiles to Requisitions and Projects. This ensures information moves smoothly between different workflows without needing to recreate the same fields multiple times.

You can create entirely new custom fields directly inside the Job Profile view without losing progress, making setup much faster and more convenient.

Project Description source fields will be automatically added to the Project Description under Edit Project view.

When creating a Job Profile, you can define which fields should automatically populate the Project Description when creating a new project.

Multiple fields can now be selected and arranged in a custom order. The selected fields will appear in the same sequence in the generated project description.

This is especially useful for creating consistent job descriptions and reducing repetitive copy-paste work.

As the project description gives contextual information for Teamdash AI-powered tools, it also helps to improve AI-generated summaries and AI CV screening results.

Some field types are intentionally excluded from description sources, including user, date, datetime, file/files, and multilingual text fields.

Job Profiles can be cloned either with or without field data, allowing teams to quickly create variations of existing profiles without rebuilding everything from scratch.

Archived fields are automatically excluded during cloning, helping keep new profiles clean and up to date. This is especially useful when hiring for similar positions that share most of the same requirements but need slight adjustments.

When creating a new project, you can now select a Job Profile as part of the setup flow or start with an empty project.

Once selected, Teamdash can:

The project detail view also displays the linked Job Profile and clearly identifies imported values, making the relationship between profiles and projects much more transparent.

Job Profiles work best when used for recurring hiring needs where consistency matters. Creating reusable structures for common roles helps reduce manual work and ensures projects always contain the right information from the start.

We recommend:

A well-structured Job Profile can significantly speed up project creation and improve consistency across hiring teams.

A Project Template defines the project structure and workflow, like automations. While a Job Profile stores reusable hiring information, field values, and project setup data for a specific role or hiring scenario.

Yes. New custom fields can be created directly inside the Job Profile setup flow without losing progress.

Yes. Regular users can view and select Job Profiles during project creation, but can't create them.

Archived fields are clearly labeled and automatically excluded when cloning Job Profiles.

Yes. Simply select the fields in the order you want them to appear. The generated Project Description will follow the same sequence.