How to Give and Receive Technical Mentorship in English

Mentorship is one of the most valuable relationships in a developer’s career — both giving and receiving it. But the English of mentorship is subtle. It sits at the intersection of technical language, coaching vocabulary, and professional empathy. Whether you are a senior engineer supporting a junior colleague or a developer seeking guidance from a mentor, knowing how to have these conversations in English clearly and respectfully makes them far more effective.

---

Key Vocabulary

Mentor — an experienced person who provides long-term guidance and support to a less experienced person, often in an informal relationship. “My mentor helped me navigate the transition from individual contributor to tech lead.”

Mentee — the person receiving mentorship. “I’m currently mentoring two mentees — they’re both junior engineers who joined in January.”

Coaching — a style of support focused on asking questions and helping someone discover answers, rather than providing them directly. Different from mentoring, which may include more direct advice. “Instead of telling you what to do, I want to coach you through the decision — what options do you see?”

Growth area — a professional or technical skill someone is working to develop. A neutral, constructive term. “One of my growth areas is system design — I’m actively working on it by reviewing architecture docs and doing mock interviews.”

Stretch assignment — a task or project that is intentionally beyond someone’s current comfort zone, designed to accelerate learning. “Taking on that incident response was a stretch assignment — it was stressful, but you grew a lot.”

Accountability partner — someone who helps you follow through on goals by checking in and asking how you are progressing. “We agreed to be accountability partners — we meet biweekly to review our learning goals.”

Sounding board — a person you use to test ideas, think out loud, or get an early reaction before committing to something. “I’d like to use this session as a sounding board — I’m thinking through a career decision and want your perspective.”

---

Phrases for Starting a Mentorship Relationship

The first conversation sets the tone. These phrases help establish a productive relationship:

• “I’d love to learn from your experience — would you be open to meeting monthly?”
• “I’m not sure exactly what I need yet, but I know I want to grow in the direction of X.”
• “How do you prefer to structure our sessions? I’m happy to follow your lead.”
• “What would be most useful for you to know about where I am in my career right now?”
• “I want to make the most of your time — I’ll always come prepared with specific questions.”

---

Phrases for the Mentor Role

When you are the mentor, your language should guide without prescribing. Ask more than you tell:

• “What have you already tried? I want to understand your thinking before I share mine.”
• “What’s your instinct here? Let’s start there.”
• “I faced something similar early in my career — would it be helpful if I shared what I did?”
• “I’m going to push back on that assumption — what evidence do you have for it?”
• “You’ve made real progress since we last spoke. I want to acknowledge that.”
• “Here’s a stretch assignment I’d like to suggest — I think it will challenge you in exactly the right way.”

---

Phrases for the Mentee Role

When you are receiving mentorship, being specific and engaged is what makes sessions valuable:

• “Since our last session, I’ve been working on X — here’s where I got stuck.”
• “I want to be specific about what I need today — I’m trying to decide between A and B.”
• “Can I use you as a sounding board? I want to think through this decision out loud.”
• “I’ve been reflecting on the feedback you gave me last time — I want to share what I’ve done with it.”
• “I’m not sure I understood the point you made about X — could you say more?”

---

Phrases for Giving Feedback Constructively

Feedback is central to mentorship. The language you choose determines whether it lands well:

• “I want to give you some honest feedback — is now a good time?”
• “I noticed something in how you handled the standup today — can I share an observation?”
• “The way you communicated that decision was effective. Here’s specifically what worked.”
• “I want to be direct with you because I think it will help: the technical explanation you gave was too abstract for the audience.”
• “This is meant as a positive challenge — I think you’re capable of more than you’re currently taking on.”

---

Phrases to Avoid

Avoid	Why	Try instead
”You should just do X.”	Removes agency from the mentee	”What do you think about trying X?"
"That’s a simple problem.”	Dismissive	”This is more common than you’d think — here’s how I’d approach it."
"When I was your age…”	Condescending	”Earlier in my career, I faced something similar…"
"I don’t have time for this.”	Damages trust	”I’m short on time today — can we do a focused 15-minute session?"
"You should already know this.”	Shuts down learning	”This is something a lot of people find tricky — let’s work through it.”

---

Quick Reference

Situation	Phrase
Starting a relationship	”Would you be open to meeting monthly?”
Using coaching technique	”What’s your instinct here?”
Asking to use as sounding board	”Can I think through this decision out loud with you?”
Giving positive feedback	”Here’s specifically what worked.”
Giving challenging feedback	”I want to be direct because I think it will help.”
Acknowledging progress	”You’ve made real progress since we last spoke.”

The best mentorship conversations are honest, specific, and two-directional. The vocabulary in this guide helps you create those conversations — whether you are the one teaching or the one learning.

Navigating Nuances: Refining Your Approach with Precise Language

The core of effective technical mentorship isn’t just about sharing knowledge; it’s about fostering a supportive environment where mentees feel empowered to learn and grow. Often, this involves communicating clearly and precisely – something that can be particularly challenging for non-native English speakers navigating the nuances of professional discourse. It’s not simply about translating your ideas into English; it’s about adopting the vocabulary and phrasing used by experienced developers in collaborative settings. Let’s consider some common scenarios where precise language makes a significant difference.

For example, during a code review, a mentor might offer feedback beyond a simple “This needs fixing.” Instead, they could say, “I noticed this section isn’t adhering to our team’s style guide regarding variable naming conventions – specifically the camelCase format. Could you explore refactoring it to align with that?” This phrasing clearly identifies why the change is needed and directs the mentee towards a specific solution without immediately implying failure or inadequacy. Similarly, in Slack conversations, instead of saying “This isn’t working,” a mentor could ask, “Can you describe the steps leading up to this error? Knowing your process will help me understand where things might be going wrong.” This encourages active problem-solving and detailed explanation, crucial for learning.

Furthermore, when discussing progress or seeking guidance, phrasing is key. A mentee hesitant to admit they’re struggling might say, “I’m having a little trouble with this feature.” A mentor could respond with, “Let’s break it down. What specifically are you finding difficult? Are there any parts of the requirements that aren’t clear?” This shifts the focus from vague discomfort to actionable questions and demonstrates a willingness to collaboratively troubleshoot. It avoids judgmental language and fosters a safe space for vulnerability. Crucially, learning how to frame requests effectively – rather than demanding assistance – is a core skill in mentorship relationships.

Finally, when describing changes in a pull request, avoid simply stating “Fixed bug.” Instead, detail what was fixed: “Implemented fix for issue #1234, which prevented the application from crashing under specific user input conditions. This involved refactoring the error handling logic within the process_request function and adding a more robust validation check.” This level of specificity provides context, allows reviewers to easily understand the impact of the change, and demonstrates a thorough understanding of the underlying problem.

# Example: Using Git for commit message formatting (demonstrates precise language)
git commit -m "Refactor: Improve error handling in process_request function"

By consciously incorporating these refined phrases and approaches into their communication, non-native English speakers can not only improve their fluency but also build stronger, more productive mentorship relationships.