Mentoring Junior Engineers Without Doing Their Work

Mentoring junior engineers is not the same as answering every question quickly.

Fast answers feel helpful in the moment, but they can create dependency. Good mentoring helps engineers become more independent while still feeling supported.

Start with the goal

Before helping, understand what the junior engineer is trying to learn.

Ask:

• What have you tried?
• What result did you expect?
• Where exactly are you stuck?
• What part feels unclear?
• What would you do next if I were not here?

These questions reveal whether the problem is technical knowledge, debugging process, confidence, or missing context.

Teach the debugging path

Do not only explain the fix. Explain how you found it.

For example:

• which logs you checked
• which assumption you tested first
• why one hypothesis was more likely than another
• how you narrowed the failure
• what signal confirmed the fix

This teaches the mental model behind the answer.

Use code reviews as mentoring

A code review can either create shame or create growth.

Prefer comments that explain the principle:

• “This works, but it couples payment logic to the controller. Can we move it into a service so the retry behavior is easier to test?”
• “This query may become expensive as the table grows. What index would support this access pattern?”
• “Can you add a test for the failure case? That is where this function is most likely to break.”

The goal is to improve both the code and the engineer’s judgment.

Avoid taking over

Taking the keyboard is tempting, especially when the answer is obvious.

Use a ladder instead:

1. Ask a question.
2. Give a hint.
3. Point to a similar example.
4. Explain the concept.
5. Pair briefly if needed.
6. Let them finish the change.

This keeps ownership with the mentee.

Make progress visible

Junior engineers often do not notice their own growth.

Call out specific improvement:

• “Your test coverage is much stronger than last month.”
• “This design doc is clearer because you separated goals from implementation.”
• “You debugged this production issue with a good hypothesis-first approach.”

Specific feedback builds confidence and reinforces the right behavior.

Mentoring is promotion evidence

For senior engineers, mentoring is also leadership impact.

Track examples:

• engineers you helped onboard
• repeated questions you turned into documentation
• code review patterns you improved
• debugging habits you taught
• projects where someone became more independent because of your guidance

This evidence matters for Staff Engineer promotion because Staff-level impact includes raising the capability of others.

Good mentoring is not doing the work for someone. It is helping them become the kind of engineer who can do more of it next time.