Developing others: what interviewers score and how to build the story

Developing others is mandatory for manager and staff-plus candidates and increasingly asked at senior. Most individual contributors have real material here and describe it in a way that scores as nothing.

This lesson fixes the description. It starts with the one distinction the whole competency turns on — whose outcome it is — then covers the signals, including the question interviewers ask in almost every round and candidates often cannot answer, the seven phrasings, and the requirement that eliminates most candidate material.

The definition

The distinction in that last sentence is the whole competency. An engineer who unblocks a struggling colleague by taking the task and finishing it has helped the project and scored zero on this competency — possibly negative, because the colleague learned nothing and the dependency is now stronger.

What it looks like without a title

You do not need reports. The four common shapes:

Mentorship. A recurring relationship, usually informal, with someone who is not your report. The evidence is what they can do now that they could not before.

Code review as teaching. Review is the highest-frequency teaching surface most engineers have and the least deliberately used. The difference between "change this to a map" and "what happens here if the list is empty?" is the whole competency in one line.

Onboarding. Not the document. The first-month experience of a specific person, and what you changed for them.

Creating conditions. Giving away work you would enjoy, running a rotation so someone else gets the interesting incident, or deliberately not answering in a meeting so someone else does.

What it is not

It is not being nice. Approachability is a prerequisite, not the competency.

It is not delegation for your own capacity. Handing off work because you are busy is delivery. Handing off work you wanted to do, because someone else needs it, is this.

Signals scored

Three positives, four negatives, and one that interviewers ask for directly and candidates rarely have.

The positive indicators

1. Real investment of your own time, at a cost. Named and quantified:

"We paired for ninety minutes every Tuesday for four months. That came out of the work I'd otherwise have done on the ingestion rewrite, which slipped about three weeks as a result, and I'd make that trade again."

The cost is what makes it credible. Mentorship with no opportunity cost usually means it did not happen at the stated intensity.

2. Adaptation to the individual. Evidence that you diagnosed this person rather than applying a general method:

"The first thing I got wrong was assuming it was a knowledge gap and sending them reading. It wasn't. They knew the material and they were writing designs that answered 'how' without ever stating 'why', so reviewers couldn't evaluate them and rewrote them instead. That's a framing problem, not a knowledge problem, and it needed a completely different intervention."

3. Evidence the other person actually improved. Specific, external, and preferably something they now do without you.

The negative indicators

The one that is asked for directly

"Where is that person now?"

Interviewers ask this in almost every developing-others interview, and a large share of candidates cannot answer. It is a fair test: if you genuinely invested months in someone, you know what happened to them.

The strong answer is specific and does not require a promotion:

"They're a senior engineer on the same team, promoted about nine months after we stopped pairing. More usefully — they now run the design review I taught them to write for, and two months ago they gave me feedback on one of my designs that changed it."

The last sentence is the strongest available evidence in the competency, because it shows the relationship inverted.

Questions asked

Seven phrasings. Three are asked mainly of managers, and individual contributors should prepare them anyway if interviewing at staff level.

1. "Tell me about someone you mentored."
2. "Tell me about a time you helped someone improve."
3. "How do you handle an underperforming teammate?" (manager-weighted)
4. "Tell me about a time you gave someone difficult feedback."
5. "Tell me about a time you had to develop someone with a very different working style from yours."
6. "How do you decide what work to give away?" (staff and manager)
7. "Tell me about someone who grew faster because you were there." (the hardest and best)

What each is really probing

Question 4 has a common failure

"A time you gave someone difficult feedback" is answered badly when the feedback was so carefully wrapped that it did not land. Interviewers probe for the actual words.

Interviewer: What did you say?

Weak: "I said that there were some areas where maybe we could look at improving the approach to code review, and asked how they felt things were going."

Strong: "I said: 'Your review comments are landing as dismissive with at least two people, and I think you don't intend that. The specific thing is that you say what's wrong without saying what you'd do instead, and on a long thread that reads as contempt.' Then I stopped talking, which was the hard part."

Have the sentence. Interviewers ask for it.

Question 3 requires an honest ending

Underperformance stories where everything resolved happily are less common in reality than in interviews. Interviewers know this. An honest answer that ends in the person leaving the team, handled well, scores better than an implausible turnaround.

Building the story

Two tests, and one requirement that eliminates most candidate material immediately.

Test 1 — the outcome belongs to them

The subject of the result sentence must be the other person. Try writing it:

If every sentence you can write has you as the subject, this is a delivery story.

Test 2 — you can say where they are now

Not necessarily promoted. Where they are, what they do, and ideally something they do that you do not.

The requirement that eliminates most material

One person, named, over a sustained period. Plural mentorship — "I've mentored a lot of juniors" — produces nothing scoreable. It is the single most common way this competency gets answered into a zero.

Sustained means months, not a conversation. The exception is a single high-stakes feedback conversation with a documented consequence, which can carry a story on its own.

Level calibration

Where to look

• The person whose pull requests you reviewed most in the last two years
• Anyone who joined the team and asked you the most questions in month one
• Someone you deliberately handed work to that you wanted
• Anyone you had a hard conversation with, in either direction
• The person on your team whose promotion case you wrote or contributed to