Technical Career Stages - second-hand-tigers/badocter-career-learnings GitHub Wiki

Learning Hub › Career Learnings Directory › Dr. Docter's Career Learnings › The Renaissance Engineer

Technical Career Stages

Many of the companies you will work for are multi-generational enterprises, some like ExxonMobil stretching back more than 140 years (tracing back to Standard Oil, founded in 1870). That kind of longevity is only possible when each generation is mentored by the one before it and mentors the one after it. The later stages of an engineering career are less about elite technical skill than most engineers expect; they are about developing others and institutionalizing practices that position the next generation for success. That mandate relies on non-technical skills that take years to build, and the four-stage model below shows what each stage expects of you.

When I was working on my co-op jobs, and even into my first few years at ExxonMobil, my perception of an engineer's career was largely focused on building technical expertise with the goal of performing as an elite-level individual contributor. This perception was reinforced by the technical experts portrayed in film and television. For example, in the original Star Trek, mentoring was almost never shown on screen; the technical experts simply knew everything, and the junior crew were little more than red-shirts in the plot. Growing competency to develop and lead others did not cross my mind until I started observing that it was a large part of what the senior professionals ahead of me were doing, and later when career development frameworks were promoted as a part of developmental planning tools that explicitly described the stages and expectations.

The Four-Stage Model

Stage	Typical Time in Stage	Focus	Work Scope
1. Apprentice	~2 yrs	Learning the Business	Training in tools, skills, work processes, and job-specific theory. Tasks within a project, under the direction of a Stage 2-3 colleague.
2. Colleague	~8 yrs	Implementing	Competent at standard application and troubleshooting in your own discipline. Leading and contributing to standard, predefined-scope projects. Onboarding and training Stage 1.
3. Expert	~10 yrs	Leadership / Mentoring	Defining projects and initiatives (scope, benefit, cost, time). Advanced application and troubleshooting. Leading new-technology pilots and commercialization. Mentoring Stage 1-2 through coaching, 1-on-1s, and shadowing/delegating. Owning Individual Development Plans of others.
4. Sponsor	Remainder of career (often blended with Stage 3)	Strategic Vision, Regional/Global Influence	Developing and promoting the 1- and 5-year strategic plan. Driving emerging innovations to commercialization. Promoting regional/global development programs, discipline health, and initiatives that institutionalize knowledge across geography and generations.

Stages describe scope and influence, not job titles. My own title read "Real Time Optimization Engineer" for most of two decades while the scope underneath it grew from a modeling and support apprentice (Stage 1) to Global Network Action Team Lead (Stage 3); see Career Timeline.

Most senior technical staff will have final roles that are a mix of Stage 3 and Stage 4, particularly if they are involved in the day-to-day in any way, including any hands-on work and mentoring. To become fully Stage 4 requires letting go of the day-to-day. Some technical leadership roles are fully Stage 4, but they resemble management-path roles more than technical-path roles (see ExxonMobil's dual-ladder structure on Who is Dr. Docter?). For me, having some hands-on work as part of my role was a career satisfaction requirement. Many other senior practitioners were highly energized by fully Stage 4 roles — the decision is not one-size-fits-all; it requires self-examination and open discussions with your supervisor and mentors.

At the end of my career, I'd say I was a Stage 3.5 overall: ~25% of my role was hands-on, but that 25% was Stage 3-level work items that all had clear ties to supporting Stage 4 objectives. I had contemporaries who were pure Stage 4 but were 0% hands-on, and we collaborated, leveraging each other's perspectives and strengths. The ways in which we were different made us more effective as a whole (see Infinite Diversity in Infinite Combinations).

The jump from Colleague to Expert is where the role's responsibilities with a significant non-technical component start to dominate — and where a lot of very technically strong engineers get stuck without realizing it (see below).

Being a Successful Expert Isn't All About the Technical Skill

Reaching Stage 3 on technical merit alone is not the same as succeeding at Stage 3. It's possible to be highly experienced and technically proficient while still failing at the actual job of an Expert: not caring about the team, not owning mentoring or succession planning — or actively blocking it — not advocating for the technology, and blaming others for not understanding the work. Every senior engineer has a responsibility to be ethical, develop the next generation, and be an ambassador for the technology, not just a repository of it.

There's a well-known fictional illustration of exactly this failure mode — see The Failed Expert for the full breakdown.
For a real-life version of this, see Teammates or Competitors?, where a feedback system that weighted behavior more heavily at each promotion finally made the lesson stick for this technically strong lone wolf.
Since technical skill alone won't carry you through Stage 3, group work in school is worth taking seriously long before you get there — see Getting Graded on Group Projects is Fair.

Blind Spots and Plateaus

You will plateau in every assignment eventually — you'll have learned what that assignment requires and practiced it enough that it becomes routine. You may even start thinking of yourself as the expert; however, reaching full competence in one assignment does not mean you've learned what's required for any assignment.

"What you see is all there is" (WYSIATI, Daniel Kahneman's term from Thinking, Fast and Slow) is the trap waiting at that point. A plateau should trigger a change in course, but plateaus and the need for a course change are often invisible to the person actually on the plateau. This is why external input — a mentor, a supervisor, an honest peer — matters more as you advance, not less.

For a real example, see The Blind Spot I Didn't Know I Had.

Relocations as a Plateau-Breaker

Changing location is one of the more effective ways to break out of a plateau: it resets other people's first impressions and expectations of you, grows your network, and tags you as someone with regional/global reach rather than a single-site reputation. There's a fictional character who illustrates the "resetting first impressions" effect particularly well — see Dread Pirate Roberts Succession Plan. My own move to Antwerp is the real-life version: see Landing in Antwerp Without an Answer.

Central Engineering vs. Manufacturing Assignments

Both environments develop you, but along different lines:

Central Engineering	Manufacturing Sites
Emerging technology more visible	Business challenges more visible
More access to technology-area experts; network growth toward technical peers	More access to operations experts; network growth toward site peers
Selling technology	Buying technology
More business travel (life-balance trade-off)	Less business travel (life-balance trade-off)
Mid-level expert gets regional/global line of sight, can leverage knowledge across multiple sites earlier in career	Mid-level expert can be a big fish in a small pond, leading local site initiatives earlier in career
Operations reality arrives filtered through remote-support calls	Operations reality is staring you in the face

The Leadership, Business, Interpersonal, and Technical (LBIT) dimensions are a part of development in both environments; however, they have different focuses that are complementary. For example, at a manufacturing site, the engineer will be growing knowledge of industry-standard technologies already deployed at that site, and will be experiencing all of the business challenges in real time, some of which may be addressable with the standard tools, while other challenges may just have to be lived with — problems looking for solutions. In central engineering, an engineer will be growing knowledge of how industry-standard approaches work across many sites, and evaluating emerging technology — solutions looking for problems. The central engineer will not have direct line of sight to all of the business challenges the manufacturing engineer is seeing. Both engineers are developing Technical and Business proficiency in this example, but they are not the same. When the two meet, the results can be substantial — see From "Sliced Bread" to Patent.

Rather than picking one track, consider taking assignments in both over a career: it broadens your general understanding, helps you connect emerging technology to real business needs, and — not a small thing — both sides end up claiming you as one of their own.

Stage 3 and 4, Applied as a Volunteer

Second-Hand Tigers is a volunteer initiative I started, not an employment relationship — but the career stage model doesn't require a paycheck to apply. The majority of my effort roughly follows the Stage 3.5 pattern of my final roles at ExxonMobil.

Developing soft-skill and career-development material for university students and early-career engineers is Stage 3 Expert-level work: mentoring, scaled to a classroom instead of a direct-report team. The material is only credible because it draws on all 3.5 stages' worth of my experience — it's not something I could delegate to someone in Stage 1 or 2 to write.

Once the material is developed, I can start training someone in Stage 1-2 to apply the approaches, so we can verify and validate (V&V) that the material is complete and the methods are effective. The next phase is to train the next trainer, someone approaching Stage 3 (let's call them Stage 2.5), to lead training sessions on modules where they have demonstrated competency, positioning them to complete their transition to Stage 3 — the leader develops more leaders, and the initiative outlasts my involvement (see Dread Pirate Roberts Succession Plan).

The Stage 4 half is really about reach beyond a single location and a single discipline. The plan is to pilot the material with Lamar University Chemical Engineering first if there's enough buy-in to make that happen. The longer-term goal is promoting it to other disciplines and other universities and colleges — the same regional-to-global expansion Stage 4 describes inside a company, just applied to an education network instead. That "beyond your own discipline" piece shows up in unplanned ways, too: walking back to the car from class, I passed the Department of Leadership Studies recruiting table, struck up a conversation about what I'm building, found real interest, and traded contact information. That kind of opportunistic, cross-discipline networking — outside process control, outside engineering entirely — is exactly the Stage 4 behavior the model describes, just happening on a college campus instead of across ExxonMobil sites.

It's also worth being explicit about something the four-stage table doesn't say directly: Stage 4 effectiveness doesn't require Stage 3-level expertise in every area a Sponsor touches. The Leadership Studies conversation is a good example — I'm not the domain expert there, and I don't need to be. Where a Stage 4 effort spans ground outside your own expertise, the job is to collaborate with whoever is the Stage 3 expert in that piece and bring the organizing and leadership skill set — recruiting collaborators, carrying the vision, driving toward global reach — rather than personally covering the technical depth everywhere the effort goes.

See Who is Dr. Docter? for background on the expertise this work draws on, and Career Timeline for the full year-by-year path that led here.

Four-stage model source: "Engineering Career Development and Fostering a Mentoring Culture" (video), keynote address, American Institute of Chemical Engineers (AIChE) Southwest Student Regional Conference, 2021

License: © 2026 William Docter. This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). You may copy, redistribute, remix, and build upon this material, including for commercial purposes, provided you give appropriate credit to William Docter and indicate if changes were made. The Second-Hand Tigers logo is not covered by this license. All rights in it are reserved.