Job Architecture 101

Table of Contents

• Job Architecture
  • What are each of the job architecture fields?
  • Example bands with job architecture
• HRIS Matchers
  • What is the purpose of HRIS matchers?
  • What are the supported HRIS matchers?
• Common Errors
  • Duplicate Bands error
  • Jobs and HRIS job matcher errors
  • Payzone and HRIS location matcher errors

Job Architecture

What are each of the job architecture fields?

The job architecture fields that determine a unique job are: Function, Ladder, Ladder Rank, and Payzone → payzone is only included if there’s location based pay

• Function

  • This refers to a group of people that all perform the same “function” → sometimes this maps to family
  • Examples of functions:
    • Engineering
    • Product Design
    • Sales
    • Customer Success
  • Example that is not a function:
    • R&D → this is a department that includes multiple groups that perform different functions

• Ladder

  • This is the progression or track that a job belongs in within a given function. Think about the specific role of this job
  • The ladder will also likely denote whether the job is for an IC, Manager, Exec, etc.
  • Examples of ladders within the function Customer Success:
    • CSM
    • CSM Manager
    • Customer Success Operations
    • Customer Success Executive

• Ladder Rank

  • This is simply the leveling/hierarchy of each role in the ladder
  • The lower the number, the lower the level
  • 1 is the lowest level, but there is no requirement to start from 1

• Payzone

  • This is a group of locations that are all paid at the same rate
  • In some cases this can be thought of the same as metro
  • Examples of payzones:
    • Tier 1
    • Bay Area

Job Architecture fields DO NOT have to be the same as HRIS fields OR exist in the HRIS. This are strings that only live in Pave, so it’s encouraged to make these as readable as possible to describe the exact job.

Example bands with job architecture

HRIS Matchers

What is the purpose of HRIS matchers?

• The only purpose of HRIS fields are to match employees to bands
• These fields do not define the job of a band, that’s what job architecture is for
• HRIS fields do not have to be the same as the job arch fields → they are only fields that exist in the HRIS on employees
• HRIS fields will not be exposed on bands for non-admins

What are the supported HRIS matchers?

• Job Matchers
  • Job Code
  • Family - Level
  • Title - Level
  • Title
• Location Matchers
  • Metro

Common Errors

Note: Sort on the uniqueMatcherKey column to group bands that need to be resolved together. For example, duplicate bands will have the same uniqueMatcherKey

Order of Operations:

1. Solve any missing field/extra field errors
   1. Need to first ensure that you are uploading bands with the correct columns
2. Solve duplicate bands errors
   1. Duplicate bands errors will cause other errors
   2. It’s often the case that solving duplicate band errors will also get rid of all the additional errors related to job architecture and matchers
3. Solve all other errors

Duplicate Bands error

**Duplicate Bands Detected**

When does this happen?

• This error occurs when there are duplicate (non-unique) job architecture combinations
• The combination of Function - Ladder - Ladder Rank or Function - Ladder - Ladder Rank - Payzone (if location-based pay) must be unique for every band
• These fields are how we define a unique job and every unique job should only have one band

How to resolve?

• To resolve, one of the bands needs to be removed or updated
  • If the bands are exactly the same → delete one of them
  • If one of the bands has different pay values → confirm which band has the correct values and delete the other one

NOTE: Always resolve this error before any other job architecture errors. This error may be the cause behind the other job arch-related errors below.

Jobs and HRIS job matcher errors

You will see two different types of errors for this:

• Jobs without Unique HRIS Job Matchers
• HRIS job matcher combos matching to multiple jobs

Rules:

• Non-payzone job architecture fields (Function - Ladder - Ladder Rank) must always match to the same HRIS job matcher(s)
• HRIS job matcher(s) must always match to the same “role”

Causes:

• When you have the same HRIS job matcher(s) on multiple bands with different combinations of Function - Ladder - Ladder Rank
• When you have multiple bands with the same combination of Function - Ladder - Ladder Rank on multiple bands but not the same HRIS job matcher(s) on each of these bands

Examples:

• Jobs without Unique HRIS Job Matchers

There’s an error here because these bands have the same Function - Ladder - Ladder Rank but different HRIS Job Codes

• HRIS job matcher combos matching to multiple jobs

There’s an error here because these bands have the same HRIS Job Codes, but different combinations of Function - Ladder - Ladder Rank

*This chart shows which fields need to be one to one with each other

Payzone and HRIS location matcher errors

You will see two different types of errors for this:

• Payzone matching to multiple hris location matcher combos
• HRIS location matcher combos matching to multiple payzones

Rules:

• Payzone must always match to the same HRIS Metro
• HRIS Metro must always match to the same Payzone

Causes:

• When you have the same HRIS Metro on multiple bands with differentPayzones
• When you have the same Payzone on multiple bands with differentHRIS Metros

Examples:

• Payzone matching to multiple hris location matcher combos

There’s an error here because these bands have the same Payzone but different HRIS Metros

• Payzone matching to multiple hris location matcher combos

There’s an error here because these bands have the same HRIS Metros but different Payzone

*This chart shows which fields need to be one to one with each other