Principal DevEx Engineer, AWS Developer Experience
Amazon · Seattle, WA
$188,900–$330,500from the description
Jul 16, 2026
Seattle, WA
Jul 21, 2026
What this job asks for AI summary
A principal-level role focused on shaping how AI agents interact with AWS cloud services. The work involves hands-on building with AWS tools to evaluate the developer experience, then translating those findings into technical content, standards, and product direction that service teams adopt. It suits a senior engineer with deep experience in agentic tooling who can also influence product and engineering organizations across a large portfolio.
Senior level · 10+ years · San Francisco-Oakland-Hayward, CA · Full-time
Advertised as Principal, but the requirements read as Senior.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 2,600 people in the San Francisco-Oakland-Hayward, CA area plausibly meet what this posting asks for (software developers). range 770–3,900
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $190,744 (middle half $167,095–$224,501). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
Two salary ranges are listed: San Francisco, CA ($188,900–$330,500/yr) and Seattle, WA ($164,200–$287,400/yr). The higher SF range is reported; the Seattle range is $164,200–$287,400 annually.
The role is posted across at least two metros (San Francisco, CA and Seattle, WA); CBSA reflects the higher-comp SF location. The Seattle CBSA (35620 equivalent is 42660 Seattle-Tacoma-Bellevue, WA) is an equally valid primary location.
SOC classification is a judgement call: the role is primarily a developer-experience/developer-advocacy function — hands-on building, technical content creation, and product influence — rather than a pure software engineering IC role. 15-1252 is used because the JD emphasizes hands-on building and technical depth; 15-1299 (Computer Occupations, All Other) is a reasonable runner-up for the advocacy/strategy dimension.
The 'Principal' title is taken at face value for advertised seniority, but the actual requirements (10+ years, no explicit org-wide technical authority scope beyond influence) support a Senior-level assessment.
'Technical content writing' is listed as a required skill because the JD explicitly gates on it ('Experience writing high-quality technical content') in the Basic Qualifications section — it is a named, concrete capability even though it is not a tool name.
'Open source' and community credibility (speaking, technical following) appear only under Preferred Qualifications.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.