Mentorship¶

Theme: Growth & Leadership | Seniority: Senior → Staff

Why This Question Gets Asked¶

"Tell me about mentoring someone" is scored on the mentee's outcome, not on how good it felt to mentor. Interviewers are checking:

• Did you diagnose what the person actually needed, or default to generic advice?
• Can you delegate a project you could do faster yourself, and let them own the mistakes?
• Can you give feedback that stings, specifically enough that it changes behavior?
• Is there a measurable outcome for the mentee — a promotion, a skill they didn't have before, work they can now own unsupervised?

STAR + Reflection Framework¶

flowchart LR
    S[Situation\nwho, what gap] --> T[Task\nyour role, what you\ncommitted to]
    T --> A[Action\nwhat you delegated,\nwhat feedback you gave]
    A --> R[Result\ntheir outcome, quantified]
    R --> Ref[Reflection\nwhat you'd do differently]
    style A fill:#1b5e20,color:#fff
    style R fill:#e65100,color:#fff
    style Ref fill:#37474f,color:#fff

Seniority Differentiation¶

Delegating a Stretch Project¶

The mechanics that separate real delegation from dumping work:

1. Pick something genuinely uncomfortable, not busywork. If you'd have done it in half the time and it wouldn't have taught you anything either, it's not a stretch project.
2. Set the boundary once, explicitly. "You own the design decisions; I'll review once, then get out of the way" — vague availability ("let me know if you need anything") invites either abandonment or micromanagement.
3. Let them hit a real mistake if the blast radius is contained. Catching their own gap in a design review teaches more than being told the answer.
4. Attribute the outcome to them, not to you, afterward — in promo docs, in team updates, in the interview story itself.

Assessing Delegation Readiness¶

flowchart TD
    A[Candidate for a\nstretch project] --> B{Shown sound judgement\non smaller scoped work?}
    B -->|No| C[Not ready yet —\npair closely on something smaller first]
    B -->|Yes| D{Is the blast radius\nof a mistake contained?}
    D -->|No| E[Narrow the scope until\na wrong call is recoverable]
    D -->|Yes| F[Delegate: set the boundary\nonce, review the doc, then step back]
    F --> G{Did they make a call\nyou'd have made differently?}
    G -->|Yes, and it stood| H[Real delegation —\nattribute the outcome to them]
    G -->|No, you overrode it| I[Not delegation yet —\nreassess your own letting-go]

A Mentee Who Didn't Improve¶

Not every investment pays off, and it's worth naming when it doesn't. I spent close to a year with an engineer who was struggling with debugging discipline — jumping to fixes without forming a hypothesis, the same pattern across a dozen incidents. I paired with them repeatedly, gave direct feedback each time, and delegated smaller investigation tasks with explicit checkpoints. The pattern didn't change. What I eventually realized, too late to fully act on it, was that I'd been treating it as a skills gap when it was closer to a mismatch — the role required fast, ambiguous triage under pressure, and this person did genuinely careful, methodical work when given time, which was a real strength I kept trying to route around instead of routing to. I should have raised, much earlier, whether they belonged on a different kind of team rather than continuing to coach a mismatch as if more repetition would close it. They eventually moved to a data-quality role on another team and did well there. I learned to ask "is this a skill gap or a fit gap" explicitly, early, instead of assuming every struggle is coachable with enough time.

Giving Hard Feedback¶

The feedback that sticks has three properties: it's specific, it names the pattern not the person, and it comes with a concrete alternative.

Common Interview Questions¶

1. "Tell me about mentoring someone junior."
2. "Describe a time you delegated something you could have done faster yourself."
3. "Tell me about giving feedback that was hard to deliver."
4. "How do you know when someone is ready for more responsibility?"
5. "Tell me about someone whose growth you're proud of."

Staff-Level Extensions¶

Red Flags in Answers¶

Self-Assessment¶

• [ ] Can I name the specific gap I diagnosed in a mentee, not a generic one?
• [ ] Do I have a story where I delegated real ownership and let a mistake play out safely?
• [ ] Do I have a specific hard-feedback moment with the exact words I used?
• [ ] Can I cite a measurable outcome for them (promotion, new capability, ownership)?
• [ ] For Staff roles: did I address a pattern across people, not just one relationship?