Aaron Moncur is the founder of Pipeline Design and Engineering and host of the Being an Engineer Podcast - now with over 350 episodes across six years. He has spent that time asking engineers at every career stage to articulate the real craft of their work: what they've built, where they've failed, and what they've had to learn outside the classroom. This episode is different. Brad Hirayama flips the mic and pushes Aaron to distill the five most consistent patterns that have emerged from all of those conversations.
If your technical skills are good enough - 80th percentile - and your soft skills are in the top 5%, there's almost no limit to how far you can go in your career.
In this episode:
Why technical proficiency is the entry ticket into engineering and not the determining factor in how far you advance
The business context most engineering programs never cover, and how missing it quietly caps your trajectory inside any organization
How a slumping pair of shoulders during a Teams message exchange became a real-time lesson in what engineering leadership actually looks like on the floor
The concrete difference between a mentor, a coach, and someone you take to lunch and why each one serves a different function in career development
Why doing more than what you're paid for works like loading fuel before you light a match - the effort comes first, and the return comes back disproportionately
Bonus Content:
A Cautionary Tale: The Machine that Couldn’t Fail
S7E9 Brad & Aaron | Top 5 Takeaways After Interviewing Over 300 Engineers
Aaron Moncur is the founder of Pipeline Design and Engineering and host of the Being an Engineer Podcast, where he has spent six years and nearly 350 episodes interviewing engineers about the real craft of building things. In this episode he steps out of the host chair - joined by Brad Hirayama - and answers the question directly: what do those 350 conversations actually teach? The five lessons he names are consistent across every background and career stage. He covers why understanding the business context behind engineering decisions separates career-limited technicians from engineers who advance, how soft skills function as a ceiling-raiser that technical proficiency alone cannot replace, the practical difference between a mentor and a coach and why both matter, what doing more than what you're paid for actually looks like in practice versus simply logging more hours, and why building shared processes is the infrastructure that makes teams scalable beyond any one person's knowledge. He closes with two methods for accelerating the speed of engineering - including one that turned a half-day custom-design task into zero extra minutes by reaching into a drawer for a tape measure. For engineers who have the technical foundation and want to understand what actually determines whether they advance, this episode is a direct answer.
>If YouTube isn’t your thing, check out this episode and all of our past episodes on Apple, Spotify, and all the rest.
Great engineering doesn’t always lead to successful products.
In this upcoming PDX Webinar, Arne Lang-Ree (Chief Design Officer & Cofounder at Spanner) will show how engineering teams can turn product-market fit into a practical design objective.
The session covers frameworks for translating user needs into engineering constraints and evaluating product success throughout development.
Join us on April 23 at 9:00 AM PT / 9:00 AM MST / 12:00 PM EST.
The engineer with the sharpest technical skills in the room isn't always the one who advances
Aaron Moncur has taught engineering fundamentals to middle and high school students through a volunteer CAD program called CAD Club for years. At the start of every term, he shows them a single slide about technical skills versus soft skills. The framing is direct:
If you're the most skilled engineer in the room when it comes to technical skills, but your communication, your soft skills are not that great - there is a bar beyond which you really can't progress as an engineer in any organization.
An engineer at the 80th percentile technically who is genuinely capable, not the sharpest in the room, but operating in the top 5% for communication and soft skills faces almost no career ceiling. The technical floor is a prerequisite. What happens above that floor is determined by something else entirely.
Aaron tested this dynamic in practice at Pipeline. A new project lead with real excitement about his role came to the Director of Engineering with an idea to improve a team process. The director - still getting up to speed on Pipeline's faster, lower-bureaucracy culture - responded by asking for a formal proposal. Aaron watched the exchange happen and caught the moment it landed:
I remember being in the room with this project lead and watching him receive that feedback from our director... I remember seeing this project lead's shoulders just slump. Like he was so excited about this idea he'd had.
He could have left it alone. Instead, he stepped in, not to escalate, but to acknowledge what he saw:
I approached this project lead and said: 'Hey, I noticed that you looked a little disappointed by the response that you got. Let's talk about that. How are things going? How are you feeling right now?
The conversation that followed involved both the project lead and the director. No formal proposal was written. The idea got evaluated and implemented. What could have ended in disengagement ended with momentum. That's what the soft skill looks like in practice. It’s not a personality trait, but an active intervention that keeps the work moving.
A Cautionary Tale: The Machine that Couldn't Fail
The patient's prescription called for 200 rads. The Therac-25 delivered somewhere between 15,000 and 20,000 - no error displayed, no alarm triggered, and an operator who had no idea anything had gone wrong. AECL passed every structured safety verification they ran, because the fatal failure mode only existed outside the space those tests were designed to find. This week's article traces the design review decision, made before a single line of code was written, that made that possible, and what it means for every engineering team currently replacing hardware safety layers with software.
To read the full article, visit the full article on The Wave.
When Your Machine Shop Says No
Last year, a customer couldn't find a shop willing to make their part. Difficult material, tight tolerances, small quantity.
We tested our internal supply chain. Made the parts ourselves. Sent them as a surprise.
They worked perfectly. That customer has ordered hundreds more since.
Now available: custom machined parts with Pipeline engineering oversight, pricing that outperforms domestic shops, and the same supply chain we trust for our own work.
Want to learn more? Contact us at the link below: