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.
The structural foundation CHROs present to the board and CFOs use to defend headcount decisions.

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.

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/year