The same advice at the wrong time is bad advice.
Sometimes the difference in life experience is obvious, and you have to adjust to the other person’s rhythm.
In my experience it is more like “Oh, I was like that at X years old.” That recognition is useful — but only if you resist the urge to skip them past the stage they are in. Everyone has to live through their own version of it.
Everything is new and exciting. They want to learn everything at once. They volunteer for things they do not fully understand. Energy is high, direction is low.
What they need: structure, small wins, and protection from overcommitting. Give them clear tasks with defined boundaries. Celebrate the first thing they ship. Do not let them take on three projects because they want to prove themselves.
Common mistake: assuming their enthusiasm means they can handle ambiguity. They cannot. They are eager because they do not know enough to be overwhelmed yet. That changes fast if you throw them into the deep end.
They know enough to see how much they do not know. The initial excitement has worn off. They can do the work but they question whether they are doing it well enough. Impostor syndrome lives here.
What they need: validation that the frustration is normal, exposure to the bigger picture, and harder problems. This is the stage where a mentor’s context matters most. “I felt exactly this way two years in. It passes. Here is what helped me.”
Common mistake: more technical training. The problem is rarely knowledge at this stage — it is confidence and perspective. Another tutorial will not fix “I do not feel like I belong here.”
They can do most things independently. They rarely ask for help because they do not need it for the day-to-day. They might seem like they do not need a mentor anymore.
They do.
What they need: challenge. New dimensions of growth beyond their current comfort zone. Leadership opportunities, cross-team exposure, a project outside their specialty. And someone to bounce ideas off when the stakes get higher.
Common mistake: ignoring them because they are “fine.” The quiet competent is the person most likely to leave without warning, because nobody noticed they had outgrown the role.
At some point, the person you are mentoring catches up. They might even surpass you in certain areas. The relationship shifts — it becomes less about guidance and more about perspective exchange.
What they need: you to acknowledge the shift. The worst thing a mentor can do at this stage is keep acting like the authority. The best thing is to say “I think you know more about this than I do. What do you think?”
This is also where mentoring becomes bidirectional. You start learning from them. If that bruises your ego, mentoring is not for you.
Experience level is one axis. Personality is another.
Processes everything out loud. Needs to verbalize before they can decide. Meetings with them are long. Slack messages are paragraphs.
Approach: let them talk, but help them find the signal in their own noise. After they explain their thinking, ask: “If you had to summarize that in one sentence, what would it be?” You are not dismissing them — you are teaching them to find the core of their own thoughts.
Processes internally. Answers questions with three words. You are never sure if they are stuck, thinking, or bored.
Approach: do not fill the silence. Ask a question and wait. If they need time, give them time. Written communication (async messages, shared docs) often works better than live conversations. They are not disengaged — they are just not verbal about their engagement.
Will not ship until it is flawless. Every code review has 40 comments. Every document goes through five drafts. The quality is high, the velocity is low.
Approach: help them find the line between “good enough” and “perfect.” Timeboxing is your friend. “Spend two hours on this and show me what you have.” Show them real examples of shipped work that was not perfect and succeeded anyway.
Ships fast, breaks things, moves on. Velocity is high, quality varies. They would rather ask forgiveness than permission.
Approach: do not slow them down — redirect them. Channel the speed toward things where fast iteration is valuable (prototyping, spikes, proof of concepts). For things that need precision, pair with them so they learn to match speed to stakes.
Every person is a different combination of stage, personality, context, and goals. There is no universal approach to mentoring.
But there is one rule that applies to all of them: meet them where they are, not where you think they should be.
The eager beginner does not need your senior-level perspective on architecture. The frustrated intermediate does not need a pep talk about potential. The quiet competent does not need more autonomy — they need harder problems.
The same advice at the wrong time is bad advice.