WeSearch

Predicting AI job exposure

·8 min read · 0 reactions · 0 comments · 57 views
Predicting AI job exposure
TL;DR · WeSearch summary

The article discusses the challenges of predicting job exposure to AI and automation. It highlights that while technology can disrupt industries, historical data shows that some jobs may remain stable or even grow despite automation. The author argues that the relationship between technology and employment is complex and often unpredictable.

Key facts
About this source

Benedict Evans files mainly under business.

Original article
Benedict Evans
Read full at Benedict Evans →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherBenedict Evans
Canonical URLhttps://www.ben-evans.com/benedictevans/2026/5/24/ai-job-exposure
Publication timeSun, 24 May 2026 20:35:51 +0000
Retrieval time2026-05-24T20:37:34.510Z
Last seen2026-05-24T20:37:34.510Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster5GaXeD76MaH-
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Predicting AI job exposure It would be really nice if we had some way to analyse which jobs, companies and industries were exposed to AI, and if we could assign scores, and build charts, and map that against the progress of large language models. We know, in principle, that like every other big wave of technology, AI is bound to destroy some jobs and create others. But which ones? In the last three years a bunch of people have been very busy crunching census data, making tables and building viral charts. I think this is mostly impossible: I think this is an exercise in predicting something that cannot be predicted. The simplest way to see the problem is to back-test this against other big technology shifts in the past.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Benedict Evans.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Benedict Evans