Skip to content

HR — Job Architecture & Role Catalog

A job architecture catalog keeps role titles and grades consistent across countries for HR, recruiting, and AI assistants.

Why this is needed

  • Job titles drift across regions.
  • ATS and HRIS need a shared role definition.
  • AI recruiting needs approved role text.

Proposed entities in EntiHub

Governance settings

Setting Recommended value Why
approvalRequired true Role/grade changes affect compensation bands.
historyEnabled true History of role definitions.
allowSameAuthorApproval false Maker/checker separation for sensitive changes.
deletedRetentionDays 90 (or higher) Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: job_role
displayName: Job role
domain: HR
description: Job role
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: role_code
uniqueConstraints:
  - name: uq_job_role_role_code
    columns: [role_code]
columns:
  - name: role_code
    dataType: string
    nullable: false
    maxLength: 32
  - name: title
    dataType: string
    nullable: false
    maxLength: 128
  - name: job_family
    dataType: string
    nullable: false
    maxLength: 64
  - name: grade
    dataType: string
    nullable: false
    maxLength: 16
  - name: status
    dataType: string
    nullable: false
    maxLength: 16

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

role_code title job_family grade status
FIN-ANALYST-II Finance Analyst II Finance G8 active
ENG-SE-III Software Engineer III Engineering G10 active

Benefits for the company

  • Consistent titles across countries.
  • Clear input to recruiting and leveling.
  • Governed changes to architecture.