Mentoring Developers
Mentor engineers effectively through structured growth plans, deliberate practice, pair programming, and regular feedback conversations.
Mentoring is the practice of deliberately accelerating another engineer's growth through guidance, feedback, and challenge. Effective mentors don't give answers-they develop the judgment to find them. The best technical mentors are multipliers: their impact lives on in every engineer they've grown.
Mentor to build independence, not dependence. Ask more questions than you answer. Meet the mentee where they are, not where you wish they were. Growth requires discomfort-give stretch assignments, not busy work. Feedback is a gift; withhold it and you harm growth.
Workflow
- Establish goals and a growth planMentoring without direction is just conversation; goals create accountability and measurable progress.
- Use the Socratic method, not lecturesAnswers fed to mentees don't build the judgment to apply knowledge in new contexts.
- Use pair programming strategicallyPair programming transfers tacit knowledge (how to debug, how to read code, how to Google effectively) that documentation can't capture.
- Give specific, growth-oriented feedbackVague feedback ("good job" or "needs improvement") doesn't help growth.
- Create stretch opportunitiesGrowth happens at the edge of comfort; safe assignments produce plateaus.
Output Format
Written growth plan with 3-month goals, weekly check-in cadence, structured feedback notes, stretch assignment log, milestone celebrations.
Examples
Growth plan entry: "Goal: lead a project with 2 external dependencies by Q3. Current state: strong individual contributor, unclear on managing cross-team dependencies. Actions: shadow next cross-team project; lead standup by week 4; own the stakeholder update by week 8."Socratic pair session: mentee stuck on concurrency bug → "What are all the places this data is written?" → "What if two writes happen at the same time?" → "How would you verify that?" → light bulb moment about locksStretch assignment: "I'd like you to run the architecture review for the new notification service. I'll be there, but you drive the technical discussion."Edge Cases & Gotchas
- Mentee who wants answers, not growth: name the pattern kindly-"I could tell you, but you'll learn more by figuring it out; here's a hint to unstick you"-and set expectations about the mentoring style
- Mentee who is not growing: distinguish capability gap (needs different approach) from motivation gap (different conversation) from fit gap (career direction mismatch)
- Reverse mentoring: junior engineers often have insights about new technologies; creating two-way mentoring relationships builds organizational learning
When to Break These Rules
- In a crisis (production outage, tight deadline), shift from mentor mode to expert mode-answer directly. Return to mentoring mode when the pressure lifts and debrief the experience.
Reference Files
Lara Hogan "Resilient Management": https://resilient-management.com/Pat Kua "Talking with Tech Leads": https://leanpub.com/talking-with-tech-leadsThe Coaching Habit (Michael Bungay Stanier): https://boxofcrayons.com/the-coaching-habit-book/