The buyer question
Which side of Seattle's cloud split does the mandate sit on — hyperscaler platform engineering in the Amazon and Microsoft home ecosystem, or enterprise cloud adoption and migration — and which infrastructure decisions, operating boundaries and results will the candidate personally own?
What the public record shows
The hyperscaler anchor is corporate record: Amazon's Puget Sound headquarters supports 80,000 employees in the region, and company-wide in Washington Amazon had more than 95,000 full- and part-time employees and supported more than 250,000 indirect jobs in 2025, after investing more than $400 billion in the state.
The investment climate is equally corporate record: in fiscal 2025 Microsoft is on track to invest approximately $80 billion to build out AI-enabled datacenters to train AI models and deploy AI and cloud-based applications around the world, with more than half of that investment in the United States. Employer-scale and investment facts document the ecosystem's density; they measure no employer-specific candidate pool, salary levels or vacancy durations.
What changes in this market
Seattle's cloud market splits between building the platforms and consuming them, and evidence does not transfer. Hyperscaler platform mandates prove themselves in services run at planetary scale — availability, efficiency and correctness owned inside AWS- or Azure-class engineering. Enterprise cloud mandates prove themselves in migrations and workloads delivered — cost, reliability and operating-model outcomes for the consuming business. AI-infrastructure mandates prove themselves in capacity and efficiency of the new AI fleets the investment records describe. A candidate's hyperscaler tenure does not certify enterprise transformation skills, nor the reverse; a brief that says 'cloud experience in Seattle' selects none of these tests until side, boundary and owned results are named.
KiTalent's mandate analysis
- Name the side of the split — hyperscaler platform engineering, enterprise cloud adoption, or AI infrastructure — and the service or workload in scope.
- For hyperscaler mandates, ask for services run at scale with the availability and efficiency outcomes personally owned.
- For enterprise mandates, ask for migrations and workloads delivered with cost and operating-model outcomes.
- For AI-infrastructure mandates, ask for capacity and efficiency records on AI-class fleets.
- Treat headcount and investment figures as ecosystem facts; test compensation and availability against the live mandate.
Where the public record stops
The cited sources are Amazon's official About Amazon news page on its Washington investment and Microsoft's official blog on its FY2025 AI infrastructure investment. They document employment, investment and build-out plans — not candidate availability, compensation or time-to-hire for any Seattle employer. Test those points against the live mandate.
Sources
- About Amazon: Puget Sound headquarters employment
- About Amazon: Washington investment and jobs
- Microsoft: FY2025 AI datacenter investment
- Microsoft: majority of investment in the United States
Related KiTalent research
- The Market Map Is Not the Shortlist: why market coverage and candidate assessment are separate decisions in an executive-search mandate
- How to Assess a Leader Beyond Competencies: a practical framework for testing judgment, evidence and operating context after the brief is defined

