Job Architecture and Levels: A Practical India Guide

Job architecture is the structure that tells you what a role is, how senior it is, what it is worth, and what the next step looks like. Most Indian SMBs build one by accident: a title is invented to close a hire, a level is created to justify a counter-offer, a band is stretched to fit a referral. Two years later nobody can explain why one senior engineer earns 40% more than another, why a "Manager" in sales reports to an "Executive" in operations, or what an employee actually has to do to get promoted.

This guide shows how to build a job architecture and levelling framework that fits a growing Indian company: the vocabulary, the level descriptors, the dual career ladder, how levels connect to pay bands and promotions, how to map your existing people into the structure without triggering a morale crisis, and how to carry it into job descriptions, hiring scorecards and your HR system. It is written for HR leads, founders and people-ops teams at organisations between roughly 30 and 1,000 employees, where the pain is real but a global consulting engagement is not on the table.

The symptoms that tell you it is time

You do not need a job architecture on day one. You need one when these start appearing:

• Two people doing comparable work sit at visibly different pay levels and nobody can defend the gap
• Titles have inflated to the point where you have four "Heads" and no clear hierarchy
• Every promotion is a negotiation rather than a decision against criteria
• Recruiters cannot tell whether a candidate is "senior" in your terms, so offers get levelled by gut feel
• Managers cannot answer "what do I need to do to get to the next level?" in a way that survives scrutiny
• Your compensation benchmarking exercise stalls because you cannot map your roles to survey roles
• Reorganisations are painful because nobody knows which roles are equivalent across teams
• Exit interviews cite "no career path" more often than pay

Any three of these together is a sufficient trigger. The cost of waiting is not just fairness; it is that every future compensation, promotion and workforce planning decision is made on sand.

The vocabulary, made unambiguous

Most confusion in this area is terminological. Fix the words first.

Two rules prevent most downstream mess. First, level is universal and function-agnostic — an L5 in marketing and an L5 in engineering represent comparable scope, complexity and impact, even though the work is entirely different. Second, title follows level; level does not follow title. When a candidate negotiates a title, you are agreeing to a label. When you agree a level, you are agreeing to scope and pay. Never let the first quietly change the second.

How many levels should you have?

The most common mistake is too many. Every level you create must be defensible in a promotion conversation, distinguishable in a level descriptor, and supportable by a distinct pay range. If you cannot articulate the difference between L4 and L5 in two sentences that a manager could apply consistently, you have one level too many.

Practical guidance by company size:

• Under 50 employees: 4 to 5 levels. Junior, Professional, Senior, Lead/Manager, Head.
• 50 to 250 employees: 6 to 7 levels, with the individual contributor and manager tracks separating at around level 5.
• 250 to 1,000 employees: 7 to 9 levels, including an executive band.

Aim for a level to represent roughly two to four years of genuine capability growth at the early stages, widening at senior levels. If people move up a level annually, your levels are too narrow and you are manufacturing title inflation.

Level descriptors: six dimensions that work

Write descriptors against dimensions, not tasks. Tasks vary by function; dimensions do not. Six dimensions carry almost all the weight:

1. Scope — what the person is responsible for: a task, a feature, a product area, a function, the company
2. Complexity — how well-defined the problems are: routine, variable, ambiguous, novel
3. Autonomy — how much direction is needed: close supervision, guidance on approach, outcomes only, sets the direction
4. Influence — who they affect: themselves, their team, adjacent teams, the organisation, the market
5. People — coaching, mentoring, managing, managing managers
6. Business impact — from task completion to measurable team results to functional outcomes to company performance

Here is a compact eight-level skeleton you can adapt. Keep each descriptor to a paragraph; long descriptors go unread.

L1 — Entry. Learns the role. Executes well-defined tasks with close guidance. Impact is limited to their own output and measured in quality and timeliness. Typically 0 to 2 years of experience.

L2 — Developing. Executes standard work independently. Escalates non-routine issues appropriately. Beginning to spot process problems and suggest fixes. Impact is consistent individual delivery.

L3 — Professional. Owns a defined area end to end. Handles variable problems without direction on approach. Reliable under normal conditions; seeks help on genuinely ambiguous work. Mentors L1s informally.

L4 — Senior professional. Owns an area with ambiguity in it. Defines the approach, not just the execution. Improves how the team works, not just what it delivers. Formal mentor to juniors. Trusted to represent the team in cross-functional discussions.

L5 — Lead (IC track) or Manager (people track). IC: leads a significant workstream spanning multiple people, sets technical or functional direction for it, and is accountable for outcomes rather than tasks. Manager: accountable for a team's delivery, performance and development, with hiring and performance responsibilities.

L6 — Principal (IC) or Senior Manager (people track). IC: solves problems affecting multiple teams, sets standards that others follow, and influences roadmap or functional strategy. Manager: runs a substantial team or multiple squads, owns a functional plan and budget, and develops managers.

L7 — Distinguished (IC) or Director. Impact spans the function. Sets multi-quarter direction. Decisions affect the company's operating performance. Accountable for outcomes across teams they do not directly control.

L8 — Fellow or Head of Function. Sets organisational direction for a discipline. Accountable to the leadership team for functional performance, capability building and long-horizon bets.

Write these once, centrally, then have each function produce a one-page functional overlay that translates the dimensions into recognisable language for that discipline. The overlay may not add or remove levels.

The dual career ladder

Organisations that only promote into management manufacture two problems: they lose their best practitioners, and they create managers who did not want the job. A dual ladder fixes both, but only if three conditions hold:

1. Genuine pay equivalence. L6 IC and L6 Senior Manager sit in the same band with the same range. If the IC range is quietly lower, the ladder is decorative and everyone knows it.
2. Genuine status equivalence. Senior ICs are in the forums where decisions are made. If leadership meetings are managers-only, the ladder is decorative.
3. Movement in both directions without stigma. A manager who returns to an IC role at the same level is making a lateral move, not a demotion, and should be described that way in writing.

State in the policy that the tracks separate at a named level, that criteria differ but scope is equivalent, and that switching tracks does not change level by default.

Building it: a ten-step method

Step 1: Inventory what exists

Export every current employee with title, department, reporting line, date of joining, current pay and a one-line description of what they actually do. Expect surprises: duplicate titles for different work, unique titles for identical work, and people whose actual role has drifted far from their designation.

Step 2: Define job families and sub-families

Group work by the skills required, not by the reporting structure. A typical Indian SMB lands on eight to twelve families: Engineering, Product, Design, Data, Sales, Customer Success, Marketing, Finance, People, Operations, Legal and Compliance, Administration. Sub-families come later and only where volume justifies them; do not create a sub-family for one person.

Step 3: Write the level framework

Use the six dimensions. Decide the number of levels, write the generic descriptors, and decide where the IC and manager tracks separate. This is a small-group exercise — two to four people — not a committee.

Step 4: Create the role catalogue

For each family, list the roles that exist and the levels at which each role can exist. Not every role exists at every level. "Payroll Executive" may exist at L2 to L4; "Payroll Manager" at L5 to L6. This catalogue is the backbone of your architecture and the thing recruiters and managers will actually use.

Step 5: Slot current employees

Map each employee to a role and level based on the work they genuinely do today, not on their title, their pay, or their tenure. Do this in calibration sessions with managers, family by family, and require evidence for each slotting. Slot first, look at pay second — otherwise you will reverse-engineer levels from salary and reproduce every existing inequity inside a new framework.

Step 6: Reconcile the mismatches

You will find three categories, and each needs a different response.

• Under-levelled and underpaid. Real gaps. Prioritise these for correction and set a timeline, even if the budget forces phasing.
• Over-titled but correctly paid. Common. Handle through title alignment at the next cycle with careful individual conversations, or grandfather the title and align at the next move.
• Correctly levelled but paid above the range. Do not cut pay. Freeze or slow increases until the range catches up, and say so transparently.

Never reduce someone's pay to fit a new structure. The reputational cost outweighs any budget benefit, and it may raise contractual issues.

Step 7: Attach pay ranges

Covered in detail below.

Step 8: Write promotion criteria

For each level transition, state what evidence is required, who decides, when decisions are made, and what happens if criteria are met but no budget or scope exists. That last one is the question employees actually care about.

Step 9: Configure your HR system

Levels, grades, families and positions belong in your HRMS as structured fields with effective dating, not in a spreadsheet that one person maintains.

Step 10: Communicate and run the first cycle

Publish the framework, train managers, then run one full promotion and compensation cycle through it before declaring it finished. The first cycle is where the real design flaws surface.

A realistic timeline for a 200-person company: eight to twelve weeks of design and slotting, one cycle of live operation, and a review after six months.

Connecting levels to pay: bands, ranges and compa-ratio

A job architecture without a pay structure is a filing system. The pay layer is what makes it useful.

The building blocks

• Range midpoint. Your target pay for a fully competent performer at that level. Usually anchored to a market reference point for comparable roles.
• Range minimum and maximum. Typically the midpoint less and plus a defined percentage. Range spread commonly widens with seniority: narrower at junior levels where capability differences are smaller, wider at senior levels where individual impact varies enormously.
• Overlap. Adjacent ranges should overlap. A top performer at L3 can legitimately earn more than a new joiner at L4. Zero overlap forces promotions purely to fix pay.
• Compa-ratio. Actual pay divided by the range midpoint. Below 0.85 usually signals a new joiner, a developing performer or a genuine gap. Above 1.15 signals a strong performer, an over-market hire, or someone ready for the next level.

An illustrative structure

Do not copy these numbers. Derive your own from your market data, your ability to pay and your desired market position (for example, targeting the market median for most levels and the upper quartile for a few critical roles).

India-specific considerations

Cost-to-company versus fixed pay. Indian offers are usually discussed as CTC, which bundles fixed pay, variable pay, employer statutory contributions and sometimes benefit costs. Build your bands on a single consistent definition — fixed gross is usually cleanest — and convert to CTC for communication. Bands built on CTC become distorted the moment someone's variable component or benefit elections differ.

Variable pay by family. Sales roles carry a much higher variable proportion than finance roles at the same level. Define the standard fixed-to-variable split per family per level, and band the fixed component.

Location differentials. If you hire across metros and tier-2 cities, decide explicitly whether you run one national band, a small number of location tiers, or role-based exceptions. One national band is simpler, aids internal mobility and remote hiring, and costs more in lower-cost locations. Whatever you choose, write it down, because ad-hoc location decisions are the fastest route to internal pay inequity.

Benchmarking caution. Salary survey data varies in quality and in the roles it maps to. Use at least two sources where possible, check that the comparator set resembles your company in size, sector and funding stage, and re-check annually rather than rebuilding bands every quarter.

Statutory interaction. Changes to salary structure interact with provident fund wage definitions, gratuity accrual, bonus eligibility thresholds and minimum wage floors. Before you restructure bands, have payroll model the statutory impact, and confirm current rules and thresholds with your compliance advisor rather than assuming last year's treatment still applies.

Promotion criteria and governance

The framework earns trust in promotion decisions, so build governance deliberately.

What a promotion means

Define it precisely: "A promotion recognises that an employee is already performing consistently at the next level's scope, complexity and autonomy, and that the business requires that scope in their role." Two ideas are embedded here, and both matter. Promotion follows demonstrated performance at the higher level, not potential. And the business must need the scope — promoting someone into scope that does not exist creates an over-levelled employee and a future problem.

Evidence requirements

For each transition, require a short written case: specific examples mapped to level dimensions, manager assessment, peer or stakeholder input for senior levels, and performance history. Cap the case at one or two pages. Long promotion documents reward writing ability rather than capability.

Calibration

Promotions are decided in calibration sessions where managers present cases against the framework, not in one-on-ones. Calibration is the single most effective control against inconsistency, favouritism and unconscious bias. Keep notes on decisions and reasons.

Cadence

One or two promotion cycles per year, aligned to the compensation cycle. Off-cycle promotions should be genuinely exceptional, require an extra approval, and be reported to leadership so you can see whether "exceptional" is becoming routine.

The uncomfortable case

Someone meets the criteria but there is no budget or no scope. The honest answer is to say so, explain what would change the answer, give a review date and document the conversation. The dishonest answer — inventing a title, or promising next cycle without intending it — costs you the person and the framework's credibility at the same time.

Job descriptions that match the architecture

A job description is where architecture meets the outside world. Keep it short, structured and connected to the level.

Template:

1. Role and level. Role name from the catalogue, level, family, track, reporting line, location, work pattern.
2. Purpose. Two sentences on why the role exists and what changes if it is done well.
3. Outcomes. Four to six measurable outcomes expected in the first 12 months. Outcomes, not activities: "reduce payroll processing time to two days" rather than "process payroll".
4. Responsibilities. Six to eight bullets. If you need fifteen, you are describing two roles.
5. Requirements. Split into must-have capabilities and useful-but-teachable. Be ruthless: every unnecessary requirement narrows your pipeline without improving quality.
6. Skills. Mapped to your skills taxonomy with proficiency levels.
7. Level indicators. Two or three lines from the level descriptor so candidates and interviewers share an understanding of seniority.
8. What we offer. Concrete and specific.

Illustrative extract for a Payroll Specialist, L4:

Purpose: Own end-to-end monthly payroll for a 600-person multi-state workforce, ensuring accuracy, statutory compliance and on-time payout. Outcomes (12 months): Payroll error rate below 0.2% of payslips; statutory filings completed before due dates every month; month-end close reduced from five days to three; documented SOP covering every recurring exception. Level indicators (L4): Works independently on variable problems; defines the approach for their area; improves process rather than only executing it; mentors junior team members.

Notice how the level indicators make the seniority legible. A candidate reading this knows whether they are being hired to run payroll or to help run it.

The skills layer

Levels describe seniority; skills describe capability. Organisations moving toward skills-based workforce management add a skills taxonomy on top of the architecture. Done well, it powers internal mobility, learning plans and workforce planning. Done badly, it becomes a 400-item spreadsheet nobody updates.

Keep it disciplined:

• Limit the taxonomy. Fifteen to thirty skills per job family is plenty. Split into technical, functional and behavioural.
• Use few proficiency levels. Four is enough: Aware, Working, Proficient, Expert. Define each in one sentence with an observable behaviour.
• Map skills to roles, not to people first. Define the skill profile a role requires, then assess people against it. The gap between the two is your learning plan and your internal mobility map.
• Refresh on a cycle. Twice a year, tied to performance conversations. A taxonomy that is updated ad hoc becomes stale within two quarters.
• Connect it to hiring. Interview scorecards should assess the skills the role profile requires, at the proficiency the level demands.

Resist the temptation to build the skills layer first. Without levels, skill profiles have no seniority anchor, and you end up with a catalogue of capabilities that cannot tell you what anyone should be paid.

Configuring your HR system

The architecture must live in your HRMS, not in a document. Minimum data model:

• Employee record fields: job family, sub-family, role, level, track, grade, title, position ID, manager, location, effective date
• Effective dating: every level or grade change carries an effective date and a reason code (promotion, lateral move, reorganisation, correction), so you can reconstruct history
• Role catalogue as master data: roles maintained centrally, selected from a list rather than free-typed, which prevents title sprawl
• Pay range table: range minimum, midpoint and maximum by grade and location tier, with compa-ratio calculated automatically
• Approval workflow: level changes routed through HR before they take effect, so nobody self-serves a promotion through a data edit
• Reporting: headcount by level and family, compa-ratio distribution, promotion rates by level and demographic group, range penetration, vacancies by level

That last report set is what turns the architecture from a governance artefact into a management tool. Once you can see promotion rates by level and group, and compa-ratio distributions by family, pay and progression conversations become evidence-based.

Titles: keeping them honest

Title inflation is the slow leak that empties a job architecture. It usually starts with a single justified exception — a candidate needs "Director" on their business card for client credibility — and ends with a company where titles carry no information.

Guardrails that work:

• Titles come from the catalogue. Every title maps to exactly one role and level. No free text in offer letters.
• One approval route. Any title outside the catalogue requires HR head approval and a documented reason.
• Separate external titles where genuinely needed. Client-facing roles may carry a customer-facing title distinct from the internal level. Record both; pay and promotion follow the internal level.
• Do not use titles as compensation. If someone deserves more money, pay them more money. A title given instead of pay costs nothing today and creates an unfixable expectation tomorrow.
• Audit annually. Count titles. If you have more distinct titles than roles in the catalogue, the guardrails are not holding.

Twelve common mistakes

1. Too many levels. Creates annual micro-promotions and endless justification work.
2. Levels reverse-engineered from salary. Locks existing inequities into the new structure permanently.
3. Descriptors written as task lists. They stop being applicable the moment the work changes.
4. Function-specific levels. L5 means something different in each team, which destroys cross-functional comparability.
5. A decorative dual ladder. Equivalent on paper, unequal in pay, status or influence.
6. Slotting done by managers alone, without calibration. Generous managers create a permanently over-levelled team.
7. Cutting pay to fit ranges. Never worth it.
8. Skipping the communication plan. Employees interpret silence as a plan to restructure pay downward.
9. Building the skills taxonomy first. Produces an unanchored catalogue.
10. Never revisiting the architecture. Roles evolve; a framework untouched for three years describes a company that no longer exists.
11. Treating it as an HR project. Without managers owning slotting and calibration, adoption fails.
12. Publishing ranges without preparing managers. If you open pay ranges to employees, managers must be able to explain range position, compa-ratio and what moves someone within a range.

Communicating the rollout

Sequence matters. A rollout that surprises people generates rumours of pay cuts within a day.

Leadership alignment first. Agree the framework, the slotting principles and the budget for corrections before anything is announced.

Manager briefing next. Managers must be able to answer three questions before employees hear anything: what is my level, why, and what does this mean for my pay. Run a session, provide a one-page crib sheet, and rehearse the difficult conversations — particularly the over-titled case.

Individual conversations before the all-hands. Anyone whose title or level changes should hear it from their manager privately, never in a group setting or a system notification.

Then publish. The framework, the level descriptors, the promotion criteria and the process. Whether you publish pay ranges is a separate decision: transparency builds trust but requires manager capability and a clean structure. Many organisations publish levels and criteria first, and ranges a cycle later once the structure has settled.

Reinforce in the cycle. The framework becomes real when the first promotion cycle visibly uses it and when hiring managers level candidates against it.

Metrics to watch after launch

Keeping it alive

Set a review cadence and stick to it:

• Quarterly: new roles added to the catalogue, off-cycle changes reviewed, title audit spot-check
• Half-yearly: skills profiles refreshed alongside performance conversations
• Annually: pay ranges reviewed against market data, level descriptors checked for drift, promotion criteria updated based on the last two cycles
• On major change: any reorganisation, acquisition or new business line triggers a family and role review before new titles are created

Assign a named owner. Job architecture without an owner decays within one hiring surge.

Frequently asked questions

How long does it take to build a job architecture for a 200-person company? Roughly eight to twelve weeks of concentrated work: two weeks for inventory and family definition, two to three weeks for level descriptors and the role catalogue, three to four weeks for slotting and calibration, and two weeks for pay range attachment and communication preparation. Add one full promotion and compensation cycle before you consider it settled.

Should we publish salary ranges to employees? It is a choice, not an obligation, and it should follow structural readiness. Publish only when levels are consistent, ranges are defensible and managers can explain range position credibly. Publishing ranges over an inconsistent structure converts a quiet problem into a loud one. A common path is to publish levels and promotion criteria first, then ranges after a cycle.

What do we do about someone paid above their range? Do not cut pay. Hold or slow increases until the range moves up around them, tell the person honestly where they sit, and if they are genuinely operating at the next level, address it through promotion rather than through the range.

How do we handle titles that clients expect, such as "Director" or "Vice President"? Use a documented external title distinct from the internal level, record both in the HR system, and make clear in the offer that pay, promotion and internal standing follow the internal level. Restrict this to genuinely client-facing roles, or the exception becomes the rule.

Do we need separate levels for each function? No. Use one universal level framework with functional overlays that translate the descriptors into each discipline's language. Separate frameworks per function make cross-functional moves, pay equity analysis and workforce planning far harder.

How does job architecture connect to a skills-based approach? Levels define seniority; skills define capability. Map a required skill profile to each role and level, then assess people against it. The architecture gives skills a seniority anchor so you can distinguish between someone who knows a skill and someone who applies it at senior scope.

What is the first thing to fix if we have no framework at all and limited time? Write the level descriptors and slot your people honestly. Everything else — pay ranges, promotion criteria, skills, titles — hangs off those two artefacts. A company with clear levels and rough pay bands is in far better shape than one with polished bands attached to arbitrary levels.

How do we avoid demotivating people whose titles are reduced? Prefer grandfathering to reduction. Keep the title, align the level internally, and align the title at the next role change. Where a change is unavoidable, do it privately, explain the reasoning, confirm that pay is unaffected, and give a concrete path to the higher level.

Bringing it together

A job architecture is not an exercise in taxonomy for its own sake. It is the structure that makes pay defensible, promotions consistent, hiring accurate and career paths legible. The work is mostly judgement rather than technique: how many levels your organisation can genuinely distinguish, where the tracks diverge, and how honestly you slot the people you already employ.

Start with levels. Slot people on the work they do rather than the titles they hold. Attach pay ranges only after slotting, never before. Then carry the structure into your job descriptions, your hiring scorecards and your HR system so it is used every week rather than reviewed once a year.

Once the framework exists, the operational challenge is keeping it accurate as people join, move and get promoted. CozyHR holds job families, levels, grades and positions as structured, effective-dated fields alongside payroll and performance data, so compa-ratio, promotion rates and headcount by level come out of the system rather than out of a spreadsheet rebuild. Try CozyHR to put your levelling framework somewhere it will actually stay current.