Linkedin Article Draft · Jul 20–26, 2026 → Jul 20–26, 2026
Data quality flag — this report contains a known defect
A median_salary Trend value was displayed where job_postings_count was intended (e.g. 'snowflake mentions moved +15000 this week, to 172500' — 172500 is a median salary, not a mention count). Root cause: Trend queries in ReportingAgent filtered by period but not by metric. Fixed 2026-08-15 (see docs/MAINTENANCE.md, tests/test_metric_isolation.py). The underlying job_postings_count data for W30 was never wrong -- only this report's narrative text. Left unedited rather than silently corrected; flagged here instead.
software engineer: what the Jul 20–26, 2026 counts show, and why not to over-read them.
Weekly read on Jul 20–26, 2026, with the misses included
I run a small intelligence system over job postings. It counts, it forecasts, and then it
grades its own forecasts. This is the Jul 20–26, 2026 read.
The movement
| Signal | Type | Job postings this week | Change | Direction |
|---|---|---|---|---|
| software engineer | role | 29 | +29 (+100%) | up |
| security | skill | 21 | +21 (+100%) | up |
| data analysis | skill | 13 | +13 (+100%) | up |
| automation | skill | 8 | +8 (+100%) | up |
| aviation safety inspection | skill | 0 | −8 (-100%) | down |
The forecast
_No forecast currently clears the governance rules._
The grade
Track record: 72 forecasts scored, mean accuracy 0.74, calibration delta -0.12 — the system has been overconfident and has lowered its own confidence accordingly.
What I would actually do
- individual: Build capability in risk management (skill). Demand is rising 0% across the last 6 observed periods, and the 4w forecast holds that direction. (confidence 0.44)
- individual: Build capability in stakeholder management (skill). Demand is rising 5% across the last 6 observed periods, and the 4w forecast holds that direction. (confidence 0.39)
Recommended images: the movement table as a simple bar chart; the accuracy record over time.
Call to action: if you track a signal that contradicts this, I would rather see it than not.
Evidence Summary
- Jobs analyzed: 40
- Companies: 2
- GitHub projects: 0
- News articles: 0
- Research papers: not collected
- Distinct sources: 2
- Last updated: 2026-07-25T10:45:04+00:00
- Confidence: not available — no linked forecast
Publish to scheduler
Pushes this report as a LinkedIn draft into your scheduler's Awaiting Publish queue. Held there for your approval — nothing goes live automatically.
What this does not claim ▸
I cannot see hiring outcomes, only postings. I cannot see sources I have not connected. And a four-week linear forecast cannot see an inflection coming — by construction, it will miss the turn. Those limits are in the system's own records, not just this post.
How we know
Evidence
Confidence
Source diversity
2 sources
93% from one source — treat as narrow
Last updated
2026-07-26
Reality validation
Not yet scored against reality.
How this forecast was made
- Approach
- Linear trend fitted to recent weekly counts, with a range to account for uncertainty
- Can it be edited?
- No — forecasts are locked at publication and scored as-is
Primary sources