Many teams confuse Company Job Titles, Business Titles, and the Kamsa Job Match. They work together, but each serves a different purpose.
This guide explains what each one means and how they align.
Company Job Title
The Company Job Title is the title your organization uses publicly. It’s what the employee believes their title is and what typically appears on the census file you upload to Kamsa.
Examples:
Back End Engineer
Front End Engineer
Senior Front End Engineer
Account Executive, UK
Company Job Titles for similar roles often vary, even when the underlying job is the same.
Business Title
The Business Title is the internal, standardized version of the job. It creates consistency across similar roles so you can align levels, compare employees, and apply one salary range.
Business Titles help when:
Two Company Job Titles differ but represent the same role
Titles include regions or internal naming quirks
Company titles are inflated or not level-aligned
Examples:
Senior Front End Engineer + Senior Back End Engineer → Senior Software Engineer
Account Executive, LATAM + Account Executive, EMEA → Account Executive
Business Titles are auto-populated from the Company Job Title during upload, but can be edited anytime in Employee Data, Employee Profile, or Job List.
In many cases, the Business Title may stay exactly the same as the Company Job Title.
Kamsa Job Match
The Kamsa Job Match is the exact Kamsa job and level that the role maps to. It ties your Business Title to Kamsa’s market data so the correct salary range can be applied.
Example:
Back End Engineer → Business Title: Software Engineer → Kamsa Job Match: Software Engineer (IC3)
Even when Company Job Titles differ, they can map to the same Kamsa Job Match and therefore share the same market range.
How they work together
The flow is simple:
Company Job Title → Business Title → Kamsa Job Match
Company Job Title: what your organization calls the role
Business Title: the internal, normalized title for consistency
Kamsa Job Match: the market-aligned job and level used for benchmarking
Clean alignment across these fields ensures accurate job leveling, consistent ranges, and reliable benchmarking in Kamsa.