Job Architecture Software That Governs Every Role. Connect Structure to Every Pay Decision.
CompBldr job architecture software gives every role a governed structural address across job families, sub-families, grades, levels, and codes—then connects that structure to job evaluation, market benchmarking, salary ranges, and compensation planning.
.svg)
The structural foundation CHROs present to the board and CFOs use to defend headcount decisions.
governed taxonomy for job families, sub-families, groups, grades, levels, and codes
configurable grade levels supported in the score-based architecture
framework changes with version history, editor records, timestamps, and review steps
Six Components. One Governed Taxonomy.
The setup layer sits before everything else—authoring, evaluation, benchmarking, and planning all draw from it. Unlike point solutions that add job architecture later, CompBldr is built architecture-first so downstream workflows can use the same structural 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 counts are 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 such as ENG-FSD-G1-001 encode family, sub-family, grade, and sequence so each role can be referenced consistently across connected workflows.
.svg)
Grade Title Matrix
The synthesis view maps titles across families, sub-families, and grades so teams can review gaps and inconsistencies in one place.
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, such as API Engineering, Backend Development, and 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 With Reviewable Assignments
Once score boundaries are configured, evaluated roles can be mapped consistently to grade ranges. Changes remain reviewable and versioned rather than silently overriding prior assignments.
See Every Role, Every Grade, Every Family. In One View.
The Grade Title Matrix maps titles across families, sub-families, and grade levels in one view. Detailed, Compact, and Grid modes help HR, Finance, and leadership review the structure at the level of detail they need.
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 a top-level classification that groups roles by broad capability domain, such as Engineering, Product Management, or Human Resources. It matters because downstream decisions—from job description authoring to compensation benchmarking—depend 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 work domain, such as API Engineering or Backend Development, and sit alongside the family structure as an additional 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 Your Job Architecture Once. Govern Every Role That Follows
When the foundation is right, everything built on top of it—job evaluation, market benchmarking, salary bands, and compensation planning—becomes easier to govern and defend.
15-minute walkthrough · See the job architecture workflow using real product screens
.svg)
.svg)
.svg)
