Behavioural Interviews Module 5 – Growth, customers, integrity and AI at work
Feedback, learning and growth questions
Answer feedback, learning and growth questions with what you changed, how you learned it and who noticed, and show the habits that keep your skills current.
What you will learn
- Describe acting on critical feedback, with evidence of change
- Explain how you learned something difficult quickly
- Show adaptation to change and growth outside your comfort zone
- Describe concrete habits that keep your skills current
Before you start
What you’ll learn · Before you start
What you will learn
- Describe acting on critical feedback, with evidence of change
- Explain how you learned something difficult quickly
- Show adaptation to change and growth outside your comfort zone
- Describe concrete habits that keep your skills current
Before you start
On this page
Asked for a time she received critical feedback, Kavya’s first draft gives the criticism three sentences and what she did about it none. The interviewer learns almost nothing from the criticism itself: what they can write down is the change that followed, and whether it lasted.
Feedback questions, learning questions and growth questions all look for that change. Below are the shape of a strong answer to each, Kavya’s feedback story told part by part, and a checker that says what your own stories still lack.
Not affiliated
Based on public information about Meta, Microsoft, Google, Netflix and Amazon. MySmartCoPilot is not affiliated with Meta, Microsoft, Google, Netflix and Amazon, and Meta, Microsoft, Google, Netflix and Amazon’s real hiring practices may differ from what this lesson describes.
Feedback questions ask what you changed, and how you know it worked
Employers that publish what they assess say so directly. Meta’s full-loop guide lists growing continuously among the five focus areas of its behavioural interview and asks: “Do you take constructive criticism as an opportunity to improve?” Microsoft’s interview tips suggest thinking about “how you have applied feedback” and how you then adapted your approach, and Netflix’s culture page lists willingly receiving and giving feedback under candour. None of them asks how the criticism felt.
A feedback story that answers them has five parts, a MySmartCoPilot pattern: the feedback, stated fairly; your first reaction, honestly and briefly; what you changed; how you checked that it worked; and who noticed. Step through Kavya’s story, part by part:
The drawing shows the whole scene; its 6 steps are listed below.
Every step as text
- The feedback. Kavya's tech lead tells her that readers of her 14-page design documents cannot find the decision. She repeats it as it was said, without softening it into praise or turning it into a complaint about the lead.
- Her first reaction. Her first reaction was to defend the detail. One honest sentence about it makes the change that follows believable; a minute on it would turn the answer into a grievance.
- What she changed. She checks where her recommendation first appears, page 9, and from her next design on opens every document with a one-page decision summary: the problem, the options, her recommendation and what she needs from readers.
- How she checked. She counts the questions that ask what she is proposing. On her next three designs they fall from about a dozen a document to one.
- Who noticed. The staff engineer now sends new joiners her document as the example. Someone else acting on the change is the strongest evidence that it worked.
- The whole answer. Five parts in about two minutes. The criticism takes one sentence; the change, the count and the person who noticed take the rest, and that is what the interviewer writes down.
The criticism takes one sentence of the two minutes; the rest is a change someone could see, from a page added to every document to a staff engineer who now hands her document to new joiners.
Feedback that was really praise
“My manager said I care too much about quality” is a strength dressed as criticism, and it answers a question about growth with a compliment. Choose feedback that named a real gap, and say what the gap cost before you fixed it.
Checkpoint
Check: The five parts of a feedback story
Learning questions ask how you learned, not how fast you are
A learning question asks about your method. Meta’s guide asks how you have approached improving your skills; Microsoft describes the growth mindset: The view that skills grow with effort, practice and feedback rather than being fixed. Microsoft names it among the parts of its culture that its interviews focus on. it looks for as “true learners who can acquire new skills rapidly”; Amazon’s principle Learn and Be Curious says that leaders “are never done learning”. “I’m a fast learner” claims the result and skips the method.
A learning story has five parts of its own: the goal and its deadline, how you learned, what you delivered, how long it took and how you shared it. Here is Rohan’s, a data engineer whose team had three weeks to learn a new framework:
| Part | Rohan’s learning sprint |
|---|---|
| The goal | Move the order-events pipeline from nightly batches to a stream, in three weeks |
| How he learned | The official tutorial, then a job rebuilt in a sandbox, then a design check with an expert |
| What he delivered | The orders dashboard’s lag fell from about six hours to under a minute |
| How long | Three weeks, alongside his normal work |
| How he shared it | A lunch session whose notes two other teams used |
The delivery row is what turns learning into a result.
Checkpoint
Check: Telling how you learned
Growth questions ask for a change you chose
Growth questions move from what happened to you to what you went looking for. Google’s interview tips ask, “How do you push yourself to grow outside your comfort zone?”, and Netflix’s culture page describes resilience as adapting quickly to changing circumstances. Two kinds of story answer growth questions:
| Kind of story | How it starts | What it is told by |
|---|---|---|
| A stretch assignment: Work you take on that is beyond what you can already do, chosen so that you grow, such as joining the on-call rota of a system you do not know yet. you chose | You go looking for it: the on-call rota of a system you do not know | What you can do now that you could not before |
| A change you adapted to | It is imposed: a cancelled project, a new team | What you do differently because of it |
A growth story about a real gap is also the best raw material for “What is your weakness?”: the gap, what you are doing about it and the evidence so far. And “How do you keep your skills current?” is a growth question about the future: answer it with habits you can show, not with a list of technologies.
Key idea
Feedback, learning and growth stories are scored on the same thing: a change you made, a check that it worked and someone who saw it. The criticism, the course or the stretch only sets the change up.
Checkpoint
Check: Stretches, changes and the weakness link
A three-week learning sprint, hour by hour, and how to tell it Pro: opens with a Pro, Premium or Ultimate pass
“I learned it in three weeks” invites the next question at once: how, and how did you know? Here is Rohan’s sprint phase by phase, his learning log added up, and the answers to the probes his story invites.
In this part:
- Rohan’s sprint, phase by phase, and why that order
- His learning log, added up into the numbers he will say
- Five probes a learning story invites, answered from the log
- The whole answer in 170 words, with every number in place
1 diagram · 1 runnable example (JavaScript) · about 6 minutes
Opening this part with your pass…
This part opens with any MySmartCoPilot pass.
- Pro pass · 1 week₹79$2.99
- 30 days₹179$5.99
- 1 year₹1,699$45
One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.
Passes can’t be bought right now, so this part can’t be opened at the moment. The free part above stands on its own. If you have a pass, enter your licence key.
It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).
Stretches, keeping current and the weakness question, with a rubric by level Pro: opens with a Pro, Premium or Ultimate pass
Growth stories go wrong in two ways: a stretch told without evidence, and keeping current told as a list of technologies. Both are fixed with the evidence a feedback story needs: what it cost, what changed and who gained.
In this part:
- A stretch you chose, told with what it cost and what it changed
- A change you did not choose, told as growth
- Keeping current, audited before you say it
- From a real gap to the weakness question
- A rubric: what each level is expected to show
1 runnable example (JavaScript) · about 6 minutes
Opening this part with your pass…Pro part. It opens with the same pass as the part above.
Practise: check your two stories
Write one feedback story and one learning story, put them in the checker in place of Kavya’s and Rohan’s, and fix what it marks missing:
// Feedback and learning stories, checked for the three things an interviewer listens for: what prompted the change
// (the feedback you were given, or what you had to learn and by when), what you did differently, and evidence that it
// worked, told after the change (a number, a length of time, or someone who noticed). Kavya, Rohan and their stories
// are invented. Put your own stories in STORIES, one string each, and run it again.
const STORIES = [
{
name: 'Kavya, feedback, first draft',
text: 'My tech lead told me my design documents were hard to follow. I was surprised, because I thought they were thorough. It was a good learning experience.',
},
{
name: 'Kavya, feedback, rewritten',
text: 'My tech lead said readers of my 14-page design documents could not find the decision. My first reaction was to defend the detail, but when I checked, the recommendation first appeared on page 9. I started every document with a one-page decision summary: the problem, the options, my recommendation and what I needed from readers. On my next three designs, questions about what I was proposing fell from about a dozen a document to one, and our staff engineer now sends new joiners my document as the example.',
},
{
name: 'Rohan, learning, first draft',
text: 'I am a fast learner, so I picked up the stream-processing framework very quickly for our migration.',
},
{
name: 'Rohan, learning, rewritten',
text: "Our team had three weeks to move the order-events pipeline from nightly batches to a stream, and none of us had used the framework. I worked through its official documentation and tutorial in the first week, rebuilt our smallest job in a sandbox in the second, and asked the platform team's expert to check my design. In week three I moved the first job: the lag on the orders dashboard fell from about six hours to under a minute, and two other teams used the notes from my lunch session for their own moves.",
},
];
// What prompted it: words that report feedback, or a goal with a deadline.
const PROMPT = /\b(?:told me|said|feedback|pointed out|asked me to|criticis\w*|had (?:\w+ ){0,2}(?:days?|weeks?|months?) to|had to learn|needed to learn|goal)\b/i;
// What you changed: "I" and a verb of doing. "I picked up", "I learned" and "I realised" are claims, not changes.
const CHANGE = /\bI (?:started|stopped|changed|rewrote|began|switched|added|moved|rebuilt|built|worked through|practised|practiced|set up|asked|now)\b/i;
// Evidence, in a sentence after the change: a number, a length of time, or a person who noticed or took it up.
const EVIDENCE = [
['a number', /\d|\b(?:one|two|three|four|five|six|seven|eight|nine|ten|dozen|half|twice|double|halved)\b/i],
['a length of time', /\b(?:later|since|days?|weeks?|months?|releases?)\b/i],
['someone who noticed', /\b(?:noticed|adopted|cited|thanked|sends|uses|used|asked for)\b/i],
];
const sentencesOf = (text) => text.split(/(?<=[.!?])\s+/);
let complete = 0;
for (const story of STORIES) {
const sentences = sentencesOf(story.text);
const prompt = PROMPT.exec(story.text);
const at = sentences.findIndex((s) => CHANGE.test(s));
const change = at >= 0 ? CHANGE.exec(sentences[at]) : null;
const after = at >= 0 ? sentences.slice(at + 1).join(' ') : '';
const evidence = EVIDENCE.map(([what, re]) => [what, re.exec(after)]).filter(([, m]) => m);
console.log(story.name);
console.log(prompt ? ` ok what prompted it: "${prompt[0]}"` : ' missing what prompted it: the feedback you were given, or what you had to learn and by when');
console.log(change ? ` ok what you changed: "${change[0]}"` : ' missing what you changed: what you did differently, as "I" and a verb (I started, I rewrote, I asked)');
console.log(evidence.length ? ` ok evidence it worked: ${evidence.map(([what, m]) => `${what} ("${m[0]}")`).join(', ')}` : ' missing evidence it worked: a number, a length of time or someone who noticed, after the change');
console.log('');
if (prompt && change && evidence.length) complete++;
}
console.log(`${complete} of ${STORIES.length} stories have all three parts.`);Output
Kavya, feedback, first draft
ok what prompted it: "told me"
missing what you changed: what you did differently, as "I" and a verb (I started, I rewrote, I asked)
missing evidence it worked: a number, a length of time or someone who noticed, after the change
Kavya, feedback, rewritten
ok what prompted it: "said"
ok what you changed: "I started"
ok evidence it worked: a number ("three"), someone who noticed ("sends")
Rohan, learning, first draft
missing what prompted it: the feedback you were given, or what you had to learn and by when
missing what you changed: what you did differently, as "I" and a verb (I started, I rewrote, I asked)
missing evidence it worked: a number, a length of time or someone who noticed, after the change
Rohan, learning, rewritten
ok what prompted it: "had three weeks to"
ok what you changed: "I worked through"
ok evidence it worked: a number ("three"), a length of time ("week"), someone who noticed ("used")
2 of 4 stories have all three parts.
Recorded with Node.js 24.21.0 on macOS 26 arm64. To run it yourself: mise exec node@24.21.0 -- node growth_check.mjs
Runs on this device, in your browser. The first run downloads JavaScript (about 0.6 MB), which is kept for the next runs.
Your run, in this browser
Both first drafts fail on the change: Kavya’s says how she felt and Rohan’s claims speed. The checker reads words, so it cannot tell a true story from an invented one; that part is yours.
Online Notepad Draft each story here first, then paste it into the checker as one string.Practice that adapts to you
Practise this lesson
8 questions about 5 ideas of this lesson. Each answer is explained at once, and what you get right is kept in this browser.
Interview questions
One warm-up comes with its answer. For the other three, pick a story from your bank and say it out loud before reading the first step of each.
-
Fresher to mid · Warm-up
What is an interviewer listening for when they ask about critical feedback you received?
A change, and evidence that it worked. The criticism on its own tells the interviewer little; what they can write down is what you did with it. Meta's full-loop guide asks whether you take constructive criticism as an opportunity to improve, and Microsoft's interview tips ask you to think about how you have applied feedback and adapted your approach. So give the feedback one fair sentence and your first reaction one honest sentence, then spend the rest of the answer on what you changed, how you checked that it worked and who noticed. Pick feedback that named a real gap: "I care too much about quality" is praise in disguise and dodges the question. End with what you do differently now, so that the change sounds like a habit rather than a single fix.
-
Mid to senior
Tell me about feedback you disagreed with when you first heard it. What did you do with it, and were you right to disagree?
-
Fresher to senior
What is the hardest thing you have had to learn for your work? How did you know you had learned it well enough to rely on?
-
Mid to staff
How do you keep your skills current? Tell me one thing you learned recently and where you used it at work.
Key takeaways
- A feedback answer gives the criticism one fair sentence and spends the rest on what you changed, how you checked it and who noticed.
- A learning answer shows the method: the goal and its deadline, the sources and practice, what you delivered, how long it took and how you shared it.
- A growth answer is a stretch you chose or a change you adapted to, told by what you do differently now.
- Keeping current is answered with habits you can show, never with a list of technologies.
Terms in this lesson
- growth mindset
- The view that skills grow with effort, practice and feedback rather than being fixed. Microsoft names it among the parts of its culture that its interviews focus on.
- stretch assignment
- Work you take on that is beyond what you can already do, chosen so that you grow, such as joining the on-call rota of a system you do not know yet.
References
- Software Engineer Full Loop Interview Guide (linked from the onsite preparation page) (Meta Careers)
- Interview tips (Microsoft Careers)
- Interviewing at Google: interview tips (Google Careers)
- Netflix culture: the values we live by (Netflix Jobs)
- Leadership Principles (Amazon.jobs)
- Interviewing at Amazon: the interview loop (Amazon.jobs)
Related tools
Report a problem with this lesson
Kept only in this browser. Your Learn progress