Mentoring Without the Ego

The worst mentoring looks like this: a senior engineer explains things at length, shares war stories, gives prescriptive advice, and walks away feeling like they've made a difference. The mentee smiles, nods, and learns almost nothing — because the session was about the mentor's knowledge, not the mentee's growth.

Good mentoring is the opposite. It's quiet. It's mostly listening. It's asking questions that help the other person think rather than giving answers that show off what you know. It's uncomfortable, because the mentor has to resist their strongest instinct: solving the problem themselves.

What Mentoring Actually Is

Mentoring is helping someone develop the judgment, skills, and confidence to navigate challenges independently. It's not tutoring (teaching specific skills), not managing (directing work), and not coaching (goal-oriented performance improvement — though it overlaps).

The goal isn't to create a copy of yourself. It's to help someone become a better version of themselves — which might look very different from you.

The Ego Traps

The Expert Trap

You know the answer. It's obvious to you. The temptation is to give it immediately. "Here's what you should do." "When I faced this, I did X."

This feels helpful. It isn't. The mentee gets a fish but doesn't learn to fish. And the answer might not even fit their specific situation — your experience isn't universal, even if it feels like it should be.

Instead: Ask what they've considered. "What approaches have you thought about?" "What are the tradeoffs you see?" Often, they're closer to a good answer than they realize, and a guiding question gets them there with much better retention than a handed-down answer.

The Hero Trap

The mentee has a problem. You solve it for them. They're grateful. You feel important. This pattern repeats. Over months, the mentee brings every problem to you and never develops problem-solving independence.

You've created a dependency, not a mentee.

Instead: Help them solve it themselves. "Where would you start debugging this?" "What would you Google?" "Who else on the team might have context?" The goal is to model the problem-solving process, not to demonstrate your problem-solving prowess.

The Story Trap

Mentoring sessions that are mostly the mentor telling stories about their career. "When I was at Company X..." "Back when I was learning..." "I once had a situation where..."

Stories have their place. But if you're spending 70% of the session talking, you're lecturing, not mentoring. The session should center the mentee's questions, challenges, and growth — not your history.

Instead: Limit yourself to one relevant story per session, and only when it directly addresses something the mentee raised. Ask first: "Would it help to hear how I approached a similar situation?"

What Good Mentoring Looks Like

Listen More Than You Talk

The most effective thing a mentor does is create space for the mentee to think out loud. Many problems become clearer when spoken aloud to an attentive listener. You don't need to provide insight — you need to provide attention.

A useful meeting structure: the mentee sets the agenda, talks through what they're working on and where they're stuck, and the mentor asks questions that help clarify the thinking. The mentor's job is to be a thinking partner, not an oracle.

Ask Questions That Develop Judgment

Good mentor questions aren't trivia. They're judgment questions.

• "What's the most important thing to get right here?"

• "What would happen if you did nothing?"

• "What's the worst thing that could go wrong with this approach?"

• "Who would be affected by this decision?"

• "What would you advise someone else to do in this situation?"

These questions develop the mentee's ability to think through problems — which is the skill that distinguishes senior engineers from junior ones. Technical knowledge can be learned from documentation. Judgment is learned through practice and reflection.

Give Feedback Directly and Kindly

When feedback is needed, be direct. Not harsh — direct. "I noticed you didn't ask clarifying questions in the meeting, and the team built something different from what was requested. What happened?" is direct and curious. "You should have asked more questions" is direct and prescriptive. "Maybe consider asking questions next time?" is indirect and unhelpful.

The combination of directness and genuine care is what makes feedback land. The mentee knows you're honest (because you're direct) and that you're invested in their growth (because you care).

Let Them Make Mistakes

The hardest part of mentoring: watching someone head toward a mistake you could prevent. A design choice you know will cause problems. A project approach that will hit a dead end.

If the mistake is small and recoverable, let it happen. The learning from experiencing a mistake is deeper than the learning from being told about it. Debrief afterward: "What happened? What would you do differently?"

If the mistake is large and costly, intervene — but frame it as a question first. "I see a potential issue with X. Have you considered what happens when Y?" Give them the chance to catch it themselves.

Be Honest About What You Don't Know

"I don't know" is one of the most powerful things a mentor can say. It normalizes not knowing. It shows that competence isn't about having all the answers — it's about knowing how to find them.

"I don't know, but here's how I'd figure it out" teaches more than any answer would.

Structuring a Mentoring Relationship

Set expectations early. How often do you meet? Who sets the agenda? What's in scope? Some mentoring relationships focus on career growth. Others focus on technical skills. Others focus on navigating organizational dynamics. Clarity prevents drift.

Meet regularly. Every 1-2 weeks works for most relationships. Less frequent than that and momentum dies. More frequent and it becomes a management relationship.

Let the mentee drive. They set the agenda. They bring the questions. If you're always deciding what to discuss, you're mentoring your idea of their development, not their actual development.

Check in on the relationship. Every few months, ask: "Is this working for you? Are we focusing on the right things? Is there something I could do differently?" This feedback loop keeps the relationship useful.

Key Takeaway

Good mentoring is about the mentee's growth, not the mentor's expertise. Listen more than you talk. Ask questions that develop judgment rather than giving answers that demonstrate knowledge. Let small mistakes happen for the learning they provide. Be direct with feedback and honest about what you don't know. Resist the expert trap, the hero trap, and the story trap. The goal is to make yourself unnecessary — and that's the most valuable thing you can do.