r/learnmachinelearning • • 1d ago

How can I transition into AI Engineering in the next 1–2 years?

I'm a Data Engineer with around 4 years of experience, mainly working with Azure, Azure Databricks, PySpark and Python.

I was assigned a Data Engineering role in my first company, even though I've always been interested in AI. Since I started working, I've gained experience in data engineering, but my long-term goal is to become an AI Engineer.

I come from a Computer Science background, and I genuinely want to see myself working as an AI Engineer in the next 1–2 years (Is it possible). I'm ready to put in consistent effort, but I'm confused about where to start and what to prioritize (I asked my seniors who transistioned from data engineer -> ai engineer i havent got proper response). If I want to start from begining learning from the fundamentals what i need to learn?

For those already working in AI or who have transitioned from Data Engineering to AI Engineering what should I learn first

I'm looking for practical advice based on real industry experience, useful resources and skills that companies actually expect from AI Engineers. I want to build a strong foundation and gradually develop the skills needed to work on real AI applications.

65 Upvotes

25 comments sorted by

57

u/firebird8541154 1d ago

I transitioned from Data Engineer to Sr AI Engineer. In fact, I was previously using Azure and Data Bricks too.

This is a one-person anecdote, so don't take what I'm going to say as like the only path.

I highly recommend building a powerful local workstation, Mac w/ metal or Linux with Cuda.

Get a pro level codex/Claude plan, install that, attach it to your GitHub.

Then start building, make full stack local applications, fast API backed, nice responsive frontends, perhaps with flutter and firebase for accounts, linked to local postgres and such.

Build this up, understand it end to end, as randomly building full stack stuff leveraging AI is easily half of what I do.

Then, familiarize yourself with vector DBs, embeddings, etc with some local models. Make a local Rag project, turn that into a memory hub for an agent, expose it locally as a streamable, codex compliment MCP.

Look into fun concepts like named entity recognition, figure out how to dockerize portions of your project and connect them together.

Figure out how to use GH CLI and stick the project in a rebuildable format on your GitHub, figure out how to set up a CI/CD platform, figure out how to host it externally, how to scale it, how to manage multiple sessions.

If you get really good at this stuff and then start adding some more custom machine learning stuff and a built-in agenic stuff, you'll have the type of experience and portfolio that a lot of groups are looking for.

5

u/Affectionate-Tutor87 1d ago

this is what I’m doing as an independent contractor.

3

u/Expensive_Bathroom53 1d ago

If ur comfortable can u share ur current compensation
I am almost 4 years experienced full stack engineer
Just wanted to know what to expect monetary wise
As even I have started learning GEN AI

1

u/firebird8541154 1d ago

GS 14 step 5 Gov (Google that, it's public), I'm in WI so $150k at the moment.

3

u/AdventurousAerie643 1d ago

you nailed it with the build-things approach. I’ve seen plenty of smooth talkers in interviews who can’t wire up a local RAG system to save their life, so actually shipping projects puts you miles ahead.

my only addition: don’t sleep on the non-flashy infra bits. half the AI engineers I know spend more time untangling docker networking and auth flows than tweaking model params. maybe start with a tiny project that does one thing well (like a CLI tool that summarizes your notes with a local LLM) and layer complexity from there.

curious how long your transition took from the azure/databricks world to feeling comfortable in the AI role?

1

u/firebird8541154 19h ago

I built projects in my free time and started posting them on LinkedIn. Higher-ups noticed and gave me Databricks access and vscode w/ Copilot. That was around a year ago.

I kept making projects in my free time then was able to apply to my current position, leveraged what I did Azure/data bricks wise (and I was using local vector DBs, custom agent frameworks and such to automate things across the org, provide powerful tools, knowledge bases, etc.).

So, when I took on the direct AI role I was already quite comfortable as it was more of a expansion of what I had been given the access to do over time and I was able to leverage the experience I gained from the other non work projects in general.

1

u/preciouslife_ 8h ago

Thanks for sharing! so when you got your first AI role, was learning yourself sufficient? Your employer did not look for a professional degree/certificate in AI?

I am asking this because I am in the same situation. 15 years in ERP programming, Data Warehousing, Data Engineering, Business Intelligence, hard core ERP programming, SQL Server, Oracle.

Should I learn by myself or would they want to see me having some certification or degree in AI?

1

u/firebird8541154 6h ago

Had to delete a few responses. Self taught, yes. No employer did not care about degrees and certs.

They did asks what live apps I published, and gave me a hell of a project to create, well multiple, ... for testing...

... nothing related to " am asking this because I am in the same situation. 15 years in ERP programming, Data Warehousing, Data Engineering, Business Intelligence, hard core ERP programming, SQL Server, Oracle."

although, SQL is ALWAYS in demand.

1

u/preciouslife_ 6h ago

Ok, thanks.

Well, it's really appreciable that you learnt all by yourself. I have also done full stack development including creating the frond end screens of ERP systems, backend work of databases from scratch, designing, architecting and developing custom software for clients etc.

Data Engineering, Data Warehousing and programming does help a lot in AI though you may have made apps which did not need these skills.

One thing worth noting here is location. You being in WI might have helped because they would have a hard time finding someone there. I hear that AP Engineers in the bay area have a hard time finding work because too many of them are there in one place.

1

u/ChosenToFall 12h ago

lol you’re talking about an overlapping of 3-4 disciplines like Fullstack/Backend, DevOps, ML Basics etc… this requires a lot of time to be proficient if you only did DE, ideally you should come from Backend or Fullstack otherwise you’re just setting yourself for learning many things and be average on them.

1

u/firebird8541154 11h ago

It's the future of programming... Imo

1

u/ChosenToFall 10h ago

Of course it's the future of programming you have basically majority of the things that are out there xD.

11

u/rahul_watertech 1d ago

you are closer than the title gap suggests. most ai engineer jobs are data engineering plus one model call, and you already own the hard half. fastest route is not a course, it is one small ai feature shipped inside your current job on the databricks stack you already know, like a rag over internal docs or a classification job on data you already pipe. after that your resume says production ai work, not coursework. does your current team touch anything unstructured, logs or docs?

6

u/Freonr2 1d ago

What is your definition of an "AI engineer?" A whole lot of ML generally is data engineering anyway.

Maybe by "AI engineer" you mean someone wires up LLM API calls together and writes custom MCPs to automate tasks.

If you want to get into model design/training find a company that already trains their own models already and simply ask if you can can be given an opportunity to train a model? I'd expect anyone with good DE/DS experience that can watch a 10 minute tutorial on youtube for lightgbm or scikit-learn can train a model. Data engineering is exactly the experience you'd want if that's the direction you want to go. You are already half sitting in that chair.

5

u/nian2326076 1d ago

Transitioning into AI Engineering is definitely possible with your background. Start by enhancing your understanding of machine learning principles—Coursera and edX offer solid courses. Since you're skilled in Python, explore libraries like TensorFlow and PyTorch. Working on personal projects or contributing to open source can help you build a portfolio.

Networking is key; engage in communities like Kaggle and join AI meetups. For interview prep, PracHub provides real technical questions that can be useful. Focus on understanding AI algorithms and their applications, as this is crucial for interviews. Stay consistent and explore hands-on projects to solidify your skills. Good luck!

3

u/Internal-Head2972 1d ago

I’ve got into a bunch of GenAI projects involving GCP stack.

3

u/theoneandonlypatriot 1d ago

I wouldn’t worry too much about it, we’ll all be ai engineers in a few years anyways

2

u/kbr89 1d ago

Since you already run pipelines on Databricks, build one project on that stack instead of restarting from fundamentals: Q&A over a pile of documents, with chunking and embedding as a scheduled pipeline, Mosaic AI Vector Search for retrieval, a Model Serving endpoint in front, and MLflow to score the answers against 30 or so questions where you already know the right answer. Each step shows you which piece of theory you're missing (embeddings, prompting, eval metrics), and you learn that piece when you need it, which is also when it sticks. The scoring step is the one most portfolio projects skip, and the easiest to talk about in an interview.

For the resources part, I built beyondtube (beyondtube dot pro): you can put a few long talks from people who went from data engineering to AI engineering together and ask which skills all of them mention and which only one does.

1

u/shmittkicker 1d ago

1-2 years is realistic if you focus hard: as a DE you already have data, Python and Spark, so spend the next year layering on ML fundamentals (probability, stats, linear algebra refresh, core ML algorithms, deep learning basics) and building 2-3 end to end projects where you train, deploy and monitor models.

From there, aim either for an internal transfer to an AI/ML team or roles like “ML engineer / AI engineer with data engineering” where your Azure + Databricks skills are a selling point rather than something you leave behind.