40 Microsoft Behavioral Interview Questions by Theme

Microsoft behavioral interview questions rarely arrive in a round of their own. They come as the first ten minutes of a coding interview, as most of the hiring manager's hour, and as whatever the final interviewer decides to dig into after reading everyone else's notes. A candidate who has prepared "the behavioral round" finds there was no such round, and that five different people each asked one or two questions and wrote the answers down.
This is a question bank for that situation: forty questions in five themes, each theme with what a strong answer contains and one short invented sketch. The themes follow the culture areas Microsoft names on its own careers pages and the competencies candidates report being scored on. For the structure of the loop itself, read the Microsoft software engineer interview guide; it is not repeated here.
How the questions are spread across the loop
Microsoft does not publish a rubric. Its interview tips page, as of November 2026, lists the culture areas it wants candidates to know: growth mindset, diverse and inclusive, One Microsoft, customer obsession, values, and manager expectations. Third-party guides add a set of competencies that interviewers reportedly score, with names like collaboration, drive for results, customer focus, influencing for impact, judgment and adaptability. The lists overlap, and they reduce to the five themes below.
Three things about the format, all candidate-reported and all varying by team:
- Every interviewer asks a little. Candidates report technical interviewers opening with a behavioral question before the problem, and behavioral rounds that include a short coding problem. One guide reports that interviewers in the final round all score collaboration, adaptability and customer obsession alongside technical skill, whatever their round is about.
- The hiring manager asks the most. Their round is usually half or more about how you work.
- The last interviewer asks what is still open. If your loop has an "as appropriate" round, that person has read the earlier feedback and tends to return to the weakest or least clear signal.
Microsoft's stated answer format is STAR with a fifth step: Situation, Task, Action, Result, Reflection. The reflection is where most answers fall short, because it requires saying what you would do differently and meaning it. If you have not used the format before, the STAR method guide covers the first four steps.
Growth mindset
This is the theme every guide puts first, and the one most likely to be probed by more than one interviewer. The question is always some form of: show me you can be wrong and get better. Interviewers listen for a real failure stated early and plainly, and for a change in behavior that outlasted the incident.
- Tell me about a time you failed. What did you change afterwards?
- Describe a piece of critical feedback you disagreed with at first.
- Tell me about a project that did not go as planned. What would you do differently now?
- What is something you believed about engineering two years ago that you no longer believe?
- Tell me about a time you had to learn a technology quickly to deliver something.
- Describe a time someone more junior than you taught you something.
- Tell me about a decision you made that turned out to be wrong. How did you find out?
- When did you last ask for feedback, and what did you do with it?
What a strong answer contains. The failure in the first two sentences, without a cushion. Your own part in it, with no "we" hiding the decision. The specific thing you do differently now, with one later occasion where you did it. And a reflection that costs you something: "I should have asked the on-call team before I shipped" is a reflection; "I learned the importance of communication" is not.
Sketch, invented, for question 2. A backend engineer is told in a review that her design documents are hard to act on: thorough, but the decision is buried on page four. She thinks the reviewer is skimming. Two weeks later a partner team builds against an option she had rejected in an appendix. She moves the decision and the rejected options to the first half page of her next three documents and asks the same reviewer to time how long it takes to find the ask. Reflection: she had been writing to show the work, and readers needed the answer.
Collaboration and One Microsoft
Microsoft is a company of large product groups that depend on each other, and "One Microsoft" is its name for working across those lines. Diversity and inclusion questions tend to land in this theme too: how you made room for a view that was not yours, or for a person who was not being heard.
- Tell me about a project that depended on a team you had no authority over.
- Describe a disagreement with a partner team. How was it decided?
- Tell me about a time you built on someone else's work instead of starting your own.
- Tell me about a time you helped another team succeed at a cost to your own schedule.
- Describe a time you changed your approach because of a colleague's perspective.
- Tell me about a time you noticed someone was being left out of a discussion. What did you do?
- Tell me about working with someone whose style was very different from yours.
- Describe a time you gave credit that could have been yours.
What a strong answer contains. The other people by role, and what each of them wanted. A mechanism that settled the disagreement (an agreed test, a shared metric, a written proposal), because "we talked and aligned" gives the interviewer nothing to write. A result that belongs to more than one team. For the inclusion questions, one concrete action you personally took; general statements about valuing diversity score nothing.
Sketch, invented, for question 10. A client engineer needs a new field in an API owned by a platform team that is mid-migration and has frozen the schema. Escalating would win the argument and lose the relationship. He writes a one-page proposal with two options: the platform team adds the field after the freeze, six weeks out, or his team ships a temporary adapter now and deletes it on a named date. The platform lead picks the adapter and adds one condition, a contract test in their pipeline. The feature ships on time and the adapter is removed in week seven. Reflection: he would have asked about the freeze calendar before committing his own date.
Customer focus
Microsoft's phrase is "customer obsessed", and its culture page talks about understanding customers "with a beginner's mind". For an engineer the customer may be an enterprise admin, a developer using your API, or the team next door. Interviewers want to hear how you found out what the customer needed, which is different from what they asked for.
- Tell me about a time you learned something from a customer that changed what you built.
- Describe a time you pushed back on a feature request because it did not solve the customer's problem.
- Tell me about a trade-off you made in the customer's favor that cost your team something.
- How did you last find out how your work is used in practice?
- Tell me about a time a customer was affected by an issue you owned. What did you do first?
- Describe a time you had to balance one large customer's demand against the product's direction.
- Tell me about a time you simplified something for the people using it.
- Tell me about a decision you made with data about customers that turned out to mislead you.
What a strong answer contains. A named kind of customer, a way you learned about them that went beyond a ticket (a support call you joined, usage data you pulled, an admin you sat with), the trade-off, and what it did for them in terms they would recognize. Stories whose result is an internal metric alone tend to read as weak here.
Sketch, invented, for question 17. An engineer on an identity product keeps seeing a request for bulk import by spreadsheet. Before building it, she joins three support calls and finds the admins are not importing users: they are fixing the same misconfigured group, by hand, every Monday after a sync job. She ships a validation warning on the sync job in a week instead of an import tool in a quarter. The request volume for bulk import falls without the feature existing. Reflection: she now reads ten raw tickets before accepting a summary of them.
Ambiguity and adaptability
Guides report adaptability as a scored competency, and it is also tested live: they describe interviewers changing a coding question halfway through to see how the candidate adjusts. The behavioral version asks what you did when the goal moved, the plan broke or nobody could tell you what was wanted.
- Tell me about a project where the requirements were unclear at the start. How did you decide what to build?
- Describe a time priorities changed in the middle of your work.
- Tell me about a time you had to make a decision without the data you wanted.
- Tell me about a reorganization or strategy change that affected your project.
- Describe a time you were handed someone else's half-finished work.
- Tell me about a time you were wrong about how long something would take.
- Describe a time you had to stop a project you believed in.
- Tell me about a time you had two managers or stakeholders asking for conflicting things.
What a strong answer contains. What was unknown, stated precisely. The step you took to shrink it (a prototype, a written set of assumptions sent for objection, a small release), and what you decided not to wait for. Then the correction: where your first read was off and how quickly you noticed. An answer in which the ambiguity was resolved by a manager telling you what to do is an answer about your manager.
Sketch, invented, for question 26. Six weeks into a performance project, an engineer's team is told a compliance deadline now comes first. He has a half-merged caching change. Instead of parking it, he spends one day putting it behind a flag that defaults to off, writes a two-paragraph note on its state and the one known bug, and moves to the compliance work. Three months later a colleague picks it up from the note and ships it in a week. Reflection: he had started the caching change as one large branch, and would now cut it so that every merged piece is safe to leave.
Impact and results
One guide ties this theme to the way Microsoft describes impact internally, in three parts: your own work, what you contributed to others' success, and what you achieved by building on others' work. The same guide lists solo-hero stories among the common mistakes. A result here is stronger when someone else's work is visible in it.
- What is the piece of work you are proudest of, and how do you know it mattered?
- Tell me about a time you delivered something under a hard deadline. What did you cut?
- Describe a time you improved something nobody asked you to improve.
- Tell me about a time your work made another engineer or team faster.
- Tell me about a result you got by reusing something that already existed.
- Describe a goal you missed. What did you tell people, and when?
- Tell me about a time you had to choose between quality and a date.
- What did you do in your last role that would not have happened without you?
What a strong answer contains. A number with a before and after, and one sentence on how you measured it. Your part separated from the team's. Who else benefited. For the deadline and quality questions, the thing you chose not to do and who you told. Interviewers at senior levels also listen for scope: whether the result changed one service or how several teams work.
Sketch, invented, for question 37. A team needs rate limiting for a new public endpoint. An engineer finds that another org already runs a limiter as a shared library, with one missing feature: per-tenant overrides. She contributes the override to their library instead of writing her own, which takes nine days against an estimated four weeks for a new component. Two other teams adopt the override within the quarter. Reflection: finding the library took a chance hallway conversation, so she added it to her team's design template as a required "what exists already" section.
Manager variants
Candidates for lead and manager roles get the same five themes pointed at a team. Microsoft lists "manager expectations" among its culture areas, and the reported questions are about how you develop people and what climate you create. These sit outside the forty:
- Tell me about someone you managed who was underperforming. What did you do, in order?
- Describe how you helped an engineer grow into a role they were not ready for.
- Tell me about a time you had to deliver a decision to your team that you disagreed with.
- How do you find out what your team will not tell you?
- Tell me about a hire you got wrong.
- Describe a time you protected your team's focus from a request that came from above.
- Tell me about a time your team failed. What was your part?
Strong manager answers name the person's situation without identifying them, give the conversation and not only the outcome, and include what you got wrong. The engineering manager interview questions bank goes further on people and delivery stories.
Mistakes that cost offers
- No real failure. A "failure" that was secretly a success, or someone else's fault, is the mistake guides list first for growth mindset answers.
- No reflection. The answer ends at the result. Add the fifth step, and make it specific enough that it could be wrong.
- Only solo stories. If none of your eight stories has another team in it, the collaboration signal is empty.
- Skipping inclusion. Candidates prepare for conflict and forget they may be asked what they did to include someone. Have one concrete example.
- Different versions for different interviewers. Notes are compared. A story whose numbers move between rounds is noticed.
- Folding on the follow-up. "What would you do differently?" and "what did your manager think?" decide the grade more than the opening answer does. Rehearse the story to its third follow-up, ideally with a coach who has worked at Microsoft asking them.
Building the set of stories
Forty questions do not need forty stories. Eight will cover them: two failures, two cross-team stories, two customer stories, one about a changed plan, one about your largest result. Write each as five lines, one per STAR(R) step, then mark which of the five themes it can serve. The story bank guide shows the layout.
Then say them aloud to someone who will interrupt. Written stories sound complete until the first follow-up, and a listener who has run this kind of loop will find the gap in a minute; that is the point at which an hour with one of the coaches who have worked at Microsoft is well spent. If you interview at more than one company, check the stories against the Amazon questions by principle and the Meta questions by signal too. The stories transfer; the emphasis does not.
Where coaching fits
A question bank tells you what will be asked, and only another person can tell you how your answer sounded. techinterview.coach lists six coaches with Microsoft on their history as of November 2026; a mock behavioral session with a coach of that background can cover your weakest theme and the follow-ups you did not anticipate. For repetitions before or between sessions, the AI practice interview runs a behavioral round by voice and writes a recap of what worked and what to drill. It is free, sign in to start.
Related guides
- Microsoft software engineer interview: the loop these questions are asked in, including the as-appropriate round.
- The STAR method: the structure Microsoft extends with a reflection step.
- Building your story bank: how to get eight stories to cover forty questions.
- 40 Meta behavioral interview questions by signal: the same exercise for a company that grades signals.
- Amazon behavioral interview questions: sixty questions by leadership principle, for comparison.
- Engineering manager interview questions: more people and delivery questions for the manager variants.