When Mentoring Goes Wrong

When an opinionated senior engineer and a hesitant junior engineer clash, the real problem isn't attitude; it's two brains doing exactly what evolution designed them to do.

When Mentoring Goes Wrong

Here's something nobody tells you about expert mentors: the better they are at their job, the harder they can be to learn from.

Mark has 20 years of experience. He's seen projects fail, watched teams make the same mistakes over and over, and built up strong opinions about the right way to do things. And he's probably right, a lot of the time. The frustrating part for Harry is that "probably right" and "definitely right" aren't the same thing, and the gap between those two is exactly where the tension lives.

So what's actually going on here?

Mark's brain is working against him

When you've done something for 20 years, your brain stops consciously processing it. Neuroscientists call this automatization: expertise gets encoded so deeply that you can't easily explain why you do things the way you do. Mark doesn't just know the right answer; he feels it. And when Harry pushes back, it doesn't register as a reasonable alternative view. It registers as noise.

There's also something more personal happening. Mark's identity is built around being the expert in the room. When Harry questions his approach, even gently, Mark's brain reads it as a threat. Not to the project, but to him. Research on the default mode network shows that self-referential threats, the kind that poke at who we think we are, activate the same neural circuitry as physical danger. Mark's defensiveness isn't a character flaw. It's a biological reflex.

The result? He talks more, listens less, and doubles down.

Harry's brain is working against him too

Harry is an introvert with limited experience, and that's a rough combination in this dynamic. His ideas are probably good. But without the confidence that comes from years of battle-tested decisions, he can't project certainty. And in a room with someone like Mark, uncertainty gets eaten alive.

Here's the counterintuitive part: Harry's self-doubt might actually make him a better engineer in the long run. In Zen, this quality has a name: shoshin, or beginner's mind. The idea is that an open, questioning mind sees more possibilities than one that's already decided what's true. Shunryu Suzuki captured it simply: "In the beginner's mind there are many possibilities; in the expert's mind there are few."

Questioning assumptions, staying curious, not defaulting to habit: these are features, not bugs. But they're nearly impossible to leverage when you're being talked over.

What Mark could do

Mark should try asking one question before giving any advice: "What's your thinking here?" Not as a test, but as a real question. Research on expert blind spots shows that experienced people are often terrible at explaining their own reasoning because it's so deeply automatic. Arthur Deikman called this de-automatization: the deliberate effort to loosen habitual patterns of thought and perception. Forcing himself to listen first wouldn't just make Mark a nicer mentor. It would make him a better one.

Mark might also consider that Harry's pushback isn't insubordination. It's signal. The teams that catch problems early are the ones where junior people feel safe saying "I'm not sure about this." Psychological safety isn't soft management. It's how good engineering actually works.

What Harry could do

Harry needs a different strategy than direct confrontation, which clearly isn't working. Instead of "I think you're wrong," try "Can I walk you through my reasoning and get your feedback?" That reframes the conversation: Harry isn't challenging Mark's authority; he's inviting Mark's expertise to evaluate his thinking. A small shift in framing, but it changes everything.

Harry should also document his reasoning in writing: an email, a shared doc, a comment in the code. Writing forces clarity, and it creates a record that doesn't depend on Mark's willingness to listen in the moment.

Buddhist psychology has a useful concept here: upadana, or clinging. Mark clings to his expertise as identity. Harry clings to the idea that being right should be enough. Neither is serving them. The practice, for both, is to hold their views a little more lightly and get genuinely curious about the other person's perspective.

And yes, Harry's manager telling him to "learn how to deal with difficult people" is a cop-out. But that's a separate problem.