Growth: what interviewers score and how to build the story

Growth is evidence that you improve on purpose. It is not evidence that you are curious, and it is not a reading list.

That distinction rules out the most common answers to growth questions, so this lesson starts with it. Then it covers the signals — including one question asked in almost every loop — the six phrasings you will meet, and a three-line test for building a story that scores.

The definition

The two words doing the work are deliberate and observable. Everyone improves through exposure. The competency is about whether you improve on purpose, and whether you can point at the difference.

What it is not

It is not learning technology. "I taught myself Rust" is fine and it is nearly always the weakest available answer, because learning a language is what engineers do and it costs nothing to claim.

It is not curiosity. "I read a lot of engineering blogs and I'm always trying to learn new things" is unfalsifiable and applies to almost every candidate.

It is not humility. Interviewers are not scoring modesty. A candidate can be confident and still score full marks here.

It is not the failure question. Adjacent, and different. The failure question (covered in Section 5) is about ownership of a bad outcome. This is about the mechanism by which you got better, which may have nothing to do with a failure.

The pairing that makes it work

Every strong growth story is a pair: a specific trigger and a specific change, with an effect between them.

Trigger: three people independently told my manager I shut down discussion in design reviews. Change: I stopped speaking first, and I started writing a "what I might be wrong about" section in every design doc. Effect: two of the next four designs changed direction based on someone else's input, which had not happened in the previous year.

Twenty seconds, and it fills the rubric row completely. Most candidates give the trigger and skip the other two.

Signals scored

Four positives, four negatives, and one signal that is asked for directly in almost every round.

The positive indicators

1. You act on feedback, specifically. The observable form names the behaviour, not the sentiment:

"The feedback was that my design docs were hard to review. What I changed concretely: I now put the decision and the alternatives on page one, and the mechanism after. The first doc I wrote that way got four substantive comments; the previous one had got two typo fixes."

2. You seek feedback unprompted. Rarer and weighted heavily:

"After every design review I run, I ask one person who was quiet what they didn't say. About a third of the time there's something."

3. Self-awareness about a real weakness. A weakness that costs something, described without either drama or deflection.

4. Demonstrated change over time. The strongest form has a "before" and an "after" separated by months, with evidence at both ends.

The negative indicators

The one that decides it

"What's the most useful piece of feedback you've ever received?" — or its harsher sibling, "what would your last manager say you need to work on?"

This is asked in most loops, and it is answered badly by most candidates, which makes a good answer disproportionately valuable.

What a good answer contains:

• A real weakness that has a cost you can name.
• The words the person actually used, near enough.
• What you changed, specifically.
• What is still true. The strongest answers admit the change is partial: "I'm better at this than I was and it's still the thing I have to consciously watch."

That last element is worth deliberate practice. A candidate who claims a weakness is fully solved has told the interviewer they stopped paying attention.

Questions asked

Six phrasings, and two of them are the same question wearing different clothes.

1. "Tell me about feedback that was hard to hear."
2. "What's the most useful feedback you've received?"
3. "Tell me about a skill you deliberately built."
4. "Tell me about something you changed your mind about."
5. "What would your last manager say you need to work on?"
6. "Tell me about a time you had to learn something quickly to get a job done."

What each is really probing

Question 1 and question 5 are the same question

The interviewer wants a real weakness. Question 1 gives you narrative cover; question 5 removes it. Prepare one answer that serves both, and be ready for the follow-up that turns one into the other: "and is that still something you work on?"

Question 4 deserves preparation

"Something you changed your mind about" is under-prepared and it is the best question in the set, because it lets you show updating on evidence rather than on authority.

Strong answers change a belief about how to work, not a preference:

Weak: "I used to prefer NoSQL databases and now I mostly reach for Postgres."

Strong: "I used to believe that if a system was hard to test, the tests were the problem. I spent about two years writing increasingly elaborate test infrastructure. What changed my mind was joining a team with a service that was trivially testable, and noticing that the difference wasn't the test tooling — it was that the service had one entry point and no hidden state. Untestable code is now the first thing I read as a design smell rather than a testing problem, and it has changed how I review."

The second is a belief, dated, with a cause and a consequence for how the candidate now works.

Question 3 has a trap

"A skill you deliberately built" invites a technical answer, and technical answers here are weak because learning technology is the baseline expectation. Non-technical skills score better and are more memorable:

• Running a meeting where a decision actually gets made
• Writing a design document people read
• Estimating
• Giving feedback that lands
• Saying no

Any of those, with a practice attached and an effect, outperforms "I learned Kubernetes".

Building the story

One structural test, and a second exercise that finds material most candidates believe they do not have.

The test: trigger, change, effect

Write your candidate story as three lines. If any line is empty, the story is not usable.

The change line is where most stories die. "I became more mindful about interrupting" is not a change; "I stopped speaking until at least two other people had, in every design review, for six months" is.

Where to look when you think you have nothing

Three sources, in order of how often they are overlooked:

Performance reviews. Every "areas for development" line is a trigger. Read the last three. Most people have not looked at them since the conversation.

Things you now do that you did not do two years ago. Work backwards. If you now write a one-page proposal before starting anything substantial, something taught you that. Find the event.

Feedback you rejected and later accepted. These are excellent stories because they contain both a defensible initial disagreement and a change of mind. "I dismissed it for about six months, and what made me take it seriously was —"

Level calibration

The escalation is not in how big the weakness was. It is in whether the change stayed personal or became something other people do.