Job Titles — Proposed Guide
Planned API — Reference OnlyJob Titles: Job titles are descriptive employment attributes that may influence policy design. They should not become security roles merely because two…
Overview
Job titles are descriptive employment attributes that may influence policy design. They should not become security roles merely because two systems use similar labels.
Key concepts
Separate the source title, normalized display title and any policy classification. Use effective dates when title changes affect eligibility.
Implementation considerations
Do not infer authority from titles such as director or controller. Approval permissions need explicit assignments.
Illustrative data model
This local fixture shows a possible representation for the concepts above. It is not an endpoint response, production configuration or a claim that the described capability is implemented.
{
"reference_only": true,
"topic": "Job Titles",
"user_id": "usr_example_123",
"job_title": "job title example",
"effective_on": "2026-01-15"
}Design review checklist
- Document which organization owns the job titles representation and which actor may view or change it.
- Test the boundaries of user id, job title, effective on using synthetic values, including missing or inconsistent references.
- Before future implementation, obtain an approved contract and review failure behavior. This documentation does not authorize production activation.
Proposed data types
| Name | Type | Description |
|---|---|---|
| user_id | string | Stable fictional user reference; not a secret and not evidence that a resource exists. |
| job_title | string | Illustrative job title value; interpret it only within the proposed topic-specific model described above. |
| effective_on | string (date) | Synthetic calendar date in YYYY-MM-DD form; period inclusivity must be defined by the future contract. |