Career path

AI / ML Engineer

You become the person who makes machines learn, and proves they learned the right thing.

Behind every 'AI feature' is someone who chose the model, trained or fine-tuned it, measured it honestly and kept it fast in production. That person understands what's inside the black box. Your maths degree is the unfair advantage here: gradients, probability and linear algebra are the actual working tools.

PythonNumPypandasscikit-learnPyTorchHugging FaceFastAPIDockerMLflow / W&B
A day in your future life
09:30

Overnight training finished. Validation loss looks great, which is suspicious. You find data leakage: duplicates across train and test.

11:00

Fixed the split, retrained. Accuracy is lower but honest, and it now matches what happens in production.

14:00

Product asks: 'Fine-tune or just prompt GPT?' You run both on 200 examples. The fine-tuned 1B model matches it at 1/30th the cost.

16:30

You quantise the model, cut latency from 400 ms to 90 ms, and ship it behind an API.

18:00

The drift dashboard is green. You queue tomorrow's experiment and go home.

What you'll build

  • Models that classify, rank, predict and generate
  • Fine-tuned LLMs for specific tasks
  • Search and recommendation systems
  • Evaluation suites and ML pipelines in production

Your maths edge

This is the most maths-heavy role on the list. Backprop is the chain rule, embeddings are linear algebra, loss functions come from probability, and evaluation is statistics. Most people learn these as black boxes. You'll know what they're doing.

Demand

AI/ML specialists are among the WEF's fastest-growing jobs to 2030. 64% of new GCC roles in India in 2026 needed AI or data skills.

Entry pay (India, rough)

Roughly โ‚น6โ€“18 LPA in India, with a long tail far above that at top product companies and AI labs.

The honest truth

Pure 'research' roles need an MS or PhD. Applied ML engineering, which is building and shipping models, is open to strong BTech graduates with real projects. Kaggle-only portfolios aren't enough. Show deployed, measured systems.

2-minute taste test

Try a few minutes of the job

Three real moments from an ML engineer's week. Choose, then see how an experienced engineer reasons. There's no score and no right path for you. It's just a feel for the work.

Situation 1 of 3

Your fraud model has 99.2% accuracy. Your manager is thrilled. Only 0.5% of transactions are fraud. Thoughts?

The roadmap

From your first line of code to people using what you built

Tick off steps as you go. Finishing a quest reveals a sealed insight, and finishing a stage unlocks a capability. Everything is saved in this browser.

Before you start: where to use AI (and where not to)

Use AI freely for

  • Explaining a concept, an error message or someone else's code, then asking follow-up 'why' questions
  • Quizzing you: 'ask me 5 questions on what I just learned'
  • Reviewing code you wrote: bugs, edge cases, security holes

Use carefully

  • Writing code for a concept you're learning: write it yourself first, then compare with the AI's version
  • Choosing libraries: AI may suggest outdated packages, so check the docs and the last release date
  • Facts and numbers: verify anything you'll put in a README, resume or memo

Don't use AI for

  • Code you can't explain line by line. If you can't explain it, you don't own it, and interviews will show it
  • Skipping the struggle. The 20 minutes you spend stuck is when learning happens
  • Deciding what to build or what your analysis concludes. That judgement is your job
Type the first version yourself. Delegate the second. Review every one.

Every quest has its own "use AI for / avoid" note. The full guide is in the AI Playbook.

Remaining work
~257h
At this pace
18 weeks
20 quests

Sprint Zero

Five days. Python, the maths you'll actually use, and the core libraries. You'll go deeper while building.

5 days4 quests~23 hours
Finish this stage to unlock: You can manipulate data and arrays in Python and you know where every major ML tool fits.

Learn by building

Eight builds from scratch to state of the art. Each one makes the next make sense.

~6 weeks8 quests~68 hours
Finish this stage to unlock: You can train, fine-tune, evaluate and serve ML and LLM models, and explain every step.
Job signal: Start applying for ML and data internships now, especially at startups and GCCs. How to apply โ†’

Company-style builds

Real ML briefs: an ambiguous problem, a business goal, and a definition of done. Choosing the approach is up to you.

~4 weeks3 quests~76 hours
Finish this stage to unlock: You can take a business problem to a deployed, monitored ML system with a defensible design.
Job signal: Apply broadly now: ML engineer, applied scientist intern, AI engineer roles. How to apply โ†’

Architect mode

You know how the pieces work, so stop typing every line. From here on you design, write the spec, direct AI agents and review their work like a tech lead.

~1.5 weeks2 quests~17 hours
Finish this stage to unlock: You can design a system, break it into slices, direct AI agents to build it and catch their mistakes before users do.

Your meaningful project

One project that real people use beats ten tutorial clones. This becomes the story in every interview.

4โ€“6 weeks3 quests~73 hours
Finish this stage to unlock: You have shipped something people actually use, and you can tell the story of how you built it, measured it and improved it. That's the whole job.
Job signal: This project is your headline. Put it at the top of your resume and LinkedIn and talk about it in every interview. How to apply โ†’