Job Architecture

The parts of a job architecture

Most frameworks have four layers.

• Function: the broad area of work, such as Operations, Finance, Human Resources or Technology.
• Job family: a group of jobs that use similar skills, such as Customer Support, Workforce Management or Talent Acquisition inside Operations and HR.
• Career track: usually individual contributor, manager and sometimes executive. Separate tracks let a strong specialist progress without having to manage people.
• Level: a defined step of scope and impact, for example P1 to P6 for professionals or M1 to M4 for managers. Each level has a written definition covering complexity, autonomy, impact and leadership.

The intersection of a job family and a level is a job, such as Talent Acquisition, P3. Specific titles (Senior Recruiter) and positions (the seat Maria fills in Phoenix) hang off that job.

A worked example

A regional healthcare system with 9,000 employees has 2,300 unique job titles, many created during hiring rushes. Three people doing identical scheduling work are titled Scheduler, Patient Access Coordinator and Scheduling Specialist II, with pay differing by $7,000.

The HR team builds an architecture with 9 functions, 48 job families and a common set of levels. The scheduling work becomes one job, Patient Access, level S2, with a single title and one pay range. After mapping, the title count falls to about 600. The pay range fix costs money for the underpaid group, but it removes an equal pay risk and lets recruiters reuse one job description instead of three.

Why it matters for hiring and pay

Recruiters feel a weak job architecture every day. Requisitions arrive with invented titles, no agreed level and a salary range nobody can explain. Offers get negotiated case by case, and a candidate in one region is offered more than an incumbent doing the same work elsewhere.

A clean architecture fixes the upstream inputs:

• Each requisition maps to a job and level, which links to a salary structure and a range you can post where pay transparency laws require it.
• Interview scorecards can be built per job family and level, rather than per hiring manager.
• Workforce plans count headcount by job and level, which makes cost modeling realistic.
• Employees can see career pathing options across families, not just the next title in their team.

How to build one

1. Collect every current title, its incumbents, pay and reporting line from the HRIS.
2. Define functions and job families with input from business leaders. Aim for families of jobs that share most skills.
3. Write level definitions once, for the whole company, using four or five factors such as knowledge, problem solving, autonomy, scope of impact and leadership.
4. Map each role to a family and level. Use job evaluation or market matching to settle disputes, and interview managers about what the work really involves.
5. Attach pay ranges, standard titles and job descriptions.
6. Set governance: who approves new jobs, how often the framework is reviewed, and how exceptions are handled.

For a company of a few thousand people, expect four to nine months. Most of that time goes to mapping and manager conversations, not design.

Common mistakes

• Too many levels. Eleven professional levels creates arguments about whether someone is a 6 or a 7. Most organizations manage with five or six per track.
• Levels defined by tenure. Level should describe the work, not how long someone has done it.
• Titles that drift. Without a gatekeeper, managers create new titles to win candidates, and the architecture decays within two years.
• Building it in HR alone. If business leaders do not recognize the families and levels, they will not use them in hiring or promotion decisions.