SQL Takes the Rotated Lead on a 182-Role Board
"2026-07-23 Job Index: 182 new roles. Public lead under 7-day category rotation is SQL (18 roles) - with volume still loud in Cybersecurity, OKRs, AWS, and Figma."
Today's crawl is not a title market. It is a skills market with a SQL headline.
The local Job Index for 2026-07-23 shows 182 new roles inside today's crawl window. Across that window, 44 atomic skills appear. Publishable lead under the 7-day category cooldown is SQL (18 roles). That is the public proof point - not because SQL is always the raw volume champion, but because rotation keeps the public lead honest and non-repeating.
What the board is buying#
| Skill (publishable) | Roles in window | Note |
|---|---|---|
| SQL | 18 | public lead (category rotation) |
| Cybersecurity | 38 | volume only |
| OKRs | 36 | volume only |
| AWS | 20 | volume (fast mover) |
| Figma | 16 | volume only |
Skills moving fastest since yesterday include AWS and C#. Counts are from inside the crawl window, not a share of the whole market. The direction is the useful part: companies are buying specific, demonstrable skills - not titles.
We rotate the public headline so the same Job Index category does not own the blog and email lead for more than a few days. Loud volume skills still matter; they sit on the board as context, not as today's public lead.
Why SQL as the public lead still matters#
SQL is the buyer-facing language for truth in the data layer - queries, joins, warehouse fluency, the ability to turn messy tables into decisions. When the crawl rotates to SQL, the signal is not "everyone wants a DBA." It is that operators are paying for people who can enter a dataset, name the skill unit, and ship a scoped answer without a full-time headcount story.
The volume stack underneath (cyber / OKRs / AWS / Figma) is the proof inventory. Fractional operators win when they package one of those units with a short artifact a buyer can evaluate in a minute.
What to do this week#
- Pick one skill you already shipped. Not the one on the wishlist. If SQL is yours, show a real query/notebook/dashboard - not a certification line.
- Publish one artifact. Repo, teardown, scoped note, short walkthrough.
- Price the unit, not the year. Skills language is a product wrapper for that unit.
- Route through a network. Proof without distribution dies quiet.
If you are hiring: score for demonstrated skill, not title overlap.
If you are selling work: lead with the skill board above and a scoped offer that fits in one call.
Close#
If you are building this way, Rocket turns proof into introductions and repeat work. Need a hand with login or billing - support is live.
Sources#
- Job Index export:
data/job_index/exports/job-index-2026-07-23.json(snapshot 2026-07-23, decision=fresh_signal, new_jobs=182). - Lead skill receipt:
articles/2026-07-23/lead-skill.json(sql / data_engineering, count=18). - Claims:
articles/2026-07-23/CLAIMS.json(subject/preheader align email + blog). - Email seed:
articles/2026-07-23/email-seed.md(same public lead + volume board). - No fabricated market-wide percentages; counts are crawl-window only.
Rocket membership
Turn today's skill map into paid work
Open Rocket membership for introductions, Ember, and the Job Index loop that matches demand to people who already need the skill.
Open Rocket membership →