One of the most common confusions in engineering management is the difference between mentoring and managing. They overlap but are not the same. EMs who only manage produce reliable execution but limited growth. EMs who only mentor produce growing engineers but inconsistent delivery. The best blend both, and know which mode each report needs at each moment.
The two modes
Managing
- Direction: telling someone what to do
- Accountability: setting expectations and holding to them
- Coordination: aligning the team
- Feedback: assessing performance against expectations
- Authority: making decisions about scope, headcount, comp
Mentoring
- Coaching: helping someone find their own answer
- Investment: long-term development of capabilities
- Curiosity: asking questions rather than giving answers
- Modeling: demonstrating how to do things well
- Sponsoring: opening doors and creating opportunities
The core distinction
Managing is about what. Mentoring is about how and why. Managing produces this quarter’s outcomes. Mentoring produces this engineer’s long-term growth.
When to manage
- Crisis or urgency — direction beats coaching
- New employee unfamiliar with norms — explicit guidance
- Performance gaps requiring clear expectations — managing
- Resource decisions — managers decide
When to mentor
- Growth-oriented conversations
- When a report is technically capable but stuck on judgment
- When learning is more valuable than the immediate output
- When the report wants to develop autonomy
The Socratic move
Instead of “Do X this way,” ask “What approach are you considering? What are the tradeoffs? What did you try? What did you learn?”
This takes longer in the moment. It produces an engineer who can solve the next problem without you. The investment pays off across years.
Common failure modes
Over-managing
You give answers when the engineer needed to find them. Over time, the team becomes dependent on you. Bottlenecks emerge. Engineers do not grow.
Over-mentoring
You ask “what do you think?” when the answer needed to be “we need to ship this Friday, and the answer is X.” Engineers feel ungrounded; deliverables slip.
Calibrate to the moment.
Mentoring without managing (peer mentorship)
Senior ICs mentor junior ICs without authority. The dynamic:
- No power asymmetry — the mentee can disagree freely
- Lower stakes — mentee’s career does not depend on the relationship
- Often more honest than mentor-as-manager
Encourage peer mentorship on your team. It scales mentorship beyond what a manager can provide alone.
Sponsoring
Sponsoring is going beyond mentoring — actively opening doors. Examples:
- Recommending someone for a high-visibility project
- Connecting them with senior leaders
- Putting them forward for promotion
- Speaking up on their behalf in calibration
Sponsoring is more impactful than mentoring for career trajectory. Many strong managers are good mentors but weak sponsors.
The mentor as a manager: explicit role-shifting
Strong EMs explicitly signal their mode:
- “As your manager, I am asking you to ship X by Friday.”
- “As your mentor, I am curious — what did you learn from the last project?”
The role shift makes both sides clearer. The report knows when they are getting direction and when they are getting coaching.
The interview question
“How do you balance mentoring and managing?”
Strong answers cite specific situations: “When report Y needed to ship under deadline, I gave clear direction. When the deadline relaxed, I shifted to coaching them on the design they actually wanted to learn.”
Frequently Asked Questions
Can I be a mentor and not a manager?
Yes — staff/principal ICs are often great mentors. Many engineers prefer this role.
Can I be a manager without mentoring?
You can manage execution, but you will not develop your team. Strong EMs invest in mentoring deliberately.
What if my report does not want mentoring?
Some prefer pure execution relationships. Respect that. Provide direction; back off coaching unless asked.