Microsoft Full Stack Engineer Interview Questions (2026)

1. 1Recruiter screen30 minEasy

   Role alignment, team options, and logistics with a recruiter.

2. 2Online assessment (Codility)60 minMedium

   Timed coding problems used mainly for early-career and campus screening in India.

3. 3Coding interview 145 minMedium

   DSA problem with production-quality code, testing, and edge cases in a shared editor.

4. 4Coding interview 245 minHard

   Harder algorithmic problem plus discussion of a past project's technical decisions.

5. 5System design round60 minHard

   Design a practical service (e.g. Teams presence, OneDrive sync) with API contracts and Azure-flavored components.

6. 6As Appropriate (AsApp) round45 minMedium

   Senior manager assesses growth mindset, long-term potential, and overall fit; effectively the closing behavioral gate.

1. Q1

   How would you ensure a modal, popover, or drawer in the Word web commenting UI works for keyboard and assistive technology users?

   StaffOnsite/Full Loop - UX QualityAccessibilityMicrosoft-specific

   Context: Word web commenting UI

   How to answer: A strong answer would focus on proper focus management, ARIA attributes, and keyboard interaction. This includes trapping focus within the modal, restoring focus to the trigger element upon close, and ensuring the modal is dismissible via the Escape key. Crucially, it would involve using appropriate ARIA roles (e.g., `role="dialog"`, `aria-modal="true"`) and labels (`aria-labelledby`, `aria-describedby`) to convey the modal's purpose and state to screen readers. Keyboard navigation within the modal should follow standard tab order, and the modal should be programmatically hidden from the accessibility tree when not active.

2. Q2

   Design an accessible admin console for the Outlook inbox. Explain focus order, labels, announcements, and keyboard interaction

   MediumOnsite/Full Loop - AccessibilityAccessibilityMicrosoft-specific

   Context: Outlook inbox

   How to answer: A strong answer will detail a logical focus order that follows visual layout, ensuring all interactive elements are reachable via keyboard. It will emphasize clear, descriptive ARIA labels and `aria-describedby` for complex elements, providing sufficient context for screen reader users. Crucially, it will explain how dynamic content changes and form submissions trigger `aria-live` region announcements, and outline comprehensive keyboard interactions including Tab, Shift+Tab, Enter, Space, and arrow keys for navigation within components like tables or tree views, adhering to WAI-ARIA authoring practices.

3. Q3

   How would you handle accessible errors, validation hints, and recovery paths in a high-stakes bulk action toolbar?

   MediumOnsite/Full Loop - UX QualityAccessibilityMicrosoft-specific

   Context: Edge settings page

   How to answer: For accessible errors, I would use ARIA live regions (e.g., `aria-live="assertive"`) to announce validation failures immediately without interrupting the user's flow, linking errors to their respective fields using `aria-describedby` or `aria-labelledby`. Validation hints should be provided proactively using `aria-describedby` to associate them with input fields, appearing on focus or hover, and clearly indicating expected formats or constraints. For recovery paths, I'd ensure clear, actionable error messages with direct links or buttons to resolve issues, such as 'Retry' or 'Edit Invalid Items,' making sure these controls are keyboard-navigable and have appropriate ARIA labels. A summary of all errors at the top of the form or toolbar, with anchor links to each problematic field, would also be crucial.

4. Q4

   The design for the SharePoint document library uses subtle icons and gestures. How would you negotiate an accessible implementation with design?

   HardOnsite/Full Loop - ArchitectureAccessibilityMicrosoft-specific

   Context: SharePoint document library

   How to answer: A strong candidate would first emphasize understanding the specific accessibility issues posed by subtle icons/gestures (e.g., for low vision, motor impairment, screen reader users). They would then propose a collaborative negotiation strategy, focusing on offering concrete, accessible alternatives that meet design goals (e.g., high-contrast icons, keyboard navigable actions, ARIA labels, visible focus states). The discussion should center on educating design about accessibility standards (WCAG) and Microsoft's commitment, demonstrating how accessibility enhances usability for everyone, and finding a balanced solution that preserves aesthetic intent while ensuring inclusivity. Prioritization of critical functionalities and phased implementation could also be discussed.

5. Q5

   Design an accessible upload flow for the Power BI report view. Explain focus order, labels, announcements, and keyboard interaction

   MediumOnsite/Full Loop - ArchitectureAccessibilityMicrosoft-specific

   Context: Power BI report view

   How to answer: A strong candidate would design an upload flow that prioritizes keyboard navigation and screen reader compatibility. They would detail a logical focus order, ensuring interactive elements are tabbable and follow a visual left-to-right, top-to-bottom flow. Labels would be explicit and programmatically associated with their controls, using `aria-label` or `aria-labelledby` for custom components. Screen reader announcements would provide real-time feedback on upload progress, success, or failure, leveraging ARIA live regions. Keyboard interactions would include standard keys like Enter/Space for activation, Escape for closing modals, and arrow keys for navigation within lists or radio groups.

6. Q6

   A screen reader user cannot complete the Planner board. How would you triage, reproduce, and fix the issue?

   HardOnsite/Full Loop - AccessibilityAccessibilityMicrosoft-specific

   Context: Planner board

   How to answer: Triage would involve gathering user reports, identifying the specific screen reader (e.g., NVDA, JAWS, Narrator), browser, and exact steps where the user gets stuck. Reproduction requires setting up the identified environment and attempting to navigate the Planner board using only keyboard and the specified screen reader. Fixing would likely involve inspecting the DOM for missing ARIA attributes (e.g., `aria-labelledby`, `aria-describedby`, `aria-roledescription`), incorrect tab order, or inaccessible custom controls, then implementing the necessary semantic HTML5 elements or ARIA roles and properties to ensure proper communication with the assistive technology.

7. Q7

   When would you use ARIA in the Word web commenting UI, and when would you remove it in favor of native semantics?

   StaffOnsite/Full Loop - UX QualityAccessibilityMicrosoft-specific

   Context: Word web commenting UI

   How to answer: ARIA should be used when native HTML elements cannot convey the necessary semantic meaning or interactive behavior for accessibility, such as custom UI components in the Word web commenting system (e.g., a custom emoji picker, a complex threaded reply widget, or a custom button with a dynamic state like 'resolve comment'). It's essential for roles, states, and properties that native HTML lacks. ARIA should be removed or avoided when a native HTML element already provides the equivalent semantic meaning and accessibility features, adhering to the 'first rule of ARIA' (use native HTML whenever possible). This applies to standard interactive elements like buttons, links, form inputs, and headings within the commenting UI, which inherently provide accessibility via the browser's accessibility tree.

8. Q8

   Explain how reduced motion changes your component API, QA process, and release checklist for the Teams chat pane

   MediumOnsite/Full Loop - ArchitectureAccessibilityMicrosoft-specific

   Context: Teams chat pane

   How to answer: Reduced motion significantly impacts component APIs by requiring explicit `prefers-reduced-motion` media query checks or a prop-driven approach to disable or simplify animations. The QA process must include dedicated test cases for both motion and reduced motion settings, verifying visual stability and functionality without distracting animations. The release checklist needs an item to confirm reduced motion compliance across all new features, ensuring accessibility standards are met before deployment to a large user base like Microsoft Teams.

9. Q9

   The design for the Excel web grid uses subtle icons and gestures. How would you negotiate an accessible implementation with design?

   HardOnsite/Full Loop - UX QualityAccessibilityMicrosoft-specific

   Context: Excel web grid

   How to answer: A strong candidate would first identify the core accessibility issues with subtle icons and gestures (e.g., visual impairment, motor impairment, cognitive load). They would then propose a collaborative negotiation strategy, focusing on offering concrete, accessible alternatives (e.g., keyboard shortcuts, text labels, high-contrast options, ARIA attributes) while preserving design intent where possible. The discussion should emphasize educating design on accessibility standards (WCAG) and Microsoft's own inclusive design principles, framing accessibility as an enhancement rather than a compromise. Finally, they would suggest an iterative approach involving user testing with diverse groups to validate solutions.

10. Q10

    How would you ensure a modal, popover, or drawer in the Azure portal dashboard works for keyboard and assistive technology users?

    StaffOnsite/Full Loop - ArchitectureAccessibilityMicrosoft-specific

    Context: Azure portal dashboard

    How to answer: A strong answer would focus on proper focus management, ARIA attributes, and keyboard navigation. This includes trapping focus within the modal, restoring focus to the triggering element upon closure, and using appropriate ARIA roles and states (e.g., `role="dialog"`, `aria-modal="true"`, `aria-labelledby`, `aria-describedby`). Keyboard navigation must allow users to close the modal (e.g., via Esc key) and interact with all elements inside it using Tab and Shift+Tab, while preventing interaction with the background content. Semantic HTML elements should be prioritized where possible.

11. Q11

    Audit the Office template gallery for skip links. What checks would you run manually and which would you automate?

    MediumOnsite/Full Loop - AccessibilityAccessibilityMicrosoft-specific

    Context: Office template gallery

    How to answer: A strong answer would first define skip links and their purpose in web accessibility, specifically for keyboard and screen reader users navigating repetitive content like headers and navigation. For the Office template gallery, manual checks would involve keyboard navigation (Tab, Shift+Tab, Enter) to verify skip link visibility on focus, correct target jumping to the main content area, and proper focus management after activation. Automated checks would focus on the presence of skip links in the DOM (e.g., `<a>` tags with `class="skip-link"` or `id="skip"`), their `href` attributes pointing to valid main content regions (e.g., `#main-content`), and ensuring they are visually hidden until focused using CSS techniques like `sr-only` classes. The candidate should also mention checking for multiple skip links if there are multiple repetitive blocks.

12. Q12

    The Teams chat pane has a visual regression after a design-system update. How would you isolate whether responsive typography is the root cause?

    EasyPhone/Virtual Technical ScreenCSSMicrosoft-specific

    Context: Teams chat pane

    How to answer: A strong candidate would first describe using browser developer tools (e.g., Edge/Chrome DevTools) to inspect the affected elements in the Teams chat pane. They would then focus on CSS properties related to font-size, line-height, and media queries. Specifically, they would look for `font-size` values that are relative units (e.g., `rem`, `em`, `vw`) or defined within `@media` rules, and then disable or modify these properties to see if the visual regression resolves. Finally, they would suggest checking the design system's documentation or changelog for recent responsive typography updates.

13. Q13

    Design a CSS strategy for an embedded widget in the Excel web grid that must coexist with third-party page styles

    MediumOnsite/Full Loop - Frontend FundamentalsCSSMicrosoft-specific

    Context: Excel web grid

    How to answer: A strong strategy involves using Shadow DOM for complete style encapsulation, ensuring the widget's styles are isolated from the host page and vice-versa. Alternatively, a less robust but often sufficient approach is to use highly specific CSS selectors with a unique root ID/class for the widget, combined with `all: unset` or `all: initial` on the widget's root element to reset inherited styles. Employ BEM or similar methodologies for internal widget styling to maintain organization and prevent conflicts within the widget itself. Finally, consider using CSS custom properties (variables) for configurable theming if the host page needs to influence certain widget styles without breaking encapsulation.

14. Q14

    Build the layout strategy for the Office template gallery using CSS animations. What rules would you choose and where could the approach break?

    EasyOnsite/Full Loop - CodingCSSMicrosoft-specific

    Context: Office template gallery

    How to answer: A strong layout strategy for the Office template gallery would involve using CSS Grid for the primary layout, allowing for flexible arrangement of template cards. For animations, `transform` properties (e.g., `scale`, `translate`) combined with `transition` for smooth hover effects or `animation` for more complex entry/exit sequences are ideal. Key rules include using `will-change` for performance hints, `prefers-reduced-motion` for accessibility, and `overflow: hidden` on containers to manage card expansion. This approach could break if there are too many concurrent complex animations, leading to performance issues, or if grid items have highly variable, unpredictable content sizes that disrupt the uniform grid flow.

15. Q15

    How would you create a themeable component for the SharePoint document library using aspect-ratio and object-fit without creating global style regressions?

    MediumPhone/Virtual Technical ScreenCSSMicrosoft-specific

    Context: SharePoint document library

    How to answer: To create a themeable component without global regressions, encapsulate styles using CSS Modules or scoped CSS-in-JS solutions like Styled Components or Emotion. Define CSS variables (custom properties) for theme-related values (colors, fonts, spacing) within the component's scope. Utilize `aspect-ratio` for maintaining image or video proportions responsively, and `object-fit` (e.g., `cover` or `contain`) to control how the content fills its allocated space within the defined aspect ratio. Provide a clear API for theme customization, allowing SharePoint's theming engine to inject values into these CSS variables.

Practice these with instant AI feedback in a live mock interview → Start a Microsoft Full Stack Engineer mock

Practice coding with clear communication; show a growth mindset; know your past projects deeply

Other roles at Microsoft

Full Stack Engineer interviews at other companies