CertivaPreparing for a certification? Practice tests for AWS, Azure, Google Cloud, Snowflake, Databricks and more. 20 free questions on every exam.Start practising →

#90DayAIEngineer · your own 92-day calendar

90 days to become an AI engineer.

Pick your start day, ship something every week, and finish 92 days later with a portfolio instead of a resolution. Twelve projects, about two hours a day, every video and resource in one place. Your calendar, ship dates and tracker all count from the day you choose.

92days
12projects
24videos
200+hours

Before you start

Can this really be done in 90 days?

Yes, if you already write basic code in any language: loops, functions, a little Git. New to coding? Keep the plan but slow it down: take Week 0 seriously, add a month of Python, then follow the same order.

"AI engineer" here means someone who builds dependable products on top of existing models: chatbots that stay grounded, agents that finish the job, search that understands meaning. It is not ML research, and you won't be designing new architectures.

The structure

Three months, three acts

Each month of your plan ends with a checkpoint and each week ends with a project. Twelve weeks, twelve ships.

ACT I · MONTH 1

Speak the language

How LLMs behave and how to talk to them from code.

  • LLM APIs in Python
  • How models really work
  • Prompts & JSON output
  • Embeddings & search
Ships 4 projects
ACT II · MONTH 2

Build things that think

Retrieval, tools, agents and, above all, evals.

  • RAG from scratch
  • Tool use & agents
  • Evals (the pro skill)
  • Open models & LoRA
Ships 4 projects
ACT III · MONTH 3

Ship like a pro

Deploy, monitor, build a capstone and launch it in public.

  • Deploy, stream, cache
  • Tracing & guardrails
  • Capstone product
  • Launch & get seen
Ships 4 projects

The only daily rule

The 1 · 1 · 1 method

1 hr

Learn

One video, one doc page or one chapter. Not five tabs. Take notes by hand.

1 hr

Build

A tutorial only counts once you've committed code after it.

1 post

Share

Every Friday, post what you shipped: a screenshot, a lesson, a failure. Recruiters look for builders, not certificates.

Roughly 2 hours on weekdays and 4 on weekends. Consistency beats intensity.

Week 0 · the 7 days before Day 1 · Setup

It starts before Day 1

Setup checklist

Stay accountable

  • Post every Friday with #90DayAIEngineer: what you shipped, what broke, what you learned.
  • Tag one friend to do it with you. A partner makes it far more likely you finish.
  • Missed a day? Fine. Don't miss two.

The full roadmap

12 weeks. 12 ships.

Pick a week to see what to learn, what to ship and the videos to watch. Ticks save in this browser. Rule: no week ends without a public GitHub repo.

Video library

All 24 videos from the roadmap

Every YouTube link from the article in one table. Filter by month of your plan or copy a link to share with your batch.

WeekVideoWhy watch

More playlists

CampusX playlists for this roadmap

These free CampusX playlists by Nitish Singh cover the same topics in more depth. Each week's panel above also lists the matching CampusX videos.

Don't break the chain

The 92-day tracker

Each day you finish your hour of learning and your hour of building, tap the box. One row per week of your plan; days after today stay locked until they arrive.

0days crossed off
0current streak
0best streak

Go deeper

Two roadmaps to keep open

The 12-week plan tells you what to ship each week. These two show the bigger map: one for what the job covers, one for how things work underneath.

roadmap.sh · interactive skill map

AI Engineer Roadmap

A clickable visual map of everything an AI engineer is expected to know, from using pre-trained models and prompting to RAG, agents, embeddings and safety. Each node links to free reading. Use it to check you haven't skipped a topic and to see what comes after these 92 days.

Open roadmap.sh/ai-engineer ↗

aiengineeringfromscratch.com · free, open source

AI Engineering from Scratch

A long-form curriculum maintained by Rohit Ghumare and contributors. You hand-write the tokenizer, attention, backprop and the agent loop before using any framework, then move on to LLM engineering, evals, serving, observability and agents. Runnable code in Python, TypeScript, Rust and Julia.

Open AI Engineering from Scratch ↗

Your weeksWhat you shipOn roadmap.sh, look atIn From Scratch, go to
W1–W2Chatbot, token visualizerPre-trained models, how LLMs work, OpenAI/Claude APIsSetup & tooling, software fundamentals, model architecture (optional depth)
W3–W4Resume extractor, notes searchPrompt engineering, embeddings, vector databasesLLM engineering: prompts, structured output, embeddings
W5–W6Chat-with-PDF, research agentRAG, AI agents, tool use / function callingRetrieval, agent engineering, tools & protocols (MCP)
W7–W8Eval harness, LoRA tuneOpen-source models, fine-tuning, evaluationEvaluation & testing, training basics
W9–W10Deployed app, guardrails postAI safety & ethics, prompt injection, deploymentServing & deployment, observability & monitoring
W11–W12Capstone, launchProjects section for more build ideasPick one deep-dive phase for January

Build from the bottom up

The AI engineer stack

07
Production & observabilitydeploy · trace · guard
06
Evalsgolden sets · LLM-as-judge · regressions
05
Agents & tool usefunction calling · loops · MCP
04
Retrieval (RAG)chunk · embed · retrieve · rerank
03
Prompting & structured outputsystem prompts · few-shot · JSON schema
02
LLM fundamentalstokens · context · sampling · embeddings
01
Python + APIsasync · pydantic · http · git

Most self-taught builders skip layer 06. Demos that work on three examples break on the fourth. A test set, a score and a chart of improvements make you look senior.

Stay on the road

What to learn, what to skip

Learn now

  • Calling LLM APIs well
  • Embeddings & retrieval
  • Tool use & agent loops
  • Writing evals
  • Deploying & monitoring
  • Reading model docs fast

Skip for now

  • Deep backprop math: useful later, not needed to ship products now.
  • Training models from scratch: that's research; you're doing engineering.
  • Every new framework: learn the concepts, frameworks are syntax.
  • Comparing 10 vector DBs: pick one and move on.
  • Collecting certificates: one deployed app beats ten badges.
  • Waiting to feel "ready": you won't. Start anyway.

Free resource stack

Everything else you need

All free except one book.

January 1, 2027

What you'll have to show

12public repos
1deployed product
12build-in-public posts
1eval report with real numbers
1demo video
1case study a recruiter reads in 3 minutes

Your progress lives in this browser

Move to another phone or laptop

Your batch, ticks and tracker are saved on this device only. Copy your progress code here and paste it on the other device to continue there.