🤝 Mentoring & Coaching

Technical mentors need: the ability to explain complex concepts at varying levels of abstraction, giving constructive feedback without discouraging, asking Socratic questions to guide learning rather than giving answers, active listening to understand the mentee's real blockers, writing clear learning objectives and feedback in English, and facilitating career conversations including goal-setting and performance discussions. All of these require specific language skills beyond technical knowledge.

Constructive feedback structure: start with what worked well ("The test coverage is excellent here"), describe the specific issue ("I notice the function is doing three different things"), explain the impact ("this makes it harder to test and reuse"), suggest the improvement ("what if we extracted the validation into a separate function?"), and invite discussion ("what do you think?"). Avoid: "this is wrong", "you should have", or "obviously". Specific and actionable beats vague and emotional.

Socratic mentoring questions: "What have you already tried?", "What's your current understanding of why this isn't working?", "What would happen if [X]?", "Have you considered [Y]?", "Why did you choose this approach over [alternative]?", "If you were reviewing someone else's code with this issue, what would you suggest?", "What's the simplest change that could fix this?". Questions that guide the mentee to discover answers create more durable learning than giving the answer directly.

Goal-setting conversation: "What are you hoping to achieve in the next 3 months?", "What skills feel most important for your next career step?", "What's blocking you from getting to the next level?", "Let's set a SMART goal: Specific, Measurable, Achievable, Relevant, Time-bound", "By the end of this month, I'd like you to be able to [X] — does that feel achievable?" Write goals down and review them at each session to track progress.

Mentoring: sharing experience and guidance based on your own journey — "When I faced this, I found X helpful." Coaching: asking questions to unlock the coachee's own solutions — "What do you think is the right approach?" Managing: directing work and evaluating performance — "This needs to be done by Friday." Good engineering leaders blend all three. The key skill is recognising which mode is appropriate in the moment — a mentee who needs a specific technical answer doesn't need Socratic questioning right now.

Sensitive feedback approaches: use "I" statements ("I found this hard to follow") not "you" statements ("you wrote confusing code"), provide the growth framing ("this is the typical challenge at this level — here's how to advance"), make it concrete ("this specific function" not "your code in general"), and follow up with support ("let me know when you've made the changes and we'll review together"). Create psychological safety — developers who aren't afraid of feedback improve faster.

Active listening signals: "I hear that the main challenge is X", "Let me make sure I understand — you're saying [paraphrase]?", "That sounds really frustrating — what happened specifically?", "What would make the most difference right now?", "I notice you hesitated when you mentioned [X] — what's your concern there?", "You've mentioned [Y] twice now — is that the core issue?". Reflect back what you hear before offering advice — often the mentee needs to feel heard before they can receive guidance.

1:1 structure: (1) Check-in — "How are you doing this week?" (2-3 min); (2) Updates on previous goals/action items (5 min); (3) Main topic — let the mentee choose (15-20 min); (4) Feedback on recent work (5-10 min); (5) Set next actions (5 min). Key principle: the mentee should own the agenda after the first few sessions. If you're doing all the talking, you're lecturing, not mentoring.

Career development vocabulary: growth areas (skills to develop), blind spots (weaknesses you don't see), stretch assignment (challenging task beyond current skill), sponsorship (actively advocating for someone's advancement), visibility (being noticed by decision-makers), impact (measurable contribution to the team/company), leverage (applying your skills where they create most value), trajectory (career direction and pace). These appear in performance reviews, promotion discussions, and development plans.

Handling resistance: "I want to make sure my feedback is landing helpfully — how does this feel?", "I notice you seem hesitant about this suggestion — what's your concern?", "I'm not saying you're wrong — I'm sharing a perspective. You might know something I don't", "Let's try both approaches and compare the outcome", "What would it take for you to feel confident about [X]?" Sometimes resistance signals unclear feedback, sometimes the mentee needs to arrive at the conclusion themselves. Never force — guide.