[Legacy] Company Job Architecture
What is Company Job Architecture? (aka “CJA”)
Company Job Architecture is a platform-wide data model that stores information about the jobs within a company.
Why is Job Architecture important?
The Job
The “Job” is a core HR concept that describes a single role within the organization. It is critical to many different aspects of compensation, but it is especially relevant in Market Data and Market Pricing.
Job Architecture
A company’s “Job Architecture” describes how all the jobs within a company are organized. It is often also referred to as the “Career Ladder” - though these two concepts are not always 1:1. An easy way to think about Job Architecture is like an org chart - but instead of showing all the individuals in an organization and their reporting lines to one another it shows the jobs in an organization and how they are related to one another.
Job Architecture is a critical component of how a company compensates it’s employees because it allows them to provide consistency and structure to compensation decisions. Once the Job Architecture is created, employees are “leveled” into the correct job based on their responsibilities and level of proficiency.
Core Concepts & Definitions:
| Concept | Definition |
|---|---|
| Job | A single role in an organization. Commonly described by a combination of Family + Level (e.g. SWE P1). In Pave, this is described as a unique combination of Function + Ladder + Ladder Rank. |
| Job Architecture | A list of all the jobs in an organization. In Pave, this is expressed as the complete list of all unique combos of Function + Ladder + Ladder Rank within the organization. |
| Function | A higher order organizational concept within job architecture. In Pave it is a collection of Ladders that are related - often because they have similar responsibilities. |
| Ladder | An organizational concept within job architecture. It is a collection of jobs that have the same responsibilities & career track, but different levels of proficiency. |
| Ladder Rank (aka Rank) | An organizational concept within job architecture that describes the hierarchy of jobs within a ladder. The hierarchy is often a descriptor for the level of proficiency. |
| Family | An organizational concept within job architecture that describes the responsibilities for a job. E.g. “Software Engineering” |
| Track | An organizational concept within job architecture that describes the career track for a given job or ladder. E.g. “IC”, “P”, “Manager”, or “Exec” |
| Level | A descriptor for a job’s level within the organization. Often a combination of Track + Rank. E.g. “IC3”, “P2”, “M4”, or “E7” |
| Title | The title for an individual. Sometimes 1:1 with the individual’s job, but very often not 1:1. |
| HRIS Matchers | The method for how Pave matches employees in the HRIS to a job in Pave. |
What is required to set up a company’s job architecture in Pave?
Importing Job Architecture:
The first step that’s required to set up a company’s job architecture is to simply import the complete list of unique combinations of Function + Ladder + Ladder Rank (aka the Jobs) within the organization.
Often, this will require some transposing of the company’s internal way of describing jobs into Pave’s terminology:
Sometimes this will be easy, example being when a company already has jobs described at Family + Level:
| Company Terminology | Function | Ladder | Ladder Rank |
|---|---|---|---|
| Software Engineering, P1 | Engineering | Software Engineering - IC | 1 |
| Account Executive, P4 | Sales | Account Executive - IC | 4 |
Sometimes this will be less clear:
| Company Terminology | Function | Ladder | Ladder Rank | Notes |
|---|---|---|---|---|
| Product Manager, M3 | Product & Design | Product Management - M | 1 (or 2? or 3?) | M3 sometimes is rank 1, sometimes rank 2 or 3. |
| Software Engineer | Engineering | Software Engineering - IC | ??? | This title doesn’t tell us anything about rank |
| VP, Sales | Sales | ??? - Exec | 1 | We don’t know what family to use just based on this title. We can guess the rank, but might not be right. |
Sometimes companies will not have a complete list of all the jobs in their organization because they have only created jobs based on the employees they have.
Please check out this article for details on setting up your company job architecture in Pave.