Job hierarchy levels
The hierarchy level is a classification that indicates the seniority or organizational position of a role — for example, Individual Contributor, Manager, Director, or Executive. Recruiters assign a hierarchy level when creating or editing a job, and it is used to filter and segment jobs in reports and on the job board.
How hierarchy level is used
Hierarchy level appears as a dropdown field on the job form. Once set, it allows hiring managers and administrators to filter the job list by seniority — for instance, to see all open director-level roles at once, or to produce a headcount report by management tier.
On the public job board or career page, hierarchy level can be exposed as a filter to help candidates self-sort into roles that match their career stage.
Adding a level
- Go to Configuration → ATS settings → Job and open the Hierarchy levels tab.
- Click Add a level at the top of the list: the side panel opens.
- Enter a label (for example, “Individual Contributor”, “Team Lead”, “Senior Manager”).
- Click Save.
Reordering
Drag the ⠿ handle to reorder the list (with the keyboard: Tab to the handle, Space, arrow keys, Space); the order is saved as soon as you release it. Order from lowest to highest seniority so the dropdown reads naturally from the recruiter’s perspective.
Editing and deactivating
Click a row (or ⋯ → Edit): the side panel opens; Save applies, Cancel discards your changes. Only the row’s Active switch and the ⠿ handle act immediately. Deactivate levels that are no longer used — they disappear from the dropdown without removing them from jobs that already have the value set.
There is no delete action for hierarchy levels — a level can only be deactivated or reordered.
Tips
- Use no more than five to seven levels. Granularity beyond that (for example, “Senior Associate I” versus “Senior Associate II”) is rarely useful in ATS reporting and adds cognitive overhead to recruiters.
- Align with your job leveling framework. If your HR team uses a graded system (IC1–IC6, M1–M4), adopt the same labels so data can be joined across systems.
- Include an “Unclassified” option as the first item if many roles are hard to categorize — it prevents a blank default and makes it easy to audit which jobs still need classification.