Back

Landscape

AI Careers

The AI job market is bifurcating into "big AI" (frontier model companies pushing toward AGI) and "small AI" (fine-tuned, self-hosted models for privacy-sensitive domains) — surviving either path requires deep fundamentals, business focus, and delivery skills over hype.

Created Apr 5, 2026·Updated Apr 27, 2026

Overview

Stanford CS230 Lecture 9 (Autumn 2025), featuring Andrew Ng and Laurence Moroney, covers the current AI career landscape. The core message: it's the best time ever to build with AI, but the market is noisy with hype, and many AI projects fail because teams lack fundamentals or business understanding.

The Golden Age Argument

Andrew Ng's framing: AI task complexity (measured by how long it takes a human to do the equivalent) is doubling every 7 months (per METR research). For coding specifically, the doubling time is ~70 days. This means anyone can now build software more powerful than what was possible a year ago, using AI building blocks (LLMs, agentic workflows, voice AI, deep learning).

The flip side: finding jobs has gotten tougher for fresh grads, but teams can't find enough skilled builders. The number of ideas exceeds the number of people who can execute.

The Big/Small Bifurcation

Laurence Moroney's 5-year outlook:

Big AI — Frontier model companies (OpenAI, Anthropic, Google) pushing larger models toward AGI. This is where the current hype and bubble risk concentrates.

Small AI — Open-weight models getting smaller and more capable. The 7B model of next year will match the 300B model of today. Organizations in privacy-sensitive fields (law, medicine) will fine-tune small self-hosted models on downstream tasks. Skills for this side: fine-tuning, deployment, domain adaptation.

The bubble, if it bursts, will likely hit big AI first. Small AI has longer runway because it solves concrete privacy and cost problems.

What Gets You Hired

Three things that matter more than technical depth alone:

  1. Fundamentals — Deep understanding of AI academics and practicalities, not just surface-level tool usage
  2. Business focus — Understanding what the business needs and being able to deliver for it. Bias toward delivery.
  3. Delivery skills — The people who got jobs in Moroney's examples were the ones with half-baked ideas that were well-grounded, not the ones with impressive but unshippable demos

Anti-pattern: technically brilliant candidates who fail interviews because they can't collaborate or communicate. Teamwork is non-negotiable.

The hype cycle in AI is extreme. Social media engagement farming makes signal-to-noise terrible. Advice:

  • Filter actively — most AI content is noise
  • Go deep on fundamentals rather than chasing every new release
  • Read papers (better signal-to-noise than social media)
  • Keep your finger on the pulse without drowning in it

The dotcom bubble analogy: it burst, but Amazon and Google survived because they understood fundamentals. Same principle applies.

Relationship to Agent Proficiency

Ng's personal advice aligns with the agent proficiency thesis: spend time building with agentic tools rather than consuming content passively. The practical skill of directing AI agents toward real problems is what separates hype participants from builders.

Generalists vs. Specialists

A related debate: Grok-summarized X discussion found that broad thinkers who link ideas across fields hold power amid AI's rise. Supporters cite examples like Matthew Gallagher building a $401M telehealth business with broad skills and two employees. The emerging consensus favors hybrids who go wide then deepen strategically as AI handles routine tasks. See also Agent Proficiency — agent management may be the ultimate generalist skill.

The AI Engineer Learning Path

An analysis of ~2,000 job descriptions (Luffytaro, Apr 2026, based on Alexey Grigorev's field guide) maps the skills that actually get hired in AI engineering roles. The core insight: AI engineering is about building systems around LLMs, not training models from scratch.

The 20% that drives 80% of the work:

  1. LLM fundamentals — controlling models predictably, structured outputs, prompt engineering
  2. RAG — the backbone of most real-world AI systems; chunking strategies matter more than people think
  3. AI agents — tool calling, agent loops (think → act → observe → repeat), MCP, multi-agent systems
  4. Testing and evaluation — LLM-as-judge, offline eval datasets, measuring retrieval quality
  5. Monitoring and observability — tracing, logging, cost tracking, feedback loops
  6. Production systems — turning notebooks into services, guardrails, cloud deployment

The converging stack: React/Next.js + FastAPI + LangChain/PydanticAI + OpenAI/Anthropic + Pinecone/Weaviate/Qdrant + Docker/K8s + OpenTelemetry. This mirrors Ann Miura-Ko's observation in AI-Native Product Development that the tool stack is converging across companies.

Differentiators that get hired faster: agent frameworks (LangGraph, CrewAI), fine-tuning, evaluation systems, vector databases, multi-agent architectures. See also Agentic Engineering for the harness design patterns these roles increasingly require.

Sources

  • "Stanford CS230 | Autumn 2025 | Lecture 9: Career Advice in AI" — Stanford Online (Andrew Ng, Laurence Moroney) (link)
  • "Generalists Poised to Thrive in AI Era" — X discussion summary (link)
  • "The AI Engineer Learning Path" — Luffytaro (tweet, Apr 2026) (link) — skills roadmap from ~2,000 job descriptions; based on Alexey Grigorev's AI Engineering Field Guide