Microsoft's Wrocław frontend platform team maintains the design system that powers 12 internal product teams. This is a high-leverage role: every component, token decision, and API change you make propagates instantly across thousands of screens - some used by millions of Microsoft 365 customers.

You will own the component library in Storybook, driving API consistency, accessibility compliance (WCAG 2.2 AA), and theming. A significant part of your time will involve working with the design team (Figma + Tokens Studio) to translate design decisions into typed CSS custom properties and React component props. You will publish versioned packages to the internal npm registry and write migration guides when breaking changes are necessary.

Cross-functional engagement is key: you will participate in weekly syncs with 12 consumer product teams, triage accessibility bug reports, and maintain a public changelog and RFC process for new components. You will also onboard and mentor two developers rotating into the design systems team from product squads.

Experience with ARIA patterns, focus management, and screen reader testing (NVDA, VoiceOver) is essential - we treat accessibility as a first-class deliverable, not a checkbox.

• React 18
• TypeScript 5
• Storybook 8
• Tailwind CSS 4
• Radix UI (primitives)
• Jest 29
• Testing Library
• Playwright
• Turborepo
• pnpm workspaces
• GitHub Actions
• Figma (Tokens Studio)
• axe-core
• CSS Custom Properties
• ARIA specification

Step 1 - Recruiter call (30 min): logistics, background, relocation.

Step 2 - UI architecture interview (60 min, live): we discuss your approach to component API design, theming architecture, and managing breaking changes across a large consumer base. Bring examples from your own work.

Step 3 - Live coding - React (75 min): build an accessible, composable modal component from scratch using React + TypeScript. We evaluate API ergonomics, keyboard navigation, focus trapping, ARIA attributes, and test coverage.

Step 4 - Cross-functional panel (60 min, two engineers + one product designer): scenario-based questions - how do you handle a product team asking for a one-off component that does not fit the system? How do you prioritise which components to build next? How do you communicate deprecations?

Step 5 - Offer: Microsoft runs a 5-business-day SLA from final round to offer.