Repository navigation
Mentoring Integration with Stage Development
Learning Hub › Career Learnings Directory › Dr. Docter's Career Learnings › The Renaissance Engineer
Mentoring isn't a nice-to-have layered on top of the Technical Career Stages model — it's built into how the model actually works. Nobody just ages from Apprentice to Colleague to Expert to Sponsor. Every transition happens because a specific set of developmental experiences, assignments, and mentoring relationships positioned that person for the next stage. Corporate succession planning depends on a strong mentoring culture the same way it depends on any other kind of institutionalized knowledge — which is also why Setting and Accomplishing Development Goals treats mentoring as a Business-dimension activity, not just an Interpersonal one.
Continuous development is expected at every stage, including the top. If anything, mentoring competency matters more as your reach grows, not less — the audience for your mentoring gets larger (your own team, then other disciplines, then regional and global peers) even as day-to-day hands-on coaching often becomes a smaller fraction of your time.
Lay my own career out through a mentoring lens rather than a job-duties lens, and the same thing is true at every stop: I was receiving mentoring and providing it, simultaneously, from the very beginning. The role titles and dates are on the Career Timeline; this is the mentoring relationships layered on top of them.
| Period | Mentoring Received | Mentoring Provided |
|---|---|---|
| Student years (Cincinnati & Lehigh) | Research mentored by CG, AC, AC2, and JF; internships mentored by J.H. and S.L. | Tutoring other students in calculus and probability/statistics; Taekwondo assistant instructor |
| First Research & Engineering stint (Florham Park, NJ) | Fundamental modeling upgrade project mentored by MH, MA, and HW; RTO modeling and remote support mentored by MA and BS | Supporting sites across North America and Europe |
| Second Research & Engineering stint (Fairfax, VA) | RTO deployment and commissioning team member alongside JC, AC2, PH, and BB, across sites in North America, Europe, and Asia Pacific | First time mentoring site personnel directly on RTO (TT, VN); early R&D work on "Sliced Bread" with JD (see below); RTO basic course co-developed with JC |
| Antwerp Refinery | On-site RTO support from LB, HT, and HL; RTO deployment mentored by H.F. | Extended "Sliced Bread" to a high-value prototype with JD; regional process control network rep for Plant #1 (AC2 again); rolled out "Sliced Bread" globally the following year with JD and MW |
| Fawley Refinery | RTO projects mentored by BS and HW; DMC plant testing mentored by SW, MS, and GT | Became a Basic Controls Engineer Training instructor, mentored by AC2; trained up a new RTO engineer — GT, the same person who'd mentored me on DMC testing not long before |
| Beaumont Complex | RTO projects mentored by PH, MM, and BK; technology/R&D work with RW, RR, HW, JR, AC3, and JD; DMC modeling and tuning with BS and RR; representing the site to senior management, mentored by CW and RV; becoming Process Control Application Engineering Group Lead, mentored by DS, SK, MG, and DD | Onboarding and mentoring new engineers (AC3, KW, AW, DR); guest lecturer to Lamar University's Chemical Engineering Department; cold-eyes review team leader at other manufacturing locations; mentoring the next generation of Process Control Application Engineering Group Leads in succession planning |
A few things stand out once it's laid out this way instead of lived one year at a time:
- AC2 is a 15-year throughline, not a single mentoring event. They show up in my grad-school research, my first RTO deployment team, a regional network role, and a training assignment. That's exactly what Building Your Own Mentor Network below means by identifying who actually knows their stuff and collaborating with them across your whole career, not just for one assignment.
- Mentoring relationships aren't fixed roles. GT mentored me on DMC plant testing at Fawley; not long after, GT is the new RTO engineer I trained up. The direction can reverse as both people's careers move.
- The Lamar guest lecture shows up on this table years before Second-Hand Tigers existed as an idea. The seed for the volunteer work described in Technical Career Stages was planted during the Beaumont years, not invented at retirement.
The same four stages from Technical Career Stages apply here — this page isn't reprinting that table, just pointing out what it means for mentoring specifically. Stage 3 and beyond is more about people development and driving strategic vision than it is about being the best individual technical contributor in the room. Some assignments exist specifically to build competency in that shift — First Line Supervisor, a Unit Engineering Lead role, Principal Engineer. And even when you return to a pure subject-matter-expert role after one of those assignments, the responsibilities skew further toward people development and strategic influence than they did the first time around, not back to where they started.
My own Stage 3+ path (see Who is Dr. Docter? and the Career Timeline for the exact dates) moved through Site RTO Lead, to Process Control Application Engineering Group Lead (a First Line Supervisor role, plus Utilities Engineering Lead), back to Site RTO Lead with an expanded fleet, and then Principal Process Control Engineer — bouncing between the technical and management ladders rather than picking one and staying on it. Each move changed who I was mentoring, how many people, and how directly involved I was with them day to day.
This is the case study I come back to most often when I talk about what a mentoring relationship actually looks like in practice, because it isn't a straight line and it isn't one-directional.
JD mentored me on a technology I'll just call "Sliced Bread" during my Central Engineering assignment at ExxonMobil Research & Engineering. At the time, JD was struggling to get any real interest from business owners — the value delivery potential wasn't clear or quantified, and I was a new engineer assigned to work on the tool's code and testing with no clear end-user need or use case in sight. On paper, that's a project going nowhere.
Then I took a manufacturing assignment at Antwerp. The end-user need that had been invisible from Central Engineering became obvious from the plant floor, and other mentors on-site helped me work through the process and actually quantify the potential business value. That put me in a position to become the site champion for a pilot — with access to local resources to implement it, and still with access to JD for the technical depth. We presented the pilot's results together to the technical community and management, and that joint presentation is what got technical leadership to push for a global rollout.
JD and I kept collaborating for years after that: mentoring the rest of the global community on the technology, and refining both the technology itself and how it fit into everyday work processes.
The mentoring relationship didn't end when the pilot succeeded, and it didn't run one direction. JD brought the technical depth and years of context; I brought the manufacturing-side visibility JD didn't have access to from Central Engineering. Mentoring relationships benefit the mentor as much as the mentee — this is the clearest example from my own career of why that's true, not just a nice sentiment.
The version above is the mentoring angle, condensed. The fuller story — including the crisis that actually created the urgency, and how the technology eventually became a named, issued patent — is its own page: From "Sliced Bread" to Patent.
Pay it forward. Others will invest in you if you invest in others, and it's never too early to start — high school and college students are entirely capable of tutoring other students in academics, extracurriculars, and outreach. Mentoring is a competency, and like any competency, it builds with practice, not with waiting until you feel qualified.
Early in your career, mentors are often assigned by management — they're held accountable for onboarding you as a new employee, the way J.H. and S.L. were for me at Quantum Chemical. As your career progresses, that stops happening automatically (see Setting and Accomplishing Development Goals for the same point in the development-planning context) — it becomes your job to identify who actually knows their stuff, build a real relationship, and collaborate with them across your career, not just for the length of one assignment. AC2, above, is what that looks like when it works.
You can't teach yourself something you don't know you don't know — which means where you physically and socially locate yourself matters more than it seems like it should. Sitting alone in a closed office makes it hard to leverage the more experienced people around you, and it works against you as a mentor too: your less-experienced colleagues can suffer from the same "out of sight, out of mind" problem in reverse. If you're actually present when something interesting comes up, you get included in it — mentoring opportunities in both directions tend to happen in hallways and at desks, not in calendar invites.
I'm an introvert by type (see Personality & Working Style on the bio page) — which surprises most people who've only seen me give this lecture. I'll sometimes poll a class on whether they think I'm an introvert or an extravert before I tell them, and most guess extravert, purely from watching how much energy I put into delivering the material. Then I break it to them: I'm genuinely an introvert, and the poll result is itself the point. Introverts have to consciously balance their preference for working alone against the reality that stakeholder communication and networking are just as critical to their career as they are for anyone else's — while still protecting the downtime that actually recharges them. This isn't advice that came naturally to me. It's advice I've had to apply deliberately, and the full "Sliced Bread" story is a direct product of having done so.
Related: The Renaissance Engineer · Technical Career Stages · Setting and Accomplishing Development Goals · From "Sliced Bread" to Patent · Dread Pirate Roberts Succession Plan · Communication & Marketing · Career Timeline · Teammates or Competitors? · Stress Management & Resilience
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.