LumiCV
AI & ML resume guide

Resume for AI Jobs - Examples and Templates for Every AI Role

Real, ATS-tested resume examples for ML, AI, LLM, MLOps, and research roles - written by people who hire for them. Free to copy and customise.

Why an AI resume is not a software engineering resume with PyTorch added

AI hiring managers are reading for a specific signal, and it is not the one most candidates put on the page. They have read a thousand resumes that say "built ML pipelines using TensorFlow and AWS." They are not looking for that. They are looking for evidence that you can take a model from a notebook to something that earns its keep against a real eval set, on a real budget, in a real product.

That changes what gets weight on your resume. A bullet about a fine-tuning run matters because of the eval delta and the cost - not because you used LoRA. A retrieval pipeline matters because of recall@k on a golden set and p95 latency under load - not because you wired up a vector DB. A research project matters because of the result it landed and where it landed - not because you ran a transformer.

"Hiring managers don't read your skills section. They read your bullets and decide if your skills section is bullshit."

The framework names matter, but only the right ones, and only in context. Listing PyTorch, JAX, vLLM, Triton, Ray, or a specific quantisation library is useful when the bullet around it shows you used it under pressure - shaved 40% off inference cost, kept p95 under 800ms during a launch, replaced a brittle prompt with a fine-tune that improved factuality 18 points on a held-out set. Names without numbers read as a buzzword pile.

Senior roles add one more bar: external signal. A first-author paper at a top venue, a maintained open-source repo with real users, a talk at a serious conference, or a clearly written technical blog. For research roles this is table stakes. For senior engineering roles it is increasingly the tiebreaker between two strong on-paper candidates. If you have it, it goes on page one.

"The candidates who get AI offers are comfortable being a researcher on Tuesday and an engineer on Wednesday. Your resume needs to show both."

The other thing AI hiring managers screen for is range. Pure researchers who cannot deploy get filtered out of product teams. Pure engineers who cannot read a paper get filtered out of model teams. The candidates who get offers are comfortable being a researcher on Tuesday and an engineer on Wednesday - and their resumes show both. One bullet about an eval methodology you designed. One bullet about a production rollout you owned. One about cost or latency you fixed. That is the shape that converts.

Role-by-role examples

Pick the role you're applying for

Each example shows the bullet structure, ATS keywords, and metrics hiring managers look for in that specific AI/ML role.

What recruiters scan for

The five signals AI recruiters look for in 30 seconds

First-pass screens are fast. These are the things that get a "yes, schedule them" before anyone reads paragraph two.

Quantified production metrics

Latency (p50/p95/p99), throughput (req/s, tokens/s), $/inference, accuracy lifts on a named eval. "Reduced p95 latency 38% on the recommendations endpoint, saving $14k/month in GPU spend" beats "optimised model performance" every time.

Eval rigor

Golden sets you built or curated. A/B tests you ran. Regression tests that caught a real prompt drift. Naming the eval methodology - LLM-as-judge with calibration, human-rated rubric, MMLU/HELM-style harness - signals you take quality seriously, not just vibes.

Frameworks fluency that matches the stack

Read the JD's stack and mirror it. Hiring at a vLLM shop? "Migrated inference from HF Transformers to vLLM, 3.4x throughput at same latency" lands. PyTorch, JAX, Ray, Triton, Modal, Anyscale, LangGraph, DSPy - name the ones the company actually runs.

Domain-specific signals

Research roles: papers (with venues) and a clean repo. Engineering roles: a deployed model behind a real product surface. AI engineer roles: prompt + eval discipline (versioning, regression suites, structured outputs). Match the proof to the job.

A coherent career arc

Recruiters look for a story: SWE -> ML engineer pivot, PhD -> applied scientist, researcher -> AI engineer at a startup. Make the arc obvious in your summary line and your most recent role. A one-line "previously: backend at Stripe" or "PhD in computational neuroscience, now shipping LLM products" reframes the rest of your resume in one breath.

AI resume FAQ

How is an AI engineer resume different from a software engineer resume?
A software engineer resume is judged on systems you built, code quality, and shipping pace. An AI engineer resume is judged on whether your models actually earn their keep in production - which means quantified eval results, latency and cost numbers, and proof you handled the messy parts (data drift, eval sets, prompt regressions, GPU spend). Hiring managers will skim your bullets for "deployed", "p95 latency", "cost per inference", "eval", and "% improvement over baseline". A bullet that says "built ML pipeline" is treated the same as "did stuff" - it tells them nothing.
Should I list papers on my ML engineer resume?
For research scientist and applied scientist roles, yes - papers are the primary signal of research depth, and a publications section on page 2 is expected. For ML engineer and AI engineer roles, list a paper only if it directly proves the engineering claim you are making. One first-author paper at a top venue is worth more than ten "et al." entries on a one-page engineering resume. If you have ten papers and you are applying for an engineering role, link a Google Scholar profile in the header instead of dumping them inline.
What's the best resume format for AI/ML jobs?
For engineering roles (AI engineer, ML engineer, MLOps, LLM engineer), use a one-page reverse-chronological format - same as a senior software engineer resume. Skills in a tight block at the top, experience bullets that lead with verbs and end with metrics, education last. For research roles (research scientist, applied scientist, PhD-track applied scientist), two pages is standard: page 1 for experience and selected publications, page 2 for full publication list, talks, and grants. Avoid creative templates - AI hiring is keyword-driven and recruiter screens are still a thing.
Do I need a portfolio or GitHub for AI roles?
For mid-level and below: yes, and it matters more than your resume bullets. A working repo with a clean README, reproducible eval, and one or two strong projects (an LLM eval harness, a fine-tuning run with results, a deployed demo) gives hiring managers evidence your resume alone cannot. For senior and staff: production credentials replace open-source, and a GitHub link without recent commits is worse than no link at all. If your last commit was 2022, omit the link.
How do I write a resume for an AI role I haven't done yet (e.g., SWE -> LLM engineer pivot)?
Re-frame the work you have already done in the language of the role you want. A backend engineer who built a RAG prototype, ran prompt evals, and shipped a chatbot to internal users has 80% of an LLM engineer resume - they just need to lead with that work, not their REST API throughput. Add a short "Projects" or "AI Work" section at the top with two or three concrete LLM/ML projects, even if they were side projects or 20% time. Drop unrelated bullets ruthlessly. The goal is to make the hiring manager think "they have already been doing this job, just with a different title".

Build your AI resume in 10 minutes

28 ATS-friendly templates, 14 of them free. AI tailoring on every job. Free to start, cancel anytime.