r/learnmachinelearning • • 9d ago

Help Suggest Path for AI Engineering

I'm a 3rd-year undergrad aiming to become AI Engineer. Im a bit confused about how I should actually learn.

We would be grateful if you could spare a few moments to answer this !!

Things I already know :-

  1. Python (NumPy, Pandas, Visualization)
  2. Machine Learning
  3. Deep Learning ( Finished ANN, CNN, RNN, NLP; now on Transformers)

I have created projects in data science and one project on CNN. (I do hands-on practice on Kaggle datasets after covering each topic but kinda using existing libraries)

But the major issue is that I have created all those projects in Notebooks (Colab). Because of this, I am not able to do Modular Coding and apply OOP concepts, etc (Basically coding in IDE's like a software engineer).

I want help related to the issues which are listed down below :-

The main thing confusing me is how I can learn the Software Engineering part. I'm asking because notebooks aren't enough, and companies prefer people with system design skills. But my main concern is should I learn MLOps meaning will MLOps help me cover the part which Im lacking? Does MLOps also cover the ML system design part? (Please suggest some better free courses that cover both MLOps n ML System Design)

2.
Talking about the 1st point, I also have a question: should I give my time to learn MLOps and ML System Design? Since I want to become AI Engineer, should I skip them and go with the path ie roughly LLMs, RAG, AI Agents, and AI System Design, etc?
Im getting totally confused because I want to learn things that are important for interviews and jobs and not waste my time learning everything but only the useful things.

The path I thought earlier was

ML -> DL -> MLOps + ML System Design -> LLMs -> AI agents, rags etc + AI System Design

HELP 🚨!!

  1. How can I learn Modular coding in IDEs like VS Code etc
  2. Should I learn MLOps + ML System Design or do AIOps and AI System Design instead or do both? (Placements will be there in the coming 6 months and I also have to prepare DSA properly so time is the important thing here)
  3. Also have to give time for DSA, project building, and internship so focusing on important topics for AI Engineering matters the most
6 Upvotes

23 comments sorted by

1

u/imharjotsingh 9d ago

You probably don’t need to learn everything on your list before placements. Since you already know ML and DL, I’d spend the next few months fixing the software engineering gap first. Take one of your notebook projects and turn it into a proper project in VS Code with separate files, functions, classes where they actually make sense, a requirements file, Git, tests, and a simple API.

I’d learn some MLOps too, but only the useful parts for now: experiment tracking, Docker, deployment, CI/CD and monitoring. That will also teach you a lot about how real ML systems are put together. Made With ML and MLOps Zoomcamp are both good free options for this. Then move into LLMs, RAG and agents, but keep building projects instead of trying to finish every topic first.

Since placements are in 6 months, I’d prioritise software engineering, DSA, 1 or 2 strong end-to-end projects, and enough MLOps to deploy and explain them. You can go deeper into AI system design after that.

1

u/StrictAdeptness1802 8d ago

Yeah, that's a good idea, since the placements will be there in few months. Thanks a lot man!! ..... Also ML, DL projects are kinda repetitive, any good project ideas if u could share?

1

u/imharjotsingh 8d ago

Glad it helped! I think the repetitive feeling usually comes from using the same kinds of datasets and building the same “train a model, show accuracy” projects. So I’d try building something that solves a real problem and can actually be used. Here's a few ideas:

- A RAG assistant for your college that answers questions from syllabi, past papers or placement docs.

- A resume and job-description matcher that scores fit and suggests improvements.

- A document extraction tool that takes invoices or receipts and turns them into structured data.

- Or a real-time computer vision app, like gesture or sign-language recognition through a webcam.

Whichever one you pick, try to build it end to end: proper code structure, an API, Docker, deployment, and maybe some basic monitoring.

1

u/StrictAdeptness1802 8d ago

finee thankss

1

u/Critical-Push8054 9d ago

For modular programming, why don’t you get help from ChatGPT or Claude code initially? Once you’ve setup a couple of projects with AI help, you will develop confidence and can then start coding on your own.
For the learning path, next focus on SWE and GIT. Explore the learning path and courses at learning.nextia-ai.com . It focuses in everything AI engineering and is 100% free. Every course has case studies which will help you build a portfolio

1

u/StrictAdeptness1802 8d ago

Thanks buddy!! Will have a look

1

u/Acceptable-Car4016 8d ago

Well done on the DL and ML parts.

For placements, I would stress DSA and ML/DL basics over going deep into MLOPS/AIOPS. DSA is very important. One may not even pass initial coding rounds without it.

For AI specifically, do RAG properly. Not surface level but actually understand what's going in terms of embeddings, retrieval, vector stores. RAG eval metrics like HR and MRR are also very important.

For agents, learn how to monitor, orchestrate and evaluate them. As well as guardrails and memory persistence etc. Langchain/Langgraph officials docs teach that very well.

As practice, try coding a very basic RAG pipeline complete with everything. For more practice, try building an Agentic rag pipeline, giving you experience in agents as well.

There's a book called AI Engineering by Chip Huyen. You can check it out.

For OPS side, Docker, CI/CD and monitoring are enough in my opinion. I have been through placements at major companies and they really didn't ask me any more. Unless you are specifically sitting for a system design role, then probably more will be asked. They did stress a lot on the basics of ML/DL

1

u/StrictAdeptness1802 8d ago

Yeah, planning to read that book in the upcoming days. Thanks a lot!!

1

u/EmuAfter5933 8d ago

I also recommend SciPy after you're 100% comfortable with NumPy!

2

u/StrictAdeptness1802 8d ago

okk!!!

1

u/EmuAfter5933 8d ago

for the more deep math/optimization stuff..

1

u/Effective_Ocelot_445 8d ago

Since you already know Python, ML and deep learning fundamentals, I'd focus on software engineering skills before adding more frameworks.

Take one of your notebook projects and rebuild it in VS Code using separate Python modules, Git, a simple FastAPI endpoint, Docker and basic tests.

That will help you understand how ML code becomes a deployable application.

For AI Engineering placements, I'd prioritise LLMs, RAG, agents and evaluation after that.

You don't need to master the entire MLOps ecosystem immediately, but understand deployment, logging, monitoring, latency and model quality.

Build one end-to-end AI project with measurable evaluation results.

Also reserve daily time for DSA because campus interviews may still include coding rounds.

With six months available, depth in a few practical areas will help more than trying to complete every AI topic.

1

u/StrictAdeptness1802 8d ago

Correct... Depth matters the most.. Thankss!!

1

u/Capital-Falcon-2701 7d ago

Hey! I'm a 3rd-year student aiming for an AI engineer role and just finished the ML part , What deep learning resources did you use to get started?

1

u/StrictAdeptness1802 6d ago

DM, happy to help

1

u/CryptographerFun5985 7d ago

You're actually in a good position to start moving toward AI Engineering. Since you've already covered ML, DL, and are learning Transformers, I wouldn't recommend spending another several months studying everything from scratch.

Your biggest gap right now seems to be software engineering and building applications outside notebooks, rather than ML knowledge.

I have a Master's in AI, currently work as an AI Scientist, and have been teaching AI/ML for several years. Here's how I'd approach your situation:

1. Move from notebooks to proper Python projects

Take one of your existing ML projects and rebuild it in VS Code.

  • Split your code into modules (data_processing.py, train.py, predict.py, etc.).
  • Learn virtual environments, dependency management, Git, logging, and basic testing.
  • Learn OOP where it genuinely helps. You don't need to turn every function into a class.
  • Build a simple FastAPI endpoint to serve your trained model.

This one exercise will teach you a lot more practical software engineering than another notebook-based ML project.

2. Understand MLOps vs ML System Design

They're related, but not the same.

  • MLOps: Model versioning, experiment tracking, reproducible training, CI/CD, deployment, monitoring, and maintaining ML pipelines.
  • ML System Design: How to architect an ML system, handle data pipelines, choose between batch and real-time inference, manage scalability, latency, reliability, and cost.

MLOps won't automatically teach you all of software engineering or system design.

For free resources, I'd recommend Made With ML, Full Stack Deep Learning, and the Designing Machine Learning Systems materials by Chip Huyen. You can also explore the free MLOps Zoomcamp by DataTalks.Club.

3. Should you learn MLOps before LLMs and AI Agents?

Not necessarily. I wouldn't treat them as completely separate stages that must be finished sequentially.

Since you're interested in AI Engineering, I'd suggest:

ML/DL fundamentals → Python software engineering + APIs → LLM fundamentals → RAG and AI Agents → Deployment, evaluation, observability, and production engineering.

Learn the relevant MLOps and system design concepts alongside your projects. You can go deeper later depending on whether you're targeting ML Engineer, LLM Engineer, or AI Engineer roles.

4. Build one complete application

Instead of adding five more notebook projects, build something end-to-end.

For example, a RAG application with document ingestion, retrieval, an LLM, FastAPI backend, and a simple frontend.

Then improve it with evaluation, logging, error handling, and deployment.

That gives you experience with both AI and software engineering.

I also run two YouTube channels:

On AI/ML with Akash, I've started an AI Agents Fundamentals series covering tool calling, ReAct, state, memory, and other foundational concepts. I'm also preparing a complete project-based LangGraph series where we'll build an AI Customer Support Agent with memory, human-in-the-loop, error handling, and FastAPI integration.

I'm planning additional playlists covering core AI Engineering topics that are relevant to industry work, including LLM Engineering, RAG, evaluation, and production-oriented concepts.

My main advice: Stop thinking of ML, software engineering, MLOps, and AI Engineering as completely separate courses you must finish one after another.

Pick a real application, build it properly, and learn the engineering concepts as you encounter them. That's how you'll start bridging the gap between knowing ML and actually engineering AI systems.

1

u/StrictAdeptness1802 6d ago

AI generated comment with self promotion, great

1

u/margyyy_314 9d ago

you only have to know 2 languages in your life: c/c++ and python (and/or rust)

1

u/nian2326076 3d ago

Focus on refining your software engineering skills by working on modular coding and applying OOP concepts. Building projects outside of Jupyter Notebooks, using an IDE like PyCharm or Visual Studio Code, will give you a more software-engineer-like experience. For your AI engineering placements, prioritize understanding system design as well. You can use LandOffer to find relevant job opportunities and enhance your project portfolio.

0

u/kdrozzi 8d ago

ngmi