Microsoft behavioral interview: Growth mindset plus stated values
There is often no separate behavioral round: most rounds mix in questions about past work, collaboration and learning from mistakes. The careers site names these values as what it looks for.
| Progress | Principle | Your story |
|---|---|---|
| RespectIntegrity and trust | Write a story | |
Sample answer: Tell me about a time you had to tell someone something they did not want to hearWhether you are honest when it costs you something: raising a problem early, owning your part without spin, and rebuilding confidence through actions. They want to see that people could rely on what you said afterwards. Situation I built a dashboard for our product team that showed weekly active users for a new feature. Three weeks after launch, the product lead used it in a planning meeting to argue for expanding the feature to more markets. Task While adding a new chart, I noticed that users who switched between our app and website were counted twice. The real number was about 25 percent lower than the one in the planning slides. I had to tell the product lead, quickly and clearly, even though the mistake was mine and the decision was already in motion. Action I spent an hour confirming the error with a second query so I would not raise a false alarm, then messaged the product lead the same afternoon instead of waiting for our next meeting. I wrote three things: what was wrong, the corrected number, and that it was my mistake in how I joined two data sources. I added that the trend was still upward, so they could judge whether the decision still held. I fixed the dashboard that day, put a visible note on it explaining the correction and its date, and checked my other two dashboards for the same join, finding one more small error. Then I added a test that compares our user counts against the source system each day. Result The product lead re-ran the numbers; the expansion still made sense but went to two markets instead of four. They told me later that hearing it from me within hours, with the correct number ready, made them trust the dashboards more, not less. The daily check has since caught two data problems from other teams before anyone used them. Tip: Show you were honest when it was uncomfortable, and how you earned trust back. Integrity and trust: weak answer, follow-ups and level differences | ||
| IntegrityIntegrity and trust | Write a story | |
Sample answer: Tell me about a time you had to tell someone something they did not want to hearWhether you are honest when it costs you something: raising a problem early, owning your part without spin, and rebuilding confidence through actions. They want to see that people could rely on what you said afterwards. Situation I built a dashboard for our product team that showed weekly active users for a new feature. Three weeks after launch, the product lead used it in a planning meeting to argue for expanding the feature to more markets. Task While adding a new chart, I noticed that users who switched between our app and website were counted twice. The real number was about 25 percent lower than the one in the planning slides. I had to tell the product lead, quickly and clearly, even though the mistake was mine and the decision was already in motion. Action I spent an hour confirming the error with a second query so I would not raise a false alarm, then messaged the product lead the same afternoon instead of waiting for our next meeting. I wrote three things: what was wrong, the corrected number, and that it was my mistake in how I joined two data sources. I added that the trend was still upward, so they could judge whether the decision still held. I fixed the dashboard that day, put a visible note on it explaining the correction and its date, and checked my other two dashboards for the same join, finding one more small error. Then I added a test that compares our user counts against the source system each day. Result The product lead re-ran the numbers; the expansion still made sense but went to two markets instead of four. They told me later that hearing it from me within hours, with the correct number ready, made them trust the dashboards more, not less. The daily check has since caught two data problems from other teams before anyone used them. Tip: Show you were honest when it was uncomfortable, and how you earned trust back. Integrity and trust: weak answer, follow-ups and level differences | ||
| AccountabilityOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
| Growth mindsetCuriosity and growth | Write a story | |
Sample answer: Tell me about something you had to learn quickly for a projectWhether you can learn something unfamiliar quickly and on purpose: a plan for what to learn first, using people and code as well as documents, and applying it to real work. Curiosity should lead to a result, not just a course you finished. Situation The engineer who owned our team's pricing service moved to another team with two weeks' notice. The service was written in a language nobody else on the team knew, and it was due for a change to support a new discount type in five weeks. Task I volunteered to take it over. I had never written that language, so I needed to become safe on call for the service within two weeks and ship the discount change on time. Action I made a plan around the service rather than the language. In the first three days I read the code path for a single price request from start to finish and drew it, writing down every language feature I did not understand. I learned only those features first, from the official tutorial and by writing small throwaway programs. I booked three one-hour sessions with the departing owner and used them only for questions I could not answer from the code, such as why certain decisions were made. To learn by doing, I fixed two small open bugs in my first week and asked an engineer from another team who used the language daily to review them. I kept a notes page of patterns and pitfalls, which became the service's onboarding guide. Result I took over on-call for the service after two weeks and shipped the new discount type a week early, with no incidents. A second teammate onboarded in four days using my notes. I still use the same approach for unfamiliar systems: trace one real request, learn what it needs, and ship something small in week one. Tip: Show something you learned on your own and how you used it at work. Curiosity and growth: weak answer, follow-ups and level differences | ||
How to answer
Use STAR: the Situation in one or two sentences, the Task you owned, the Actions you took (in the first person, the longest part), and the Result with a number. One strong story can cover several principles, so write a few good ones in the story bank and tag them.
Behavioral questions by theme, with a tip for each · How the behavioral round is scored
Questions people ask
What is the Microsoft behavioral interview based on?
Growth mindset plus stated values: Respect, Integrity, Accountability, Growth mindset. There is often no separate behavioral round: most rounds mix in questions about past work, collaboration and learning from mistakes. The careers site names these values as what it looks for.
How do I answer Microsoft questions on "Respect"?
Whether you are honest when it costs you something: raising a problem early, owning your part without spin, and rebuilding confidence through actions. They want to see that people could rely on what you said afterwards. Show you were honest when it was uncomfortable, and how you earned trust back. A typical question: Tell me about a time you had to tell someone something they did not want to hear
How do I answer Microsoft questions on "Integrity"?
Whether you are honest when it costs you something: raising a problem early, owning your part without spin, and rebuilding confidence through actions. They want to see that people could rely on what you said afterwards. Show you were honest when it was uncomfortable, and how you earned trust back. A typical question: Tell me about a time you had to tell someone something they did not want to hear