Show Engineers What the Next Level Requires, and Who Covers the Critical Roles
The most common request from engineers is not money. It is to know what the next level asks of them. We help you write the ladder, keep a technical track beside the management one, make promotion criteria visible, open internal moves, and name successors for roles the company cannot leave vacant. You decide who is promoted and who is named; we build the framework and the record.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsThe starting point
Do Your Engineers Know What Promotion Takes?
Where the ladder is implied, the step above senior engineer is described differently by every manager. Promotion follows tenure, loud advocacy or the threat of leaving, and the default route turns strong engineers into new managers.
We help you write what progression means and who is behind each critical role.
You may be experiencing:
- Levels from junior to senior defined loosely, with the next step left to each manager.
- Promotion cases that depend on how well a manager argues, not on stated criteria.
- Strong engineers moved into management because it is the only visible way up.
- New managers who did not choose the role and were not prepared for it.
- Internal moves between teams that need both managers to agree.
- Critical roles, such as architect or head of a client account, with no named backup.
- Little record of who is ready for a larger role and what they need to get there.
What we can help with
Our Career and Succession Management Services for Software Companies
Level Definitions and Ladder
Write the levels for engineering and for other role families, describing scope, autonomy, technical depth and influence at each, in terms a manager can observe.
Technical and Management Tracks
Define a technical route through staff and principal levels and a management route from lead to head of engineering, with equal standing and a way back between them.
Promotion Criteria and Process
Set how a promotion case is raised, what evidence it needs, who reviews it and when decisions are made, so promotion follows a visible route and not advocacy.
Readiness Review
Review readiness at a fixed point in the year, with a gap list and a development plan for each person being considered, linked to the appraisal cycle.
Internal Mobility
Define how a person moves between teams: who must be informed, what notice the current manager receives and how the hand-over is handled, so the move does not depend on goodwill.
Critical Role Identification
Name the roles whose absence would stop a release or a client programme, and record the single points of dependence on knowledge, relationships or access.
Succession Planning
For each critical role, name one or more successors with a readiness view, an interim cover arrangement and development actions. Knowledge that only the incumbent holds is written down.
Development Plans
Prepare individual development plans for people on the technical and management tracks, with stretch assignments, mentoring and manager development, reviewed on a set cycle.
The deliverables
What You Receive
Depending on the agreed scope, you can expect:
- Level definitions and an engineering ladder.
- A technical and a management track with matching standing.
- Promotion criteria and a review calendar.
- A readiness review format.
- An internal mobility procedure.
- A critical role list with single points of dependence.
- Succession cards with named successors and readiness.
- Development plan formats and tracking in your system or on GullyHR.
Step by step
How We Work
Understand the Ladder as Lived
We ask engineers, leads and managers how people have actually been promoted and which expectations are unstated.
Draft the Levels
We write level descriptions for your main role families and test them against people you know well, to see if they fit.
Design the Tracks and Process
We define the two tracks, promotion route and internal move procedure, and agree who reviews and decides.
Identify Critical Roles and Successors
With leadership we name critical roles, successors and interim cover, and write down the knowledge that needs to be shared.
Review Against the Baseline
Before work starts we note where you stand. After the first promotion round we review how the criteria worked and adjust.
The difference
Make Progression Visible
A written career framework helps your company:
We do not promise outcomes. We record a baseline before work starts, covering the share of critical roles with a named successor, promotions with written evidence and internal moves completed, and report against it, so you can see what changed and what did not.
- Tell engineers what the next level asks for.
- Offer progression that does not require managing people.
- Run promotions by a visible route.
- Move people between teams without negotiating each time.
- Name backups for roles that cannot stand empty.
- Develop people against stated needs.
Find your fit
Who This Service Is For
Product Companies Growing Their Engineering Teams
Set a ladder before the first promotions create precedents.
IT Services Firms
Define progression across delivery, practice and pre-sales roles.
Founder-led Companies
Give senior people a visible route and make succession a plan.
Companies Losing Engineers to Competitors
Show a progression path where compensation alone has not been enough.
Firms with Many First-time Managers
Support the move into management and keep a route back.
How it usually shows up in information technology and software
Career paths in software companies are often implied rather than written. The title ladder runs from junior to senior engineer and then to lead or manager, and the step from senior engineer to the next level is described differently by each manager. Promotions follow tenure, loud advocacy or the threat of leaving. The default route turns strong engineers into new managers, who may not want the role and are not prepared for it, and the company loses engineering depth. Internal moves between teams depend on the managers agreeing, and some managers hold people back. Succession for critical roles, such as architects, engineering heads or key client leads, is discussed informally, and development plans for potential successors are rare.
Common challenges
Where it goes wrong in information technology and software
Levels are described loosely
Each manager explains the next step in their own way.
Management is the only way up
Strong engineers are pushed into roles they do not want.
Internal moves need permission
Managers hold back good people, and they leave instead.
Successors are unnamed
The loss of an architect or client lead has no prepared answer.
A better process
What a working version looks like
- 01
Write the ladder
Describe each level in terms of technical depth, scope, autonomy and influence, for each major role family. The succession work builds on it.
- 02
Keep two tracks
An individual-contributor track and a people-manager track with equal standing, and a stated way back from management.
- 03
Make promotion criteria public
Evidence, a review panel and timing known to all, with feedback for those not promoted.
- 04
Open internal moves
A simple posting and transfer process, with a stated notice to the current manager.
- 05
Name successors for critical roles
A short list of roles, their candidates, readiness and development steps, reviewed twice a year.
What to check this week
- Ask three engineers what the next level requires of them.
- List recent promotions and the evidence behind each.
- Count engineers who moved into management and their outcomes.
- Check how many internal moves were blocked or delayed.
- Name the successor for the engineering head and note their readiness.
What this looks like in information technology and software
The parts of career and succession management that are specific to this sector, rather than general.
Technical and Management Tracks
Progression that does not force good engineers into management.
What this coversHide
Technical and Management Tracks
Progression that does not force good engineers into management.
What this coversHideThe default software career ladder converts strong engineers into weak managers, loses the engineering capability and creates a manager who did not want the job.
Technical track
- Engineer to senior to staff and principal
- Scope defined by technical influence, not headcount
- Parity of pay and status with the management track
- Criteria stated in observable terms
Management track
- Team lead to engineering manager to head of engineering
- Capability built before the first team
- People responsibility treated as a distinct skill
- Route back to the technical track kept open
The route back matters. Engineers try management more willingly when returning is not treated as failure, and businesses that allow it lose fewer people to the experiment.
Questions on this, in information technology and software
The technical track grows people through scope and technical influence, without direct reports. The management track grows them through leading people and teams. Both should carry comparable standing, and we help you write criteria for each.
No. Many do their best work on the technical track, and managing people is a separate skill. We help you make both routes visible, so that choosing management is a decision and not a default.
In observable terms: scope, quality, autonomy, influence and collaboration at each level. We write them with your leaders and test them on real cases, so they describe how promotions have actually been earned.
By making internal moves a process, not a favour. The framework sets notice, handover and who may refuse a move and on what grounds. We also record patterns, so that repeated blocking is visible.
That is your decision. One ready-soon and one ready-later successor is a common approach. We help you assess readiness, define interim cover and write development actions, and review the list on a fixed cycle.
Often yes. We design the ladder, readiness review and succession cards first, then set up records, reviews and reminders in your system or on the GullyHR platform, with access limited to those who need it.
Once there are several levels of engineers, yes. It lets strong engineers grow without managing, and it makes management a choice.
Technical depth, scope of work, autonomy and influence on others at the target level, shown by evidence and reviewed by more than one person.
With a defined trial, support and a respected route back to the technical track. Returning should not be seen as failure.
Roles whose absence would stop delivery or damage a client relationship, such as architects, delivery heads and owners of critical systems.
Build Careers and Backups Into the Company
If progression is unclear and critical roles have no cover, start by writing down the levels and the names.
Prefer to talk first? Call +91 80958 58589 or write to hello@gullyhr.com.
Book a Career Framework Consultation
Tell us about your levels, tracks and the roles that cannot be left vacant.
The general method — what career and succession management covers, the questions it answers and what an engagement produces — is the same whatever the sector, and is set out on the succession and leadership development page. What is above is the part that differs for information technology and software.
Other HR topics for information technology and software
Where to start
Most engagements begin with a review of how this runs in your business today, then a written process and the sequence to implement it.
See all HR topics for information technology and software, or another industry.