The Skills Market Today: C# Is the Public Lead
Today's Job Index shows 55 new roles. After filtering broad soft-skill tags, the public demand signal is specific: C#, Cybersecurity, OKRs, LLM, Figma - skills you can prove, not titles you can claim.
The old labor market bought titles and time. The one taking shape buys verified capability. Today's Job Index crawl landed 55 new roles, and after the 7-day category cooldown, the publishable public lead is C# - not because it is the raw volume champion, but because the rotation rule keeps the public headline honest and non-repeating.
What today's index shows#
The operating-system local export for 2026-07-25 has 55 new roles in the refreshed window. Across that window, 36 publishable atomic skills appear in the public signal.
The raw audit list is still topped by broad language - communication and other soft-skill tags that are useful for internal review. They are not what we publish as demand proof.
Filter those broad labels out and the volume board comes into focus. Volume is context; public lead is rotation:
| Skill | Roles in today's window | Note |
|---|---|---|
| Cybersecurity | 10 | volume only (not today's public lead) |
| OKRs | 10 | volume only |
| LLM | 6 | volume only |
| C# | 5 | public lead after category rotation |
| Figma | 5 | volume only |
| Ruby | 5 | volume only |
Today's public lead is C# (5 roles) after the 7-day category cooldown. Cybersecurity and OKRs are louder on raw count; they stay in the volume board so the index stays honest. The market is still buying a capability you can demonstrate, not a department name.
Why the skill list matters more than the titles#
The more useful pattern is that the same capability keeps crossing very different job labels. A title can hide wildly different work. A skill signal travels across teams and seniority. That is why proof beats a static credential: hiring managers and clients are buying the thing you can demonstrate, not the label you last held.
Skills over titles - the operating move#
If you are hiring, stop filtering by title overlap and start scoring by demonstrated skill. Your candidate pool widens and your false-positive rate drops.
If you are job searching or going fractional, pick one skill you can demonstrate this week. Publish the artifact. Attach it to a network where people already need that skill. Repeat for 90 days. One artifact is a fluke. A short chain of them is a signal.
Close#
If you are building this way, Rocket is where that proof turns into introductions, meetings, and repeat work - and Ember is there to help you practice the conversations that convert.
- Start free, upgrade when ready: Pricing / membership
- See member wins: Wins
- Stuck or need a human? Get help (CS help line)
- Already in? Log in and finish membership if checkout stalled
Sources#
- Job Index export: job-index-2026-07-25.json (snapshot 2026-07-25, local operating-system Job Index).
- Use publishable_top_skills for public output; broad soft-skill tags retained for audit only.
- Do not invent week-over-week deltas or market-wide coverage percentages.