AWS Owns Today's Rotated Lead on a 104-Role Board

Today's board is dense on language tags. That is not the story we ship. After the 7-day category cooldown, the public lead lands on a cloud platform skill you can prove in a deployment trail, not another soft label from the audit list.

Snapshot for 2026-08-05#

Local Job Index crawl: 104 new roles in a 183-role window. Publishable atomic skills in the public set: 46. Broad soft-skill tags still dominate the raw audit list; they stay out of the headline and out of the email subject.

About 30% of top-skill sample titles mention remote or distributed work in this window. Treat that as crawl-window noise, not a market-wide remote share.

Skills moving fastest since yesterday (volume deltas, not the public lead): Java (+9), Ruby (+7). Useful for triage. Not today's subject line.

Board A - volume (loudest publishable tags)#

Skill	Roles in today's window	Note
C#	24	Loudest volume (tied); programming_language lane
Ruby	24	Tied volume + strong day-over-day lift
Cybersecurity	20	Volume only; security category still rotated off public lead
SQL	19	Volume only; data_engineering lane
Python	17	Volume only; language lane cooled vs yesterday
JavaScript	16	Volume only

C# and Ruby are the dense tags in this window. That is the volume story - useful for hiring filters, not today's shippable lead while language and security categories are on cooldown.

Board B - public lead (rotated headline)#

Skill	Roles	Category	Why it ships
AWS	9	cloud_platform	Public lead after category cooldown; infrastructure proof you can show

AWS is today's public lead. Loud volume skills still matter for hiring filters; they are not the blog/email headline while language and security categories are on cooldown. The lead is a cloud-platform skill with 9 roles in the crawl - enough density to be real demand under rotation, not a one-off keyword spike.

What AWS as lead actually means#

When AWS owns the public lead, buyers are rarely shopping for "someone who listed AWS once on LinkedIn." They want infrastructure delivery you can show: a service map, a cost or reliability fix with numbers, IAM boundaries that survive review, or a deploy path that did not melt under load.

Titles will say platform engineer, backend, full stack, DevOps, or something messier. The unit of value is still a shipped surface in the cloud. If your last role said "ops" or "support" but you own a measured AWS change with a clear before/after, you are already in this market. If your title said "engineer" and you cannot walk an architecture decision or a blast-radius trail, the market will treat you as unproven.

Operating move this week#

Hiring: keep language volume (C#/Ruby) and cloud proof (AWS) in separate lanes. One title filter collapses both and raises false negatives.

Job search / fractional: ship one narrow AWS artifact - a service diagram with tradeoffs, a cost or latency fix with numbers, or a least-privilege IAM change with a rollback note - and attach it where people already buy that skill. One artifact is a fluke. A short chain is a signal.

Network: practice the walkthrough out loud before the high-stakes room. Proof without a clear ask still dies in the inbox.

Close#

If you are building this way, Rocket is where cloud proof turns into introductions, meetings, and repeat work - and Ember is there to rehearse the conversation that converts. When free limits bite, membership unlocks the full path via login → pricing (live multi-rail checkout; no invented /checkout SPA route).

Sources#

• Job Index export: job-index-2026-08-05.json (snapshot 2026-08-05, decision=fresh_signal, local OS Job Index).
• Public output uses publishable_top_skills only; broad soft-skill tags audit-only.
• Do not invent week-over-week market-wide coverage percentages; day deltas above are crawl-window only.