AI Engineer Foundations (Maven cohort)
For: Working engineers committing to a career pivot into AI
"AI Engineer" replaced "ML Engineer" as the dominant 2026 job title. Here's the curriculum that actually gets you hired.
The "AI Engineer" job title — coined by Swyx in 2023 — has by 2026 displaced "ML Engineer" as the dominant role for engineers building LLM-powered products. The market shift is structural: the work has moved from training models (ML Engineer territory) to applying them (AI Engineer territory). Different curriculum, different skill stack, different hiring pipeline.
The honest version of the roadmap: you don't need to know how to train transformers from scratch. You need to be excellent at applying them. That means: prompt engineering as a daily craft, agent loops, RAG and retrieval engineering, evaluation infrastructure, MCP and tool integration, observability, and the production concerns (latency, cost, failure modes) that demo code ignores. The Phase 1 developer learning path on this site covers most of it; this page assembles the rest with an explicit focus on the "I want to get hired as an AI Engineer" goal.
The shortest path from working software engineer to hired AI engineer in 2026: 30-50 hours of foundational courses (the ones below), plus 100-200 hours of project work that ships in public — a deployed agent, an open-source MCP server, a public blog with 5+ posts on production AI lessons. The portfolio matters more than the courses; the courses build the vocabulary the portfolio needs.
For: Working engineers committing to a career pivot into AI
For: Engineers who have used the OpenAI API but never built an agent loop
For: Developers building production AI agents in 2026
For: Engineers whose basic RAG works in dev but fails in prod
For: Engineers who plan to train, fine-tune, or research LLMs at depth
AI Engineers apply pre-trained LLMs to ship products (prompting, agents, RAG, evaluation, integration). ML Engineers train models (gradient descent, model architectures, data pipelines, hyperparameter tuning). In 2026, AI Engineer roles outnumber ML Engineer roles roughly 5-to-1 by job postings; the work has moved from training to application. Different curriculum entirely.
No. AI Engineering is overwhelmingly an applied software-engineering role in 2026; PhDs are nice-to-have, not required. The 2026 AI Engineer hiring pipeline values shipped projects (a deployed agent, an open-source MCP server, a published blog with production lessons) over credentials. The honest exception: AI safety research roles and frontier-lab research engineer roles still favor PhDs.
For a working software engineer transitioning in: 3-6 months of focused work — 50-80 hours of courses plus 150-250 hours of portfolio projects. For someone starting from a non-engineering background: 12-18 months including underlying CS fundamentals. The portfolio matters more than the timeline; ship 3-5 shippable AI projects in public and the timeline takes care of itself.
Python + the OpenAI/Anthropic SDK + LangChain/LangGraph + a vector database (Chroma or Pinecone for learning) + an evaluation tool (LangSmith, free tier) + MCP for tool integration. Add Hugging Face if you'll fine-tune; skip otherwise. This stack covers ~80% of AI Engineer job descriptions in 2026.
Worth $1,495 if you (a) need a commitment device to actually finish, (b) value the peer network and live instruction, (c) will ship the capstone project. Skip if you reliably complete self-paced courses on your own — the same content (DeepLearning.AI shorts + the listed reading) is free if you can self-direct.
Once you've learned the concepts, these are the agents and tools where the skills pay back.
Anthropic's terminal agent — composable, scriptable, and built around Claude's tool-use loop.
Background agent that drives the Cursor editor across multi-file changes.
Autonomous AI software engineer that ships PRs end-to-end.
Open-source autonomous coding agent that lives in your IDE.
Want a sequenced curriculum instead of one-off courses?
Browse learning paths →