Loading
Comparison · dataset August 2026

Curriculum Developer vs School Counselor: which is more exposed to AI?

44 points apart. These are not comparable risk profiles.

Curriculum Developer sits at 66% time-weighted AI exposure against 22% for School Counselor, a 44-point gap driven by the 46% of curriculum developer work time that current models can already substitute outright. School Counselor holds a larger human-critical core — 66% of the role's time sits in work like "respond to student crises" that models score poorly on. Both roles sit inside Education, so the exposure difference reflects task design rather than a change of field.

44PP GAP

Seven dimensions, side by side.

METRICCURRICULUM DEVELOPERSCHOOL COUNSELORDELTA
AI exposure66%22%44pp gap
Resilience score48/10082/10034pt gap
Substitutable work time46%15%Fully automatable today
Human-critical work time28%66%Models score poorly here
Median salary$74k$62k$12k apart
10-year growth2%4%School Counselor
US workforce200k330kBLS OEWS
Task level

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 15% for School Counselors. 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.

Curriculum Developer
MOST EXPOSED TASKS
  • Draft lesson plans and units88% · 16% time
  • Generate assessments and rubrics86% · 12% time
  • Produce student materials84% · 10% time
  • Map content to standards76% · 8% time
HUMAN-CRITICAL CORE
  • Train educators on new curriculum15% · 4% time
  • Pilot with teachers and iterate18% · 8% time
  • Judge what works for real classrooms22% · 6% time
School Counselor
MOST EXPOSED TASKS
  • Build class schedules80% · 6% time
  • Maintain student records76% · 4% time
  • Draft recommendation letters74% · 5% time
HUMAN-CRITICAL CORE
  • Respond to student crises5% · 14% time
  • Counsel students one-on-one8% · 26% time
  • Mediate conflicts and bullying cases10% · 10% time
What transfers

Both roles lean on judgement — that is the part of your experience that travels intact. The real divide is social: School Counselors score 94 there against 50 for Curriculum Developers, a 44-point spread. That is the gap you would actually have to close.

DIMENSIONCURRICULUM DEVELOPERSCHOOL COUNSELOR
Social5094
Creative5826
Procedural7244
Switching between them
ModerateDIFFICULTY

Neither role lists the other as a mapped adjacent career. With 27 points of average separation across capability dimensions, a move is realistic but not free: expect to deliberately rebuild the dimensions listed above rather than assume they carry.

Score your own exposure in 8 questions →

Common questions.

Is Curriculum Developer or School Counselor more at risk from AI?

Curriculum Developer. It scores 66% time-weighted AI exposure against 22% for School Counselor — a 44-point gap. 46% of curriculum developer work time is already fully substitutable by current models, versus 15% for School Counselors.

Which pays more, Curriculum Developer or School Counselor?

Curriculum Developer, by roughly $12k at the median ($74k versus $62k). 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 school counselor?

Neither role lists the other as a mapped adjacent career. With 27 points of average separation across capability dimensions, a move is realistic but not free: expect to deliberately rebuild the dimensions listed above rather than assume they carry.

Which role is growing faster, Curriculum Developer or School Counselor?

School Counselor, at 4% projected ten-year growth versus 2% — a 2-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.

Career families
Education
Methodology
Scores are time-weighted across each role's canonical O*NET tasks, graded against current frontier-model capability. How we score.