Role hub · live · updated 20 Nov 2026

Applied AI engineer: the role, pay and who is hiring

An applied AI engineer takes frontier models into real products and customer deployments: building and tuning systems around the model for one use case, then making them reliable in production. OpenAI and Anthropic have whole applied AI teams; so do Mercor, Klaviyo and a fast-growing list of AI startups.

Open roles
756
Companies hiring
360
Median posted pay
$180k to $263k
Remote
22%
Demand
5x searches in a year

This week · 20 Nov 202642 new Applied AI roles, most from Anthropic, SignalFire and Clera.

01 · The role

What does an applied AI engineer do

The title sits between research and product. At the labs it is often customer-facing; at product companies it is the team that makes AI features work.

  1. SCOPE

    Pick the problem

    Find the use case where a model can actually do the work, and define what good looks like before building.

  2. BUILD

    Engineer around the model

    Prompts, retrieval, tools, fine-tuning or distillation when it pays off, and the data pipeline behind it.

  3. EVALUATE

    Prove it works

    Evals on real cases, error analysis, comparisons between models and approaches.

  4. DEPLOY

    Make it hold up

    Production reliability, monitoring, cost and latency, and feeding what breaks back to the model or research team.

Applied AI is closer to research than AI engineering, and closer to customers than research.

02 · Pay

Applied AI engineer salary

Median posted pay on landed, next to the bands the biggest employers publish.

Median posted range, USD base

$180k to $263k

From 341 live postings that publish a range, before equity and bonus.

Applied AI salary by city and company →

03 · The way in

How to become an applied AI engineer

Most come from ML engineering or strong software engineering with real model work.

  1. [x]
    Get strong at Python and dataPipelines, notebooks to production, clean experiments.
  2. [x]
    Fine-tune and evaluate a modelPick an open model, tune it for one task, and show the eval numbers before and after.
  3. [ ]
    Deploy something realA system with users, monitoring and a cost budget.
  4. [ ]
    Write up the trade-offsA short public write-up of what you tried and why is strong proof for this role.
  5. [ ]
    Apply the day roles openEarly applicants get read first. Full Applied AI roadmap →

04 · The roadmap

How to become an Applied AI Engineer: the roadmap

About 3–6 months, 6 stages, 8 core skills, aiming at $200k. This is explicitly a senior IC track, not an entry role. Realistic prep is three to five years as a backend, full-stack, or ML engineer, then a six-to-twelve-month Applied AI specialization push. GoGloby calls it "a senior engineer who integrates AI systems into production software at the level where things get difficult." The job is production reliability — data access, inference reliability, governance, evaluation, observability, and failure containment — not model training. Comp skews senior: $200K-$280K total mid-level, $320K-$550K+ at staff/principal.

  1. Stage 0 · prerequisite

    Foundation (from prior experience)

    Years of production SWE: Python/TS, REST/gRPC, Docker, K8s, a cloud

  2. Stage 1 · ~6-8 weeks

    AI tooling fluency

    The 5-layer stack plus daily Cursor, Claude Code, Copilot

  3. Stage 2 · ~2-3 months

    Production integration

    End-to-end runtimes: data access, inference reliability, CRM/ERP wiring

  4. Stage 3 · ~2 months

    Evaluation and observability

    Scenario evals, drift detection, Langfuse/LangSmith, eval-driven CI/CD

  5. Stage 4 · ~2 months

    Failure containment and SLOs

    Rollback paths, fallback behavior, circuit breakers, blue-green

  6. Stage 5 · ongoing

    Specialized applied roles

    Forward Deployed, AI Native, Founding AI Infrastructure Engineer

The full roadmap: projects, skills and what to learn at each stage

The roadmap, stage by stage

This roadmap differs in shape because it is explicitly a senior IC track. GoGloby frames it as "a senior engineer who integrates AI systems into production software at the level where things get difficult"; the D.E. Shaw JD asks candidates to "design, develop, and maintain shared AI infrastructure and agentic applications, ensuring firmwide data integration"; and 2501.ai's Applied AI Engineer "builds autonomous AI agents that operate directly in the shell to complete real production tasks." Stage 0 is satisfied by prior experience: several years of production SWE, comfort with Python or TypeScript, REST/gRPC, Docker, Kubernetes, observability tooling (Datadog, Prometheus), a cloud platform, and relational databases. Stage 1 (~6-8 weeks) is AI tooling fluency — the same five-layer stack as AI Engineer plus daily use of Cursor, Claude Code, and GitHub Copilot as agentic IDEs; the capstone ships a small internal app using two of these together for a real team. Stage 2 (~2-3 months) is production integration: engineering an end-to-end runtime that manages data access, inference reliability, and governance, wiring into CRM, ERP, and internal APIs; the capstone is an LLM-powered workflow that genuinely automates a team process. Stage 3 (~2 months) is evaluation and observability: scenario-based test cases, drift detection to surface latency and cost anomalies, Langfuse or LangSmith; the capstone ships an LLM-backed feature with eval-driven CI/CD and live observability. Stage 4 (~2 months) is failure containment and SLOs: rollback paths, fallback behavior, and patterns from "Designing Data-Intensive Applications" — circuit breakers, exponential backoff, blue-green deployments. Stage 5 branches into specialized applied roles: Forward Deployed, AI Native, and Founding AI Infrastructure Engineer. For career-switchers without SWE, CodePath is the structured pipeline in.

The 2026 stack to learn deeply

The Applied AI Engineer's stack is the AI Engineer stack plus the SRE/platform-engineering stack. Tier 1, daily: Cursor and Claude Code specifically (GoGloby lists them by name as the dominant coding workflow), GitHub Copilot as a Microsoft-shop baseline, the OpenAI and Anthropic SDKs (direct API calls beat frameworks in many production paths), Pydantic v2 for every response validation, Python or TypeScript as the primary language (2501.ai is a TypeScript-first shop: Node.js, Supabase Postgres, Vercel, Vue + Nuxt, Python for evals), plus FastAPI, Next.js, and Vercel. Tier 2, production stack: Postgres is universal, scaling to Supabase, Databricks, Snowflake, or BigQuery; vector DB is pgvector by default, or Pinecone/Qdrant; MCP servers connect upstream systems — GitHub, Context7, Cursor, Supabase, Notion, Zapier, Jira, AWS, Linear, GitLab, Stripe, Shopify, Snowflake are named remote offerings — so knowing the PulseMCP registry is knowing your toolbox; Langfuse (open-source, self-hostable, free to 50k units/mo) or LangSmith (tighter with LangChain, pay-per-trace above 5k) for observability, with Phoenix, Helicone, and AgentOps as alternatives. Tier 3, frameworks: LangGraph for production stateful agents, OpenAI Agents SDK as a common default, PydanticAI for type-safe Python agents. Tier 4, eval and shipping: Ragas, DeepEval, Braintrust; Promptfoo for security and red-teaming; GitHub Actions, CircleCI, or Buildkite for eval-driven CI. Tier 5, production reliability: Docker and Kubernetes as the non-negotiable SRE baseline; Datadog, Grafana, and Prometheus for APM and metrics; PagerDuty and Incident.io for on-call. A telling build: wire an agent into the company's Jira/Slack/Notion via MCP and ship it as a usable Slack bot with LangGraph plus Langfuse retries and budget caps.

Portfolio projects that get you hired

The Applied AI portfolio is about production reliability, not model novelty — show incident experience, SLOs, and eval gates. Beginner (after SWE experience):

  • An internal Slack or Discord bot powered by Claude or GPT using webhooks, an LLM, and Langfuse tracing.
  • An LLM-driven CI/CD check: a GitHub Action that runs Ragas eval on every PR — eval-driven development in one repo. Intermediate:
  • Production RAG with leaky/edge-case stress-testing and graceful fallback (LangChain, Qdrant, OpenAI) including explicit rollback behavior, redaction, and cost alarms.
  • A custom MCP server exposing one internal database or API to Claude Desktop via FastMCP. Advanced:
  • An autonomous agent operating in a production shell with full observability — the 2501.ai model, powerful but requiring careful safety design.
  • A multi-tenant RAG system where competitors cannot see each other's data, demonstrating senior isolation design.
  • An eval-driven release pipeline that gates deploys on Ragas/DeepEval scores with rollback-on-regression — the most in-demand 2026 reliability pattern. Standout: a real production system used by a real team with measurable outcomes, wrapped in a portfolio site that explains the SLOs, the eval strategy, the rollout plan, and the incident postmortems. The through-line the report stresses: "system reliability over model quality" and "failure containment" are the central mental models, so every project should demonstrate what happens after the model is embedded in a live system.

How the role is evolving

Agentic SDLC tools — Cursor, Claude Code, GitHub Copilot — are listed by GoGloby as the primary tools for Applied AI Engineers in 2026; their purchase is no longer developer-tools budget but core AI infrastructure budget. MCP matters here operationally: remote servers grew nearly 4x since May 2025, and Applied AI Engineers operate them rather than build from-scratch connectors, so anyone building an MCP integration around the 2026-07-28 spec Release Candidate is on the bleeding edge and part of a tiny, sought-after cohort. Production observability and eval are becoming a first-class discipline, with Langfuse's open-source self-host path winning because the core repo is MIT and self-hosting is free. Two adjacent titles are rising: the Forward Deployed AI Engineer (Applied AI paired with sales engineering and customer-facing deployments) and the Founding AI Infrastructure Engineer (the employee #1-3 cousin). What is fading: pure backend engineers without an AI component, AI Engineers without SRE habits (the "only writes prompts, never on-call" pattern is closing), hand-rolled model-serving platforms (the stack has consolidated around vLLM plus Langfuse/LangSmith), and any tool lacking a working reliability story of CI/CD eval gates, SLO dashboards, and rollback playbooks. Where it heads: Applied AI Engineer is the senior seat of the AI Engineer career ladder — an SRE-with-LLM-fluency who owns the entire model-to-runtime contract. Because interview requirements across all three titles are converging on RAG, agents, cost, and multi-tenancy, differentiation is increasingly by compensation band rather than day-to-day.

How to actually get hired

From the Wellfound NY listings and the UPenn guide, 2026 Applied AI JDs ask for 2-10 years of SWE experience (the "Applied" suffix signals seniority), the ability to "design, develop, and maintain shared AI infrastructure and agentic applications," ownership "across TypeScript CLI, Postgres migrations, automated evals, and Vercel deployments," and experience implementing AI solutions rather than training models from scratch. A typical loop: a resume screen emphasizing production-reliability stories; a hiring-manager round ("Tell me about a system you shipped to production that depended on an LLM — what failed, and how did you catch it?"); a coding round that is usually a build-something-real pair-program, leaning into systems questions like the multi-tenant RAG isolation prompt; a production-design round on rollback strategies, observability, drift detection, and SLO design; and a behavioral round ("How do you approach GenAI safety in consumer products?"). To stand out, show real incident experience, cite specific SLOs you maintained, explain a chosen framework's failure modes, and bring numbers — latency p95, % drift, error-budget burn; senior 80th-percentile signals can hit $300K+ base salaries. Entry paths: SWE to Applied AI is canonical; also ML Engineer to Applied AI (model side growing into production), Data Platform Engineer to Applied AI (pipeline fluency applied to AI), and Solutions Architect to Forward Deployed AI Engineer. For early-career without SWE, CodePath is the only structured path and is aimed at community-college access.

Resources to learn from

Books

Courses

YouTube channels

  • Cole Medin — production-agent builds closest to Applied AI work patterns
  • LangChain — LangGraph production case studies map directly to the role
  • AI Jason — LLM eval content
  • David Ondrej — low-code agents for shipping quick internal tools
  • IBM Technology — explainers that map well to stakeholder communication

Blogs & newsletters

Papers & docs

Communities worth joining

Sources

05 · The difference

Applied AI engineer vs AI engineer vs research engineer

Three titles that companies use loosely. The difference is how close the role sits to the model.

AI engineerResearch engineerApplied AI engineer
Starts fromA product featureA research questionA real use case or customer
Touches the modelThrough the APITraining and experimentsFine-tuning, evals, sometimes training
OutputA shipped featureExperiments, papers, infraA deployed system that meets a bar
Common atProduct companies, startupsAI labsAI labs and AI-native startups

06 · The interview

The applied AI engineer interview

Expect coding, ML depth and a round about turning a messy problem into a working system.

  1. Coding

    Production-quality Python, often data-heavy.

    Every loop
  2. ML fundamentals

    Fine-tuning, evaluation, retrieval, failure modes of large models.

    Deeper than AI engineer
  3. Applied design

    Scope and design a system for a real use case, with how you would measure it.

    The core round
  4. Customer or stakeholder case

    At the labs: explain trade-offs to a customer-like audience.

    Labs often

07 · Hiring

Who is hiring applied AI engineers

756 open roles at 360 companies, refreshed daily. Each links to the company's own page.

08 · Where

Applied AI jobs by country

56% of Applied AI roles are in the US, led by San Francisco and New York. 22% are remote.

09 · Hiring now

Applied AI engineer jobs

756 open today. The newest openings first, from the companies' own career pages.

  • Applied AI Engineer116
  • Senior Applied AI Engineer31
  • Applied AI Engineer - AI Finance Agent23
  • Applied AI Architect15
  • Staff Applied AI Engineer12
  • Software Engineer, Applied AI11
  • Staff Software Engineer, Applied AI10
  • Applied AI Engineer, Codex8
  • Software Engineer - Applied AI8
  • Application Software Engineer, Applied AI7

Be early on every applied AI opening.

landed watches applied AI roles at the labs and AI startups and applies within the hour. 10 free applications, no card.

Start applying free →

FAQ

Applied AI engineer, answered

What is a applied ai engineer?

An applied AI engineer takes frontier models into real products and customer deployments: building and tuning systems around the model for one use case, then making them reliable in production.

How much does a applied ai engineer earn?

Across 341 live Applied AI postings on landed that publish pay, the median range is $180k to $263k in USD base, before equity and bonus. Senior roles at AI labs post well above that.

Who is hiring applied AI engineers?

landed tracks 756 live Applied AI roles at 360 companies. OpenAI, Bjak, Anthropic, Mistral AI, SpaceX, Articul8, Klaviyo and Faire Wholesale, Inc. have the most open right now.

Are Applied AI jobs remote?

22% of live Applied AI postings on landed are fully remote. Most of the rest are hybrid in the biggest tech cities.

Is an applied AI engineer the same as an AI engineer?

Often close, but applied AI roles usually go deeper on the model: fine-tuning, evaluation and research-informed choices, and at AI labs they often work with customers. AI engineer roles more often build product features through model APIs.