73% of Orgs Have Inconsistent Titles. Build One Structure Everyone Uses
Job Architecture defines families, grades, codes, and levels, giving every role a governed structural address before anything else happens. This is the foundation every other module builds on.
.svg)
The structural foundation CHROs present to the board and CFOs use to defend headcount decisions.
73%
of HR leaders report inconsistent job titles and levels across departments or regions
42%
of compensation decisions are influenced by informal leveling rather than a governed framework
2.8×
higher internal pay equity risk when job families and grades are not formally defined
Six Components. One Governed Taxonomy.
The setup layer that sits before everything else authoring, evaluation, benchmarking, and planning all draw from it. Unlike point solutions that bolt on job architecture as an afterthought, CompBldr is built architecture-first. Every downstream decision inherits the same foundation.
.svg)
Job Families
Broad capability domains: Engineering, Product, HR, Finance. The top-level taxonomy that organizes all roles.
Sub-Families
Precision within each family: DevOps, Software Engineering, HRBP, Talent Acquisition. Position count tracked per branch.
.svg)
Job Groups
Operational clusters by work domain: API Engineering, Backend Dev. A practical filter layer alongside the family taxonomy.
Job Grades
Score-based level ranges from JESAP evaluation. Roles placed by evaluation score, not manager judgment. Up to 12 levels.
Job Codes
Structured identifiers (ENG-FSD-G1-001) encoding family, sub-family, grade, and sequence. Uniquely referenceable everywhere.
.svg)
Grade Title Matrix
The synthesis view mapping every title across families, sub-families, and grades. Gaps surface immediately, not during an audit.
Every Role Gets a Governed Address. Before Anything Else Happens.
Job Architecture is the structural layer every other module depends on. Here's how it works inside CompBldr.
Define the Taxonomy Before the First Role Is Authored.
Job Family is the highest-level classification in the architecture model. Each family represents a broad capability domain. Sub-families add precision within each domain and track how many positions are already mapped to each branch.
.svg){kind=icon}
Cluster Titles by Work Domain. Give Every Role a Unique Code.
Job Groups cluster titles by practical work domain alongside the family taxonomy API Engineering, Backend Development, HR Administration. Job Codes give every role a structured, unique identifier that travels across every CompBldr module without manual cross-referencing.
Build a Score-Based Grade Structure. Roles Assign Themselves.
Once score boundaries are configured, every evaluated role falls into a grade automatically. No subjective placement, no undocumented exceptions, no structural drift.
See Every Role, Every Grade, Every Family. In One View.
The Grade Title Matrix is the synthesis view that maps every title across families, sub-families, and grade levels simultaneously. Three display modes, Detailed, Compact, and Grid, give HR, Finance, and leadership the right level of detail for their use case. Gaps surface immediately, not during an audit.
.svg){kind=small}
Frequently Asked Questions
Job architecture software is a platform that defines and governs the structural taxonomy behind an organization's roles: job families, sub-families, grades, groups, and codes. In CompBldr, Job Architecture is the setup layer that ensures every job description, evaluation, and pay decision starts from a governed foundation.
A job family is the top-level classification grouping roles by broad capability domain, Engineering, Product Management, and Human Resources. It matters because every downstream decision, from job description authoring to compensation benchmarking, depends on roles being organized into a consistent, searchable taxonomy rather than created in isolation.
A job grade is a level band with a minimum and maximum JESAP evaluation score range. Roles are placed into grades based on their JESAP score, not manager judgment. CompBldr supports up to 12 grades with configurable score boundaries. Every grade configuration is versioned and timestamped.
The Grade Title Matrix is the synthesis view of Job Architecture. It maps every job title across families, sub-families, and grade levels in one grid. Administrators use it to see the full role taxonomy, identify structural gaps, and confirm that every title has a governed family, grade, and code assignment before authoring begins.
A job code is a unique structured identifier for each role: family prefix, sub-family code, grade indicator, and sequence number, for example, ENG-FSD-G1-001. Job codes make titles uniquely identifiable and reusable across JobBldr, Job Evaluation, and Compensation Planning without manual cross-referencing or duplicate title management.
Job families classify roles by broad capability domain and form the foundation of the taxonomy. Job groups cluster titles by practical operational work domain, API Engineering and Backend Development—and sit alongside the family structure as an additional filter layer for searching, reporting, and organizing related roles.
JobBldr draws family, sub-family, grade, and code values directly from Job Architecture when a user authors a job description. Job Evaluation references grade ranges to validate JESAP scores. Compensation Planning uses family and grade data to apply merit matrix guidelines and pay range assignments. All modules read from the same governed architecture.
Yes. Job grades can be edited and the framework can be versioned. Each version is saved with the editor's name, timestamp, and a review step before publishing. Titles already assigned to a grade are not automatically regraded. Changes to grade boundaries are reviewed and applied deliberately, not automatically pushed downstream.
CompBldr Job Architecture supports an unlimited number of job families and sub-families. The grading framework supports up to 12 grade levels with configurable score ranges between each. The Grade Title Matrix scales to show all families and grades in a single view with search, filter, and jump-to-family navigation for large taxonomies.
Build the Taxonomy Once. Govern Every Role That Follows.
When the foundation is right, everything built on top of it evaluations, bands, merit cycles is defensible by default.
No credit card · 15-minute walkthrough · Most teams invest $25K–$120K/yr
.svg)
.svg)
.svg)
