Evolution of Microsoft’s Testing Practices: From 1990s SDET/STE Model to Cloud‑Native Quality Engineering

In the 1990s Microsoft assigned each product team three distinct roles—Product Manager, Developer, and Tester—following a staffing ratio of Product : Development : Testing = 0.5 : 1 : 1. Testers were split into Software Design Engineer in Test (SDET) who built test infrastructure and wrote automated tests, and Software Test Engineer (STE) who executed those tests.

Although this model helped Windows and Office achieve commercial success, it eventually proved ineffective. The testing team’s deep expertise created a bottleneck; STEs had limited career growth, and the hand‑off of code from developers to SDETs to STEs increased cost and delayed releases.

Around the year 2000 Microsoft recognized the problem and merged the SDET and STE roles. SDETs took over both test development and execution, but the core issue persisted: SDETs could not keep up with the rapid influx of new features from developers.

With the rise of cloud services in the mid‑2000s, the company faced new pressures for faster delivery, continuous deployment, and high availability. Simply accelerating the existing testing process proved insufficient; testing became a critical bottleneck that consumed an entire iteration cycle.

To address this, Microsoft redefined software quality ownership, ensuring the Master branch remained release‑ready at all times, and promoted “test left‑shift” (more unit testing) and the elimination of flaky automated tests.

They also introduced “quality right‑shift” by establishing practices that protect production while guaranteeing quality directly in the production environment, since a perfect pre‑production replica was impossible.

The organization then adopted a “combined engineering” model, merging development and testing responsibilities into a single “engineer” role. This required bidirectional training: developers learned testing skills, testers learned design and coding, and managers learned end‑to‑end feature delivery.

Specialized tasks such as performance, security, and monitoring were handled by virtual teams (v‑teams) composed of senior engineers who provided expertise while remaining aligned with their feature teams.

Through careful, incremental change and the creation of these virtual teams, Microsoft reduced hand‑offs, increased accountability, and ultimately achieved a noticeable increase in feature delivery speed despite each engineer handling a broader set of responsibilities.