Small engineering teams avoid career frameworks because they feel like corporate machinery for a company of twelve. The consequence is not the absence of a ladder but an invisible one: titles awarded to whoever raised it, salaries set by who negotiated hardest, and promotion decisions defended after the fact. In the Indian market, where people move for a title as readily as for money, that invisibility is a retention problem rather than an administrative one.
A useful framework at this size is short — four or five levels, one page each — and describes behaviour rather than tenure. What scope of problem does someone at this level own. How much ambiguity can they absorb before needing direction. What is their effect on people other than themselves. And what would they be trusted to decide alone. Years of experience should not appear anywhere, because it is a proxy that produces both premature and overdue promotions.
The distinction that matters most is between the levels where you deliver work and the levels where you increase other people's ability to deliver. Somewhere around the third level, the job stops being about personal output and starts being about design decisions others build on, reviews that raise quality, and problems solved before they reach anyone else. Teams that never articulate that produce senior engineers who are fast juniors, and are then surprised when adding people does not add throughput.
Provide two directions from there, and mean it. A technical track and a management track, at genuinely equivalent pay and standing. Without that, your strongest engineer eventually becomes a manager because it is the only way up, and you lose your best engineer to gain a reluctant manager. Both roles are hard and different, and the honest version of this framework lets somebody move back without it being a demotion.
Attach pay bands to levels and be transparent about the bands even if not about individuals. In this market compensation information circulates anyway, and it circulates inaccurately. A published band per level converts a private negotiation into a shared understanding, removes the advantage held by whoever is most willing to threaten to leave, and makes it possible to correct the drift that accumulates in any team where offers were made at different times under different pressures.
Then use it, which is where most frameworks fail. Review against it on a stated cadence, tell people specifically what stands between them and the next level, and be willing to say not yet with reasons. A ladder that exists as a document and is never referenced in a conversation is worse than none, because it advertises a process that does not operate — and engineers read that accurately as a signal about everything else the company says it does.
