The Inflection Point: Where an Engineering Career Stops Being Linear
- Eric Herrenkohl

- 5 days ago
- 5 min read
For twenty years I was the person firms called to buy leadership talent for engineering-intensive businesses. I built and led a retained executive search firm, and I saw the real cost and the real failure rate of hiring senior leaders from the outside. Today I help those same firms build their own leaders instead.
Changing seats like that teaches you something about how engineering careers actually work, and more usefully, about where they stop working.
Why engineering careers look linear until they are not
Careers in engineering firms move along a remarkably clean curve for a long time.
You pass the FE, then the PE. Staff engineer to project engineer. Project engineer to project manager. Project manager to senior project manager. Senior project manager to discipline or department lead. Every one of those steps asks for more of what the last step asked for: more technical depth, more complexity, more accountability for schedule, budget and quality.
So people learn a rule, and for a long time the rule is correct. The way to advance is to be better at the work.
That rule holds for 10+ years, which is long enough for it to feel like a law of nature rather than a stage of a career. The firm reinforces it, because the firm needs the work done well and the person doing it well is valuable exactly as they are.
Then the curve breaks.
Somewhere around the VP level, and sometimes a half step before it, the firm quietly starts asking for a different job. Not a harder version of the same job. A different one. Less pushing, more developing. Less solving, more deciding. Less personal output, more organizational output.
The difficulty is that nobody announces this. There is no memo, no revised job description, no formal moment where the firm says the rules that governed your first twenty years have been retired. Expectations change in conversations the leader is not in, and the leader finds out through absence. Their name stops appearing on lists. Their scope stops growing. The feedback gets vaguer.
Leadership capacity in engineering firms rarely erodes gradually. It breaks at specific transitions where the shape of the work changes.
What actually changes at the VP level in a consulting engineering firm
When I work with senior teams, I find it useful to separate the change into two categories. The first is the work itself. The second is how readiness is experienced by everyone else.
On the work, five transitions come up again and again.
Doing the work becomes owning outcomes the leader can no longer personally produce
Delegating tasks becomes delegating responsibility, including the decisions that come with it
Managing individuals becomes leading other leaders who run large teams and major client relationships
Being the fastest problem solver becomes deciding which problems deserve the firm's attention at all
Protecting a region, practice or discipline becomes building the enterprise
Each of those is a genuine change in the job. A VP who has made none of them can still be extremely productive technically but becomes a leadership constraint on firm growth., The second category matters just as much and gets discussed far less. A leader also has to be perceived as ready. That perception is built from signals: operating at the right altitude in an executive room, starting with the answer rather than the analysis, influencing peers without authority, carrying credible confidence rather than volume, and putting visible points on the board.
I have watched leaders make real progress on the transitions and get nowhere, because the C-suite still experienced them as a doer. Progress nobody perceives does not move a promotion decision. Both lenses have to move, and they rarely move at the same speed.
Why the strongest technical performers are the most exposed
There is a counterintuitive pattern here that senior teams consistently underestimate.
The people who struggle most at an inflection point are usually not marginal performers. They are among the strongest technical people in the building. They have been affirmed, promoted and compensated for solving problems personally. The behavior now standing in their way is the exact behavior the firm has long rewarded.
Asking that person to stop is not a small request. You are asking them to set aside the thing that built their credibility, in exchange for a kind of contribution that is slower to appear and harder to measure.
I work with an executive whose CEO thinks highly of him as does theCOO. The Chief Revenue Officer describes him as one of the most talented people he ever worked with. Yet his name was not coming up for promotions. Not debated and set aside. Not coming up at all.
He was respected. He was not considered.
That gap is where most stalled engineering executives live. The organization has reached a conclusion about them without ever articulating a reason, which leaves the leader with nothing specific to work on. Removing that fog was the first job in his engagement, and it is usually the first job.
The cost of leaving the fog in place is real. Firms lose these people. Somebody else eventually offers them the role their own firm could not decide to give them.
Four signs a leader is stalled at an inflection point
Stalls are easier to see from outside the person than from inside them. Four signals show up most often.
They have been described as almost ready for more than eighteen months. Almost ready is a holding pattern. After a year and a half it is usually a missed transition or a wrong signal rather than a timing issue.
Their team is fully occupied and their calendar is the bottleneck. Work has moved down. Decisions have not. Everything still routes through one person.
In executive settings they deliver analysis rather than a recommendation. The analysis is thorough and correct. The room wanted a point of view with a rationale behind it, and it reads the completeness as hesitation.
Their name does not come up in succession conversations, and nobody can articulate why. This is the most expensive signal because it is silent. Executive teams often do not say why someone is not ready. They simply stop discussing them.
None of these four is a performance problem in the ordinary sense. Each one is a specific, nameable gap between what the leader is doing today and what the next level requires. That specificity is what makes them workable.
What to do before the stall turns into a resignation
Once a firm can see the pattern, the work becomes fairly practical. Five steps carry most of the value.
Name the transition. Decide which of the five changes in the work this particular leader has not made. Delegation, priority setting and leading leaders are different problems with different solutions, and the label not ready covers all of them equally badly.
Isolate the variable. Be more strategic names a result. Engineers cannot work on a result. Translate it into observable behavior, such as opening the next client meeting with a recommendation, or handing a decision right to a direct report and leaving it there for a full quarter.
Give the person honest feedback. Most stalled leaders have never been told what the organization actually thinks about them. That conversation is uncomfortable, and it is the highest-return thing a manager can do.
Put a sponsor behind it. Coaching and sponsorship compound. A manager who visibly backs the leader accelerates everything, and no coach can manufacture sponsorship that does not exist.
Set a ninety-day standard. Agree in advance what progress would look like to the people whose perception matters, then check it on the date. Development work that cannot be observed cannot be assessed.Firms that do this keep leaders they would otherwise lose, and they end up with a bench from which they can promote. Firms that do not keep having the same conversation every eighteen months, usually about a different name.
If you have a leader sitting at one of these inflection points, book a call. We can pressure-test where they are and define exactly what the next role will require of them.

Comments