AI and machine learning engineering is the field that builds systems capable of learning from data and making decisions or generating outputs without being explicitly programmed for each case. The structural pull at the field level is Creation. While individual roles within the field emphasise different gradients — a research scientist discovering new architectures, an MLOps engineer making production systems reliable, an applied scientist solving domain-specific problems — the field exists because someone has to bring intelligent systems into existence that did not exist before. The defining act is creating something new: a model that can see, a system that can speak, an agent that can reason, an algorithm that can predict. The move from nothing to something is what unifies the field, even as the "something" varies enormously in ambition and form.
Discovery sits tightly alongside Creation and in research-oriented roles is arguably the dominant pull. The frontier of AI research is genuinely unknown territory — nobody knows which architectures will scale, which training methods will produce emergent capabilities, or where the theoretical limits of current approaches lie. The researchers pushing those boundaries are doing Discovery work in its purest form: asking questions nobody has answered and sometimes finding that the answers reshape the field entirely. But even in applied engineering roles, Discovery is present — the iterative process of training a model, observing its behaviour, and understanding why it succeeds or fails on particular inputs is a cycle of hypothesis and experiment that borrows from scientific method, even when the engineer does not think of it that way.
🦊
There's a guide here if you want one
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
ML-expertise barrier to building AI applications
Current fact
The barrier
Building ML-powered applications required deep expertise, usually a graduate degree
What changed
Foundation-model APIs and AutoML detach the application layer from the research layer; building on pretrained models replaces training from scratch
Behaviours involved
Domain experts embed intelligent capabilities without an ML graduate apprenticeship
Building
Product builders composing foundation-model capabilities into working systems
Solving
Rapid model-application prototyping via APIs in hours not months
BuildingExperimenting
What this is based on
Foundation-model application startup explosion
AutoML open-source ecosystem (AutoGluon, MLJAR) lowering the modelling floor
How this could age
Low risk on direction; moderate risk on conflating application-building with frontier research
What it does not cover
Building on models is democratised; training frontier models remains concentrated in compute-rich orgs. Application floor dropped; research ceiling did not.
Assessed July 2026
Research-productivity barrier
Current fact
The barrier
ML experiments were slow and labour-intensive; researchers bottlenecked by experiment throughput
What changed
Agentic ML-engineering systems run experiments autonomously (AutoResearch ~700 experiments in two days; AIDE ML; MLE-STAR)
Behaviours involved
A single researcher directing agent fleets explores a far larger hypothesis space
ExperimentingResearching
Human sets the question and interprets; agents handle the experimental grind
AnalyzingHypothesizing
What this is based on
Karpathy AutoResearch (~700 experiments, ~20 training improvements, self-reported)
AI Scientist / AI Scientist-v2 autonomous research pipelines
How this could age
Low risk on direction; moderate risk on magnitude of genuine discovery
What it does not cover
Autonomous-research outputs incremental and quality-variable; amplify reach, do not replace judgment about which questions matter. Compute access gates who can run agent fleets.
Assessed July 2026
Technical-gatekeeping barrier to AI careers
Near-term projection
The barrier
A high-value AI career required being a technical ML researcher/engineer; policy/ethics/social-science backgrounds had no substantive path
What changed
Regulation (EU AI Act) and institutional maturation created governance, ethics, and safety-adjacent roles requiring AI literacy but not a research PhD
Behaviours involved
Governance specialists translating between technical systems and regulatory frameworks
BridgingRule-making
Ethics specialists identifying and remedying algorithmic harms
~1.5% of orgs believe they have adequate governance headcount
AI Safety Institutes creating government-adjacent roles
How this could age
Low risk on direction; moderate risk on whether every role carries real institutional power
What it does not cover
Roles still demand real AI literacy; in branding-driven orgs the role can be powerless.
Assessed July 2026
Jobs that did not exist five years ago
These are real jobs that exist now and did not exist before the current wave of AI.
New title
LLMOps / AI Platform Engineer
Builds and operates infrastructure serving, monitoring, and cost-managing LLM-based production systems. Prompt management, output monitoring, inference-cost control, guardrails.
Role emerged rapidly since 2023 with generative-AI deployment; distinct from traditional MLOps · current fact
New title
AI Safety / Alignment Researcher
Works on ensuring AI systems do what humans intend and do not cause harm. Theoretical, empirical (red-teaming, evals), and applied (guardrails).
Field barely existed a decade ago; ~55% reported job growth; dedicated employers (frontier labs, AI Safety Institutes) · seen in the wild
New title
AI Ethics & Governance Specialist
Ensures AI systems are fair, transparent, accountable, and compliant with emerging regulation; builds governance structures at scale.
Regulation-created (EU AI Act); AI governance market ~$890.6M (2024) -> ~$5.77B (2029); ~1.5% of orgs have adequate governance headcount · current fact
New title
AI Evaluations Engineer / Red-teamer
Designs evaluation frameworks and adversarially tests models for dangerous or unintended capabilities.
Emerging specialisation distinct from general ML engineering; growing with safety-and-evals demand · early signal
Familiar title, new shape
AI Product Engineer (foundation-model application builder)
Builds products on top of foundation models via APIs; between software and ML engineering.
Enabled by foundation-model API detachment of application from research layer · current fact
Familiar title, new shape
Agent-Directing Research Scientist
Directs fleets of ML-engineering agents, setting hypotheses and interpreting results while agents run experiments.
AutoResearch-style demonstrations; agentic experimentation systems · projection
New role titles form fast in AIM because there is no credential infrastructure to slow them and regulation is actively creating role categories. LLMOps, safety, and governance are already deployed at scale; evals and agent-directing configurations are emerging.
Bars above the line are the parts of this work that still need a person. Bars below it are what AI can already do. Tap any column to see the actual work behind it.
high ground · holds stronglydeep water · reaches furthest
yours, by strengthAI reach, by depth
The honest read. Three strong dimensions (accountability, creative synthesis, navigating ambiguity) plus moderate relational in bridge roles. Accountability is stronger than in most digital fields because the field's products are dangerous enough that society demands human sign-off. Protection concentrated in research/safety/governance layers; thinner in routine applied-engineering, which AutoML and agentic tools target most.
Reflexive field: the work product is AI, and AI is increasingly built by AI. Three core domains (language, predictive ML, agentic) reflect that the field's own tools are being pointed at its own work. Scored under the meta-field rule — practitioner's work of building AI, not the product domains served. Agentic AI carries dual-use dynamics unique in the corpus: the field's most powerful tool is also its central safety concern.
How AI is changing the way in
4 ways into this field, and AI is not doing the same thing to each of them. 2 are opening up rather than closing.
ML Research Scientist entryHarder to enter
PhD-gated and competitive; compute inequality limits entrant scope; strong demand but high bar (inference)
Forward-looking reflexive risk (all applied)Harder to enter
AutoResearch/AIDE ML/MLE-STAR target junior applied tasks; latent risk if shortage eases and tools mature (inference/projection)
Applied AI / ML Engineer entryOpening up
~143% YoY posting growth; 3.2:1 demand-supply gap; ~70% require a degree, only ~1% a PhD, 30% no formal requirement (survey_self_report)
Safety / Governance entryOpening up
New field; ~55% reported alignment job growth; ~1.5% of orgs have adequate governance headcount; regulation-driven (survey_self_report)
That is everything we currently know about AI in AI & Machine Learning Engineering. It shows where things are moving so you can choose which way in suits you.
People drawn to AI & Machine Learning Engineering are often drawn to these. Most sit in a different part of the terrain.