ML Engineer vs Software Engineer: which is more exposed to AI?
Software Engineer carries 11 points more AI exposure than ML Engineer.
Software Engineer sits at 67% time-weighted AI exposure against 56% for ML Engineer, an 11-point gap driven by the 32% of software engineer work time that current models can already substitute outright. ML Engineer holds a larger human-critical core — 36% of the role's time sits in work like "research direction and hypothesis setting" that models score poorly on. Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.
Seven dimensions, side by side.
What actually creates the gap.
Both roles hand a similar slice of the week to substitutable work — 28% for ML Engineers, 32% for Software Engineers — but it is different work. ML Engineer exposure concentrates in "build data preprocessing pipelines"; Software Engineer exposure concentrates in "write boilerplate & crud code". Two roles can share a score and face completely different disruption timelines.
- Build data preprocessing pipelines82% · 12% time
- Write model training code78% · 16% time
- Research direction and hypothesis setting18% · 8% time
- Model architecture design28% · 16% time
- Production reliability and serving31% · 12% time
- Write boilerplate & CRUD code92% · 14% time
- Generate unit tests from specs88% · 8% time
- Author documentation85% · 6% time
- Translate code between languages81% · 4% time
- Mentor junior engineers11% · 3% time
- Negotiate scope with stakeholders14% · 5% time
- Triage production incidents22% · 4% time
Both roles lean on procedural, cognitive, creative — that is the part of your experience that travels intact. The real divide is judgement: ML Engineers score 78 there against 41 for Software Engineers, a 37-point spread. That is the gap you would actually have to close.
| DIMENSION | ML ENGINEER | SOFTWARE ENGINEER |
|---|---|---|
| Judgement | 78 | 41 |
| Cognitive | 94 | 78 |
Software Engineer appears in our dataset as a mapped adjacent career for ML Engineers: the move raises exposure by 11 points, landing at 67%. Switch difficulty reads low — capability profiles are 17 points apart on average and both sit in the same family.
Score your own exposure in 8 questions →Common questions.
Is ML Engineer or Software Engineer more at risk from AI?
Software Engineer. It scores 67% time-weighted AI exposure against 56% for ML Engineer — an 11-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 28% for ML Engineers.
Which pays more, ML Engineer or Software Engineer?
ML Engineer, by roughly $26k at the median ($158k versus $132k). Note that the higher-paying role here is also the less AI-exposed one, which matters if you are weighing pay against durability.
Can a ml engineer switch to being a software engineer?
Software Engineer appears in our dataset as a mapped adjacent career for ML Engineers: the move raises exposure by 11 points, landing at 67%. Switch difficulty reads low — capability profiles are 17 points apart on average and both sit in the same family.
Which role is growing faster, ML Engineer or Software Engineer?
ML Engineer, at 28% projected ten-year growth versus 17% — an 11-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.