30 October 2026 EN ES
The Career Ladder

How people actually move up, sideways and out

Moves

Moving Back to IC as Progression When the Next Rung Is Full

A three-part test for deciding whether returning to IC is a deliberate progression move, not a retreat, when the next management rung is full.

Illustration: Moving Back to IC as Progression When the Next Rung Is Full

You are not asking for permission to stop managing. You are asking whether the next management rung is open, whether the IC work is real, and whether the move protects your next promotion. In the 2026 LeadDev data, 32 percent of people in managerial roles said they were weighing a return to individual contributor work, up from 24 percent in 2025. The decision is easier when the org chart, the work, and the promotion path all point the same way.

The org chart decides before the title does

Start with the chart, not the feeling. A full rung changes the question from readiness to fit: does the current role still have work that matches your strengths? The memo should say three things: the next rung is full, the current role has no open scope, and the IC path has a named owner. The memo should be short enough to send to your director.

Ask for the current org chart, the approved headcount, and the list of open roles at the next level. No open scope, no approved headcount, and no named successor means the rung is effectively full. If the block is a cautious director rather than a closed ladder, say so in the memo. A full rung is an org fact, not a personal judgment.

LeadDev's 2026 engineering leadership report drew on 600 responses. The 2026 data records 22 percent of respondents saying managerial job counts fell, while 19 percent said they rose. Among respondents in organizations with fewer manager roles, 59 percent said line management was affected and 65 percent said middle management was affected.

The IC role must fit the work you want to do

Map the IC work you want to do. Write the project, the system, the review, or the technical standard you would own. When you cannot name it, the move is a mood, not a plan. The finished map is a short IC brief: the work, the owner, the expected outcome, and why your current management role is the wrong container for it.

Look for work that would be stronger with your hands in it. The work may be a service that needs a technical owner, a review process that calls for a senior engineer, or a migration that needs someone who can write code and explain tradeoffs. The org should gain something: a faster review, a cleaner rollout, a stronger technical decision. A smaller team, a quieter calendar, or a chance to avoid a difficult conversation is weak evidence.

The 2026 data shows 37 percent of respondents saying their hands-on technical responsibilities had grown over the prior year, compared with 25 percent in 2025. The 2026 data also records 45 percent of respondents saying they worked more hours per week than a year earlier, with the prior-year figure at 38 percent and the 2024 figure at 35 percent. Those numbers indicate the pull back to technical work is real, but they do not prove your case. Your case needs a role, a scope, and a reason it is better for the org.

Do not frame the move as escape from meetings, burnout, or a bad team. Tech management burnout is real, but a promotion-style case cannot rest on relief. Relief can be a reason to talk; it is not a reason to move. A manager-to-engineer transition should be about where your best work goes, not where your stress is lowest.

The move needs a promotion-style case

Build the case for future progression. Treat the IC move like a promotion case: state the level you are entering, the evidence that you can do it, and the next rung you would target. Say what the IC role protects: technical depth, delivery, architecture, mentoring, or a product area that needs a strong engineer-manager hybrid.

Name the next IC rung you would target and the evidence you would need to reach it. A missing next step may protect your sanity but not your career. Once the path exists, write it in the same language your org uses for promotion: scope, impact, quality, and peer recognition.

Then name what it does not protect: title, seniority, or a vague promise that management will return. The final case is a conversation with your director: the IC role is named, the progression path is named, and the review date is set. A review date gives the move a test, not a permanent exit. An answer of only reassessment means: keep the current role and look for a different rung.

Advertisement