Building a Job Architecture: Levels, Job Families and the End of Title Chaos

Somewhere between 200 and 1,000 employees, most Indian companies hit the same wall: forty distinct titles for what are really six levels of work, "Senior Manager" meaning different things in different departments, and promotions granted as retention currency until the word loses meaning. The cure is a job architecture — the structural skeleton on which pay ranges, career paths and workforce analytics all hang.

What a job architecture contains

A complete architecture has four components:

• Job families and sub-families. Groupings of jobs sharing a common nature of work — Engineering, Sales, Finance, Operations — subdivided where the work genuinely differs (within Engineering: software development, quality, infrastructure).
• Levels. A single organisation-wide spine of levels — typically 8 to 12 from entry to executive — each defined by descriptors covering scope, autonomy, complexity, knowledge and influence. Levels are the universal currency: a Level 5 in Finance and a Level 5 in Marketing represent comparable job size even though the work differs entirely.
• Career tracks. At minimum, a management track and a professional/individual-contributor track that both reach senior levels. The IC track matters enormously in India, where deep specialists are too often forced into people management to progress — and then lost when they refuse.
• Titling rules. A documented mapping from level and family to permitted external titles. This is where title chaos goes to die, so expect resistance.

The build sequence

• Size the jobs first. Architecture rests on consistent job sizing, which is what job evaluation provides. Evaluate anchor jobs across functions, then slot the rest. Skipping this step and levelling by current titles simply launders existing chaos into a new format.
• Draft level descriptors in your own language. Generic descriptors borrowed from a consulting deck will be ignored. Write what Level 4 autonomy actually looks like in your business, with examples managers recognise.
• Map every employee. This is the confronting step: some people will map below their current title. Decide your transition policy before mapping — typically, incumbents keep personal titles while the role is regraded, with corrections applied through natural attrition and the next cycle.
• Connect the architecture to money. Each level anchors a pay range informed by Indian market surveys for the relevant family and market. Without this connection the architecture is decorative.
• Govern it. New roles must be levelled through a defined process before being advertised. Exceptions need senior sign-off. An ungoverned architecture decays in roughly two years.

Design tensions to resolve deliberately

• Granularity. Fewer, broader levels are easier to govern but make promotions rarer; more levels offer progression milestones but invite hair-splitting. Most mid-size organisations land at 8–10 levels.
• Global versus local titles. Customer-facing functions often need market-standard external titles (the Indian banking and SaaS markets have strong title conventions) that differ from internal levels. Permit dual titling explicitly rather than pretending it will not happen.
• Wage code and compliance alignment. As labour codes are implemented, having a clean structure of levels and job families makes compliance classification — and any future pay transparency or equity reporting — dramatically easier than reconstructing logic from scattered titles.

What good looks like after twelve months

A working architecture shows up in small ways: recruiters level a new role in minutes instead of debating titles for a week; the CFO can see span and layer data that actually means something; employees can name the two or three capabilities standing between them and the next level; and promotion committees argue about evidence, not nomenclature.

The build typically takes three to five months for a mid-sized organisation, and the hardest part is never the framework — it is the political will to apply it to existing roles. Companies tackling this without an in-house rewards leader often anchor it within a fractional CHRO engagement, where it pairs naturally with pay-band design. If leadership hiring is underway in parallel, level the new roles before the search starts — our executive search team will tell you that mis-levelled mandates are the single biggest cause of failed offers.

To discuss what a job architecture would involve for your organisation, get in touch.