Loading
Comparison · dataset August 2026

Chef / Cook vs Software Engineer: which is more exposed to AI?

49 points apart. These are not comparable risk profiles.

Software Engineer sits at 67% time-weighted AI exposure against 18% for Chef / Cook, a 49-point gap driven by the 32% of software engineer work time that current models can already substitute outright. Chef / Cook holds a larger human-critical core — 78% of the role's time sits in work like "food preparation and cooking" that models score poorly on. The two sit in different families — Hospitality & Food and Computer & Math — so any move between them is a career change, not a lateral step.

49PP GAP

Seven dimensions, side by side.

METRICCHEF / COOKSOFTWARE ENGINEERDELTA
AI exposure18%67%49pp gap
Resilience score91/10069/10022pt gap
Substitutable work time0%32%Fully automatable today
Human-critical work time78%20%Models score poorly here
Median salary$58k$132k$74k apart
10-year growth9%17%Software Engineer
US workforce1.4M1.8MBLS OEWS
Task level

What actually creates the gap.

Software Engineers spend 32% of their time-weighted week on tasks a current model can produce end-to-end, against 0% for Chef / Cooks. The single largest contributor is "write boilerplate & crud code", graded at 92% and worth 14% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

Chef / Cook
MOST EXPOSED TASKS
    HUMAN-CRITICAL CORE
    • Food preparation and cooking4% · 48% time
    • Kitchen team leadership8% · 16% time
    • Guest interaction and feedback10% · 6% time
    Software Engineer
    MOST EXPOSED TASKS
    • Write boilerplate & CRUD code92% · 14% time
    • Generate unit tests from specs88% · 8% time
    • Author documentation85% · 6% time
    • Translate code between languages81% · 4% time
    HUMAN-CRITICAL CORE
    • Mentor junior engineers11% · 3% time
    • Negotiate scope with stakeholders14% · 5% time
    • Triage production incidents22% · 4% time
    What transfers

    Both roles lean on procedural, creative, cognitive — that is the part of your experience that travels intact. The real divide is manual: Chef / Cooks score 96 there against 6 for Software Engineers, a 90-point spread. That is the gap you would actually have to close.

    DIMENSIONCHEF / COOKSOFTWARE ENGINEER
    Manual966
    Social7232
    Judgement7441
    Switching between them
    HighDIFFICULTY

    Neither role lists the other as a mapped adjacent career, and the capability profiles sit 44 points apart on average. Treat a move between them as a genuine career change with a retraining cost, not as a hedge against AI exposure.

    Score your own exposure in 8 questions →

    Common questions.

    Is Chef / Cook or Software Engineer more at risk from AI?

    Software Engineer. It scores 67% time-weighted AI exposure against 18% for Chef / Cook — a 49-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 0% for Chef / Cooks.

    Which pays more, Chef / Cook or Software Engineer?

    Software Engineer, by roughly $74k at the median ($132k versus $58k). 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 chef / cook switch to being a software engineer?

    Neither role lists the other as a mapped adjacent career, and the capability profiles sit 44 points apart on average. Treat a move between them as a genuine career change with a retraining cost, not as a hedge against AI exposure.

    Which role is growing faster, Chef / Cook or Software Engineer?

    Software Engineer, at 17% projected ten-year growth versus 9% — an 8-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.

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