Curriculum Developer vs Librarian: which is more exposed to AI?
A 21-point gap separates these roles — Librarian is the more defensible seat.
Curriculum Developer sits at 66% time-weighted AI exposure against 45% for Librarian, a 21-point gap driven by the 46% of curriculum developer work time that current models can already substitute outright. Librarian holds a larger human-critical core — 46% of the role's time sits in work like "serve vulnerable patrons" that models score poorly on. Both roles sit inside Education, so the exposure difference reflects task design rather than a change of field.
Seven dimensions, side by side.
What actually creates the gap.
Curriculum Developers spend 46% of their time-weighted week on tasks a current model can produce end-to-end, against 28% for Librarians. The single largest contributor is "draft lesson plans and units", graded at 88% and worth 16% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.
- Draft lesson plans and units88% · 16% time
- Generate assessments and rubrics86% · 12% time
- Produce student materials84% · 10% time
- Map content to standards76% · 8% time
- Train educators on new curriculum15% · 4% time
- Pilot with teachers and iterate18% · 8% time
- Judge what works for real classrooms22% · 6% time
- Catalog and classify materials84% · 8% time
- Answer factual reference questions80% · 8% time
- Manage circulation records78% · 6% time
- Compile research guides76% · 6% time
- Serve vulnerable patrons10% · 12% time
- Run community programs14% · 14% time
- Defend intellectual freedom16% · 8% time
Both roles lean on cognitive, procedural, judgement — that is the part of your experience that travels intact. The real divide is social: Librarians score 76 there against 50 for Curriculum Developers, a 26-point spread. That is the gap you would actually have to close.
| DIMENSION | CURRICULUM DEVELOPER | LIBRARIAN |
|---|---|---|
| Social | 50 | 76 |
| Creative | 58 | 38 |
| Manual | 4 | 22 |
Curriculum Developer appears in our dataset as a mapped adjacent career for Librarians: the move raises exposure by 21 points, landing at 66%. Switch difficulty reads low — capability profiles are 16 points apart on average and both sit in the same family.
Score your own exposure in 8 questions →Common questions.
Is Curriculum Developer or Librarian more at risk from AI?
Curriculum Developer. It scores 66% time-weighted AI exposure against 45% for Librarian — a 21-point gap. 46% of curriculum developer work time is already fully substitutable by current models, versus 28% for Librarians.
Which pays more, Curriculum Developer or Librarian?
Curriculum Developer, by roughly $10k at the median ($74k versus $64k). Note that the higher-paying role here is also the more AI-exposed one, which matters if you are weighing pay against durability.
Can a curriculum developer switch to being a librarian?
Curriculum Developer appears in our dataset as a mapped adjacent career for Librarians: the move raises exposure by 21 points, landing at 66%. Switch difficulty reads low — capability profiles are 16 points apart on average and both sit in the same family.
Which role is growing faster, Curriculum Developer or Librarian?
Librarian, at 3% projected ten-year growth versus 2% — a 1-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.