Navigate a Plateau — Career Growth for Engineers, Part 6
Career Growth for Engineers · Part 6
A senior engineer has been at the same level for three years. Every review says the same thing: strong work, keep going. So they keep going. They take on more tickets, stay later before releases, and volunteer for the on-call rotation nobody wants. The fourth review says the same thing. When they finally ask their manager directly what is missing, the answer takes thirty seconds: the next level is defined by work that spans teams, and every project they've taken on in three years has sat inside one team. More effort was never going to close that gap, because the gap wasn't about effort.
That is the most common way a plateau lasts too long: applying a general fix, usually "work harder", to a specific cause. Plateaus have several causes, and the fixes don't transfer between them. Extra effort does nothing for a pay plateau, and a new framework does nothing for a promotion gap that is really about scope.
The working claim: a plateau is a diagnosis problem before it is a motivation problem. Name which kind you are in, run one fix for a fixed period, and decide on evidence.
Before you start
Pull your last two performance reviews and your company's level guide for your current level and the next one.
Write down, without editing, how you would describe the last six months of work to a friend outside the company. The words you choose ("routine", "invisible", "underpaid", "fine") are early data.
Block 30 minutes. This tutorial ends with a written plan, not a feeling.
Step 1: Name the kind of plateau (15 min)
The term goes back to Ference, Stoner and Warren's 1977 paper, which defined a career plateau as the point where further upward movement becomes unlikely. Judith Bardwick's 1986 book The Plateauing Trap separated two kinds that need very different responses: a structural plateau, where the next step isn't available (the organisation has no role above you, or promotions are frozen), and a content plateau, where the work itself has stopped stretching you. Engineers hit a few more specific versions:
Kind | What you notice | Usual cause |
Skill | Same problems, same tools, nothing new for a year | The role has a small surface, or you've mastered it |
Promotion | Stuck at level for two or more cycles despite strong reviews | Missing a next-level behaviour, usually scope, or no sponsor |
Recognition | Good work that nobody beyond your manager knows about | Work that is invisible by nature (prevention, reliability, glue) |
Pay | Your pay has fallen behind the market for your level | Internal pay bands lag external hiring rates |
Engagement | Lost interest, even in work you used to enjoy | Low autonomy or impact, conflict, or the early stage of burnout |
You may be in more than one. Rank them by which one, if fixed, would change how you feel about work the most.
Test you can run: finish the sentence "I would stop feeling stuck if ___." If the blank is a title, it is a promotion plateau. If it is a number, pay. If it is "people knew what I did", recognition. If it is "I was learning again", skill. If you can't fill it at all, look hard at engagement and at the burnout section in Step 5.
Step 2: For a promotion plateau, find the gap in writing (15 min)
Promotion plateaus are where effort is most often wasted, because the missing piece is usually a different kind of work, not more of the same. Ask your manager one question, in writing or in a 1:1 you take notes in: "Which behaviours in the next-level guide have you not seen from me yet, and what project would let me show them?"
Then map the answer. Make a two-column table: next-level behaviours in one column, your evidence from the last year in the other. Most promotion gaps show up as empty cells clustered on one theme, typically scope (work beyond your team), influence (decisions others adopted), or ambiguity (problems that arrived without a ticket).
If your manager can't name the gap, that is information too. Either the criteria aren't clear to them, or nobody senior is putting your name forward. Part 2 of this path covers writing the case; the Mentoring Engineers path covers why sponsorship matters at this stage.
Test you can run: count the empty cells in your table. If more than half sit on one theme, your next project should be chosen for that theme, even if it is less interesting than the alternatives.
Step 3: For a skill or engagement plateau, reshape the job before leaving it (15 min)
Wrzesniewski and Dutton's 2001 paper on job crafting describes how people change their work from the inside: the tasks they take on, the people they work with, and how they think about what the job is for. You don't need permission for much of this. A senior engineer bored by feature work can take ownership of the team's flaky-test problem, pair with the data team on a pipeline, or start running the incident reviews.
Hackman and Oldham's job characteristics model (1976) gives a useful checklist for what to add: variety of skills, a whole piece of work you can see through, work that matters to someone, autonomy, and feedback from the work itself. A plateau usually means two or three of those have dropped to near zero.
Test you can run: score your current role from 1 to 5 on each of those five characteristics. Pick the lowest score and write one change you could make in the next month that would raise it by one point without changing teams.
Step 4: For recognition and pay, use the market as a reference, carefully (10 min)
Recognition plateaus are common for engineers whose best work is prevention: the outage that didn't happen, the migration that went quietly. Make that work visible on purpose. Write a short monthly note to your manager listing outcomes, not activity, and present one piece of work at a wider forum each quarter. The technical writing guide helps if writing it up feels like a chore.
Pay plateaus are different. Internal bands often move more slowly than external offers, so staying put can mean falling behind without anyone deciding it. Check salary-survey data for your level and location, compare it with your pay, and raise the gap with your manager with the evidence in front of you. An outside offer is the most persuasive evidence, but use it only if you would genuinely take the job. Bluffing damages trust, and some companies don't match.
Test you can run: can you name three outcomes from the last quarter that someone two levels above your manager would recognise? If not, the recognition problem is partly a communication problem you can fix this month.
Step 5: Rule out burnout before you diagnose anything else (10 min)
An engagement plateau and early burnout look alike from the inside. Maslach and Leiter's work describes burnout as exhaustion, cynicism and a falling sense of effectiveness, caused mainly by the conditions of the work (workload, control, fairness, values) rather than by the individual. If that describes you, the fixes above won't help, and a stretch project will make it worse. Our burnout post covers the systemic side.
Test you can run: over the last month, how many weeks did you end more depleted than you started? If it is most of them, deal with load and recovery first, and come back to this tutorial after.
Step 6: Time-box one fix, then decide (10 min)
Indefinite "trying harder" is how a plateau turns into years. Choose the single fix that matches your diagnosis, give it a fixed period (one review cycle, or six months), and write down in advance what result would count as progress: a scoped cross-team project approved, a pay adjustment, a new area owned.
At the end of the period, compare the result with what you wrote. If it moved, keep going. If it didn't, and the cause is structural (no role above you, no sponsor, frozen bands), the honest answer may be a move, internally or to another company. Part 5 of this path covers switching well.
Test you can run: write your fix and its success measure on one line, with a date. If you can't write the success measure, the fix is too vague to test.
Worked example: two engineers, same plateau, different causes (composite scenario)
Context. Two senior engineers at a mid-sized insurer, on the same platform group, both stuck at senior for three years. Both say they feel stuck.
Decision. Engineer A assumes it is effort and spends two quarters taking extra tickets. Engineer B runs the diagnosis: the "I would stop feeling stuck if" sentence comes out as "the staff title". The gap table shows five of seven empty cells about cross-team scope.
Reasoning. B asks the manager for a project with scope beyond the team and gets the migration of three teams onto a shared deployment pipeline. B writes the success measure: "staff case submitted at the next cycle with that migration as the anchor."
What happened. A's reviews stay the same, and A's tiredness grows. B's migration ships in five months, and B is promoted the following cycle. A later runs the same diagnosis and finds that A's real plateau is pay, not title: A's salary is well below survey data for the level. A raises it with the evidence and gets an adjustment within the quarter.
Lesson. Both engineers were stuck. Neither was stuck in the way they first assumed, and the fix that worked for each was the one matched to the cause.
Trade-offs to make deliberately
Choice | You gain | You risk |
Stay and reshape the role | Keep your context, reputation and network | Slow progress if the cause is structural |
Take the stretch project for your gap | Direct evidence for the next level | Less enjoyable work for a while |
Use an outside offer on pay | The strongest evidence available | Damaged trust if you were bluffing |
Accept a plateau for a period | Time for depth, recovery or life outside work | Drifting if you don't set a review date |
Common failure modes
Treating every plateau as an effort problem. More of the same work rarely closes a scope gap.
Skipping the diagnosis. The fix for pay does nothing for a skill plateau, and the reverse.
No end date. "I'll give it more time" with no date or measure is how plateaus last years.
Ignoring burnout. A stretch project on top of exhaustion makes both worse.
Leaving before testing a fix. A new company can bring the same plateau if the cause was the kind of work you choose.
Final takeaway
A plateau tells you something is missing; it doesn't tell you what. Name the kind you are in, choose the fix that matches it, give it a fixed time and a written measure, and decide on the result rather than on how the week felt. Your next action: fill in "I would stop feeling stuck if ___" today, and book the gap conversation with your manager this week.
Sources
Ference, T. P., Stoner, J. A. F. and Warren, E. K. (1977). Managing the Career Plateau. Academy of Management Review, 2(4), 602–612.
Bardwick, J. M. (1986). The Plateauing Trap. New York: AMACOM.
Wrzesniewski, A. and Dutton, J. E. (2001). Crafting a Job: Revisioning Employees as Active Crafters of Their Work. Academy of Management Review, 26(2), 179–201.
Hackman, J. R. and Oldham, G. R. (1976). Motivation through the Design of Work: Test of a Theory. Organizational Behavior and Human Performance, 16(2), 250–279.
Maslach, C., Schaufeli, W. B. and Leiter, M. P. (2001). Job Burnout. Annual Review of Psychology, 52, 397–422.
Continue the Career Growth for Engineers path
Previous — Part 5: Switching Companies
Next — Part 7: Build a Network
Part of the Career Growth for Engineers learning path. Related: Run Effective One-on-Ones.
