Two decades in mechanical design, most of them spent as an external engineer moving between the design floors of large manufacturers in Japan, has put me in an unusual position when it comes to mentoring. I don’t have the standing of a permanent department manager, and I’m often on a project for a year or two before moving to the next one, so junior engineers don’t automatically see me as someone whose guidance carries institutional weight. And yet some of my most meaningful working relationships have been with junior designers I mentored informally during those short windows. I’ve come to believe that mentoring isn’t a title-holder’s obligation, it’s a skill and a responsibility that anyone with more scar tissue than the person next to them can and should take on.
The Mentor I Didn’t Have
When I started out, I was handed drawings, told to revise them, and largely left to figure out why certain design choices had been made through trial and error. Nobody sat me down and explained why a particular fillet radius mattered on a cast bracket, I found out because a part I designed cracked at a sharp internal corner during a drop test, and a much more senior engineer walked over, looked at the failure, and simply said “stress concentration, you’ll remember this one.” He was right, I did remember it, but I also remember thinking afterward how much cheaper that lesson would have been if someone had explained it to me on paper before it happened on a physical part.
That memory has shaped how I mentor. I try to front-load the reasoning, not just the rule. Telling a junior engineer “use a minimum 3mm fillet radius here” teaches them a number. Telling them why — walking through the stress concentration factor, showing them a photo of a failed part, explaining the specific loading condition that made it matter on this particular bracket — teaches them a way of thinking that transfers to problems I haven’t personally warned them about yet.
Why External Engineers Are Often Better Positioned to Mentor
It might seem counterintuitive that someone who isn’t a permanent employee, and who won’t be around in eighteen months, ends up mentoring the junior staff who will be. But I’ve found the opposite is often true, and there’s a real reason for it. Permanent staff engineers are frequently embedded in the same reporting structure as the junior engineer, which means feedback carries performance-review weight and juniors are naturally guarded about admitting confusion. As an outside contractor, I’m not writing anyone’s review. A junior engineer on a project I worked on years ago told me directly that he asked me more “stupid questions” than he asked his own team lead, because there was no career risk in looking uncertain in front of me.
I don’t say this to diminish the role of internal mentors, who obviously matter enormously and are around for the long haul in a way I’m not. But if you’re an external or contract engineer reading this and wondering whether mentoring is even your place, I’d argue the temporary, lower-stakes nature of the relationship can actually make you a safer person for a junior engineer to learn from, precisely because you’re outside the hierarchy they have to perform in front of every day.
Teaching Judgment, Not Just Procedure
The hardest thing to mentor is judgment — knowing when to follow the standard and when the standard doesn’t quite fit the situation in front of you. On a sheet metal enclosure project, a junior engineer I was working with followed the company’s standard bend allowance formula precisely, and the parts came back slightly out of spec on a tight interior dimension. He’d done everything “correctly” by the book. What he hadn’t yet learned was that the standard formula was calibrated for a different material thickness range than the one he was using, and an experienced designer would have caught that mismatch before it ever reached the shop floor.
Rather than just correcting the number, I walked him through how the bend allowance formula is actually derived, so he could see for himself where its assumptions broke down. That’s slower than just telling someone the right answer, and early in my mentoring efforts I underestimated how much slower it is. But procedural knowledge without the underlying judgment just produces engineers who will make a different, unpredictable version of the same mistake the next time the standard doesn’t fit.
The Cost of Mentoring, and Why It’s Worth Paying Anyway
I won’t pretend mentoring is free. Every hour I spend explaining the reasoning behind a design decision to a junior engineer is an hour I’m not spending advancing my own deliverables, and on a contract basis, my output is often literally what I’m being measured against. I’ve had project managers, not maliciously, but genuinely focused on schedule, ask me why a task that should have taken two hours took four, and the honest answer was that I spent two of those hours mentoring instead of just doing the work myself.
I’ve made peace with that trade-off because of a longer view: nearly every skilled junior engineer I’ve mentored has, at some later point, become someone who made my own work easier, whether by catching an error in my design during a review, or by handling a piece of a project competently enough that I didn’t have to double-check it. Mentoring is an investment with a delayed and diffuse return, but in an industry with as much institutional memory loss as mechanical design has when engineers rotate between companies and contracts, that return is real.
What Good Mentoring Actually Looks Like Day to Day
Good mentoring, in my experience, is less about formal sit-down sessions and more about how you handle the small moments. When a junior engineer brings you a drawing for review, resist the urge to just mark up the corrections yourself. Ask them to explain their reasoning first. Half the time they’ll catch their own error mid-explanation, which teaches them far more durably than if you’d simply pointed it out. The other half of the time, their reasoning reveals a gap in understanding that a simple correction would have papered over rather than fixed.
| Mentoring Behavior | What It Teaches | What It Costs |
|---|---|---|
| Correcting the drawing yourself | Nothing lasting | Fast, but repeats forever |
| Asking “walk me through your reasoning” | Self-diagnosis skill | A few extra minutes per review |
| Sharing a past failure of your own | Humility, pattern recognition | Requires vulnerability |
| Explaining the “why” behind a standard | Transferable judgment | Slower in the moment |
Admitting Your Own Mistakes on Purpose
The single most effective mentoring tool I’ve found isn’t a technique at all, it’s simply telling junior engineers about my own failures, in specific detail, rather than presenting myself as someone who has always gotten it right. On a hydraulic manifold design early in my career, I specified a port thread that was technically correct per the standard but incompatible with a fitting the procurement team had already sourced in bulk for a related project, and the resulting mismatch cost a week of schedule and an uncomfortable meeting. I tell that story to junior engineers not because it’s flattering, but because it illustrates a category of mistake — failing to check adjacent systems, not just your own component — that no textbook really teaches well.
What We Owe the Next Generation
I don’t think senior designers owe junior engineers perfection, or even constant availability. What I think we owe them is honesty about how we actually arrived at our judgment, including the expensive lessons, and a genuine effort to make sure the next generation doesn’t have to relearn every hard lesson the same painful way we did. The industry loses too much knowledge every time an experienced engineer moves on without passing anything down. Given how often I personally move between projects, I’ve made it a point of professional pride to leave that knowledge behind wherever I go, even in the relatively short windows I have with any one team.
Looking back over twenty years, the engineers I’m proudest of aren’t the ones whose drawings I corrected the most. They’re the ones who eventually stopped needing me to check their work at all, who developed their own instinct for where a design might fail before it ever reached the shop floor. That’s the actual measure of whether mentoring worked, and it’s a slower, quieter reward than finishing a project on schedule, but it’s the one that has stayed with me longest after the projects themselves faded from memory.
コメント