Talent Map Brief: Cloud & Platform Engineering in Seattle

Literal role requirements

• Platform/infrastructure ownership defined by the role
• Required cloud or distributed-systems depth only where explicit
• Seniority/scale expectations
• Location/hybrid constraints

Title families to test

• Platform Engineer
• Site Reliability Engineer
• Cloud Engineer
• Infrastructure Engineer
• Distributed Systems Engineer
• DevOps Engineer
• Production Engineer

Donor categories

• Hyperscale cloud organizations
• Large consumer/product infrastructure teams
• Developer-tooling and observability companies
• Data infrastructure companies
• Growth-stage SaaS/platform organizations

Geography bands

• Seattle
• Bellevue
• Redmond
• Kirkland / Eastside
• Remote Pacific Northwest talent if role policy permits

Evidence and source lanes

• Direct-title search
• Donor-company platform-team mapping
• GitHub/open-source infrastructure evidence
• Conference/talk/technical-writing evidence
• ATS rediscovery
• Adjacent distributed-systems search
• Licensed provider expansion

Questions that determine whether the market is actually scarce

• Is a specific cloud required?
• Does the role need SRE operations depth or platform product ownership?
• How much Kubernetes/IaC depth is mandatory?
• Is hyperscale experience required or a proxy for production complexity?
• What hybrid radius is realistic?

Actionable search plan

1. Separate SRE, platform, cloud, and distributed-systems archetypes.
2. Map work context and scale rather than brands alone.
3. Use open-source evidence as augmentation, never a gate.
4. Calibrate on production ownership versus tooling familiarity.
5. Measure adjacent-title unique contribution before declaring direct-title scarcity.

Related SourcingOS guidance