TECH ENGLISH

Mentoring Junior Developers

Learn how to mentor junior developers in English — give constructive feedback, explain concepts clearly, and build their confidence with the right phrases.

Practice Tech Discussions

Scenario Context

You're mentoring a junior developer who just joined your team three months ago. They submitted their first major PR and it has several issues — over-engineered class hierarchy, missing error handling, and no tests. You need to give honest feedback while keeping them motivated and helping them learn.

Why This Matters for Engineers

Mentoring is one of the highest-leverage activities a senior engineer can do. The ability to explain complex concepts in simple terms, give feedback that builds confidence rather than crushing it, and guide someone's growth requires nuanced communication skills. Non-native English speakers who mentor well demonstrate leadership qualities that are essential for promotion to senior, staff, and principal engineering roles.

Essential Phrases

Great first attempt — let's talk through a few areas where we can make this even better.

Opening feedback positively

neutral

I see what you were going for here — the intuition is right, but the implementation could be simpler.

Validating the thinking

neutral

A good rule of thumb is: don't add abstraction until you have at least three concrete use cases.

Teaching a principle

neutral

What would happen if this function receives a null input? Let's think through that together.

Guiding to error handling

neutral

When I was at your level, I made the exact same mistake. Here's what I learned…

Sharing personal experience

casual

Can you walk me through your thought process for choosing this design pattern?

Understanding their reasoning

formal

Instead of giving you the answer, let me point you in the right direction.

Encouraging independent thinking

neutral

You're making great progress — three months ago you wouldn't have been able to build this.

Acknowledging growth

casual

Let's pair on this section — I'll drive and you navigate. Then we'll switch.

Pair programming

casual

What resources have you been using? Let me suggest a few that helped me level up.

Recommending resources

neutral

Don't be afraid to ask questions — the only bad question is the one you don't ask.

Encouraging questions

casual

Technical Pronunciation

Word❌ Common Error✅ CorrectTip
juniorJUN-ee-orJOON-yurTwo syllables — rhymes with 'moon-yur'.
mentorMEN-torMEN-torStress on first syllable, same as 'mental'.
abstractionab-STRAK-shunab-STRAK-shunStress on STRAK. Make sure to pronounce the 'b' clearly.
inheritancein-HAIR-ih-tensein-HAIR-ih-tuhnsFour syllables. The ending is '-tuhns', not '-tense'.
polymorphismpoly-MOR-fismpol-ee-MOR-fiz-uhmFive syllables: pol-ee-MOR-fiz-uhm.

Written vs. Spoken English

Engineers often write one way on Slack or GitHub, but speak differently in meetings. Here's how to translate.

Correcting a design choice

Written (Slack/PR)
Consider removing the abstract base class — the current implementation only has one concrete implementation, making the abstraction premature.
Spoken (Meeting)
I think we can simplify this — since there's only one implementation right now, the abstract class is adding complexity without benefit. Let's start with a plain function.

Encouraging testing

Written (Slack/PR)
Please add unit tests for edge cases: null input, empty string, and overflow conditions.
Spoken (Meeting)
Let's add some tests for this — what happens if the input is null? Or an empty string? Those are the kinds of edge cases that catch bugs before they reach production.

Giving praise

Written (Slack/PR)
Good progress on the feature implementation.
Spoken (Meeting)
Honestly, this is really solid for your first big feature. You're growing fast.

Example Dialogue

YO
YouHey, I had a chance to look at your PR. First of all — really impressive work for your first major feature. The fact that you shipped something end-to-end is a big deal.
JU
Junior DevThanks! I worked really hard on it. I know it's probably not perfect…
YO
YouNo code ever is — that's what reviews are for. Let me share a few suggestions that I think will really level up the code.
YO
YouI noticed you created a class hierarchy with an abstract base class and three subclasses. Can you walk me through your reasoning?
JU
Junior DevI learned about the strategy pattern and thought it would make the code more extensible.
YO
YouI love that you're thinking about design patterns. In this case, though, we only have one variant right now. A good rule of thumb is: don't add abstraction until you have at least three use cases. Start simple, and refactor when complexity is justified.
JU
Junior DevThat makes sense. So I should just use a plain function for now?
YO
YouExactly. Another thing — what happens if this function receives a null input? Right now it would crash. Let's add some error handling.
JU
Junior DevOh, I didn't think about that. Should I throw an error or return a default value?
YO
YouGreat question. It depends on the context. In this case, since it's a public API, I'd throw a descriptive error so the caller knows what went wrong. Let's also add a test for that case.

Common Questions

How do I give critical feedback to a junior developer without demotivating them?
Use the 'compliment sandwich' approach — but make it genuine. Start with something they did well, then share the improvement area with a learning perspective ('Here's something that will make you even stronger…'), and end with encouragement about their growth.
How do I know when to give the answer vs. let them figure it out?
If they've been stuck for more than 30 minutes, give them a nudge. Ask guiding questions like 'What would happen if…?' or 'Have you looked at how module X handles this?' If they're truly lost, pair with them rather than just handing over the answer.
What's the best way to hold regular mentoring sessions in English?
Meet weekly for 30 minutes. Have a loose agenda: (1) How are things going? (2) What did you learn this week? (3) What's challenging? (4) Let's work through one thing together. Keep it conversational, not like a performance review.

Stop Stumbling on Tech Calls

Practice explaining code, architecture, and bugs with an AI coach that understands engineering context.

Start Practicing Now

No credit card required.