Career Levels Across Companies & Industries

A career level is the position a role occupies in a company's internal hierarchy. It sets the scope of work you are expected to handle, how much supervision you receive, the salary band your pay is drawn from, and what you must demonstrate to move up.

At large IT services companies the level is usually expressed as a grade code rather than a title, for example C3A at TCS or JL4 at Infosys, which is why two people with the same job title can sit at different levels.

Titles are marketing and grades are structure. Each company designs its own ladder around its own business, so the number of rungs, the width of each band, and the point at which a title changes are all internal decisions.

The practical consequence is that a Technical Lead at one firm may carry the scope of a Senior Software Engineer at another. Comparing grade codes and responsibilities is reliable; comparing titles is not.

Three things move together: scope, autonomy, and influence. Scope grows from a task, to a module, to a system, to a programme spanning several teams. Autonomy grows from being told what to do, to being given a problem, to defining which problems are worth solving. Influence grows from your own output, to your team's output, to decisions made by people who do not report to you.

Pay follows those three rather than leading them, which is why arguing for a promotion on the basis of tenure rarely works.

At most large employers the decision is made in a committee or panel rather than by your manager alone. Your manager assembles evidence, usually a written case covering the scope you have handled, examples of impact, and feedback from people you worked with, and a group of senior reviewers compares that case against the written expectations for the next level.

This matters because the decision is made by people who have not seen your work directly. Written, legible evidence is worth more than informal reputation.

Services ladders are generally structured and predictable, moving at roughly two to four years per grade, with annual appraisal cycles and rating systems that gate eligibility.

Product companies tend to be faster and more variable at the lower rungs and slower above senior, because each further step requires a larger demonstrated scope rather than another successful year.

Read the written expectations for the level above yours, then compare them honestly against what you did in the last year. The gap is your plan. In most cases the missing item is not skill but evidence of scope: you have done good work inside a well defined boundary and have not yet owned something ambiguous.

Then choose work that produces that evidence, tell your manager explicitly that you are working toward the next level, and keep a written record of decisions you made and what resulted. Ratings and appraisal cycles decide when the case can be submitted, so know your company's calendar.

Ignore the title and map the scope. Write down the largest thing you have owned end to end, how many people depended on it, and what decisions you made without approval. Then compare that against the target company's published expectations for the level they are offering.

Expect the possibility of a sideways or downward step on paper, especially moving from a services firm to a product company, because the ladders are calibrated differently. A lower number with wider scope is usually the better outcome.

Because there is no external standard. A company can add a rung, rename a band, or split one level into two without telling anyone outside. Some firms reserve the Senior prefix for people leading teams, others hand it out at four years of experience.

Mapping tables like the one on this page are useful for orientation, not for arithmetic. Treat them as a way to find the right ballpark, then verify against the written expectations and the actual responsibilities described in the job.

Yes, almost always. Each grade has a range, and the top of one range usually overlaps the bottom of the next. That is why a strong performer at one grade can earn more than a new arrival at the grade above.

It also explains why a promotion sometimes produces a smaller raise than expected: if you were already near the top of your band, the move may place you near the bottom of the next one.

This page covers career levels and grade codes at large IT services companies such as TCS, Infosys, Wipro, HCLTech, and Cognizant, where progression is organised around bands, appraisal ratings, and grade codes.

The engineering levels page covers product technology companies such as Google, Meta, and Microsoft, where progression is organised around L, E, or numeric ladders and compensation is heavily weighted toward equity. Use this page for services careers and that one for product company careers.

Within one company, yes, because the grade determines the band. Across companies, no. A mid grade at a firm with aggressive pay can exceed a senior grade elsewhere, and location changes the picture again.

When comparing offers, compare the full package and the scope of the role rather than the grade label attached to it.

Most large ladders split into an individual contributor track and a management track somewhere around the lead or architect grade, and moving between them is normally possible at the equivalent rung.

The switch is easier before you are several levels up either branch, because the evidence each track wants diverges as scope grows: deep technical ownership on one side, organisational outcomes on the other.