

Richie helps individuals and organizations get better at using data and AI. He's been a data scientist since before it was called data science, and has written two books and created many DataCamp courses on the subject. He is a host of the DataFramed podcast, and runs DataCamp's webinar program.
Chat with AI Richie about every episode of DataFramed - all data champs welcome!
Key Quotes
If you do wanna get a job, you need to change something in your approach, you need to take accountability for it. If you apply to 20,000 companies, someone's gonna call you back. If you build a really cool app that gets 100 users, somebody's gonna notice. If you post on LinkedIn for six months and share stuff that you're doing, that's gonna help you. There's lots of things you can do to improve your situation, and so many people that are probably a lot dumber than you have gotten tech jobs simply because they put in more work, and they didn't complain about the environment.
I always just go back to communication because ultimately what sets you apart from an AI model is what you say. The way you communicate, the fact that your little box pops up in the Slack message and says something, not an AI model, and people trust you more because of who you are. The fact that you're actually a human being.
Key Takeaways
AI engineering roles are mostly standard software engineering plus a practical AI layer. Strong system design, APIs, Python, and Docker or Kubernetes, plus knowing how to pick a model, use RAG, and handle rate limiting and context, count for more than a PhD or advanced math.
Proof of skills beats paper. A certification is a nice-to-have, so pick two or three targeted at the role you want (such as AWS for AWS jobs) rather than collecting twenty, and put the rest of your effort into real, practical projects.
Once you're hired, you're judged on ownership: making decisions without being handheld, communicating in clear structured updates, and making your contributions visible. Agree up front what success looks like in the first three months so you have something concrete to point back to when you ask for a raise or promotion.
Liên kết từ chương trình
- DataCamp Certifications
- AI Plays Flappy Bird (NEAT) project
- Nate Herk's YouTube channel
- David Ondrej's YouTube channel
- Jack Roberts's YouTube channel
- Sentdex's YouTube channel
- Connect with Tim
- AI-Native Course: Intro to AI for Work
- Related Episode: How to Have a Machine Learning Career in 2026 with Marina Wyss, Senior Applied Scientist at Twitch
Bản ghi
Richie Cotton: Hi Tim, welcome to the show.
Tim Ruscica: Thanks very much for having me. Excited to chat.
Richie Cotton: Yeah, great to have you here. AI engineering is maybe the hottest role around at the moment, but it feels like it's lots of different roles smushed into one job title. So do you wanna talk me through like what are the different facets of being an AI engineer?
Tim Ruscica: Yeah, it's funny, like AI engineer can mean so many different things depending on where you're working or who you ask. So I would say that- No, okay, maybe we can break it into two or three different categories. I would say one of them is gonna be more your math heavy, more PhD level, doing, like, actual, building an LLM, right?
Or writing ML models or doing, like, all this kind of fancy technical stuff that, to be honest, probably neither of us really know how to do and most people are not doing commonly unless they went to school for this. And then you have the much more practical side where you're taking all of that work that's been done by kind of the geniuses of the world and integrating it into applications.
And I would say that's where most AI engineers are lying nowadays, where you're using an LLM, you're using a model, you're using a Hugging Face transformer, whatever, and you're building it into an app that already exists. And actually, what that means, and I'm sure we're gonna dive into that, is that a lot of the work you're doing isn't really raw AI, ML related stuff.
It's more kind of gluing the pieces together and knowing some of the concepts and how they play, which gets into deployment, scalability, APIs. I'm sure we'll dive more into it, but that's how I view the field right now. Super technical, lower level math stuff, and then more of kind of integrating and that layer on top.
Richie Cotton: Absolutely. And these feel like very different roles then. One of them is is I guess more closely related to the traditional machine learning background but maybe at, at a larger scale, and the other one's closer to software engineering. So I guess o- on that note since AI engineer's quite a new role, people are generally transitioning into AI engineering from somewhere else.
Do you want to talk me through what background you need to get a, a job as an AI engineer?
Tim Ruscica: For sure. So I've done a lot of videos on this. And again, I think the, the term is so vague that obviously do your research and see, what role you're targeting, what companies you're looking at, because they're all gonna have their own requirements.
But generally speaking, it's gonna be the exact same list of stuff that you would normally need for a mid-level software engineering role plus some of those AI concepts. So we'll go through some of them. For example, system design, right? Okay, how do you design an API? How do you have maybe some basic load balance or some caching?
How do you think about scaling a system up that gets a little bit larger, especially when we're talking about inference of things like LLMs, right? And then we have kind of the AI layer where we're talking about, okay, how do we pick which model to use? How do we verify that we're getting the correct result?
How do we rate limit something to make sure we're not going through too much? How do we manage the context or set up things like RAG retrieve augmented generation, or connecting to external tools, adding MCP servers? Again, really depends what it is that you're building, but it's take all that traditional software engineering stuff Add that practical AI layer in terms of how do I call these APIs, how do I work with LLMs, how do I get the response back in a correct format, and combine those two skills together.
And then of course, be able to demonstrate to an employer that you actually know what you're talking about. And then I would say, to get a little bit more specific, a lot of that now has to do with using Python, for example. Most of your LLM, wrappers, SDKs, and stuff are gonna be in that language, so being really comfortable there.
And then being familiar with maybe some of the frameworks depending on what you're using. And even, Docker, Kubernetes, all those things are still equally as important when you get into the era where you're, calling LLMs thousands of times per second, depending on the app you're building.
Richie Cotton: It is basically it's all your standard software development skills, and then a few extra ones on top of that. It was interesting that the Python got mentioned towards the end. I think there's a, a lot of open-ended questions about is coding s- still worth it? Do you need to have coding skills?
Do you wanna talk me through what your position is on what do you need to know about programming?
Tim Ruscica: Yeah it's funny 'cause if you would've asked this to me, three years ago, I would've said, "Yeah, you need to know every piece of syntax. You need to be, like, expert still in your domain, know the language."
And while I still mostly believe that, it's definitely shifting pretty quickly, especially as I see even people that I know that are in this industry that don't actually have any real practical coding skills that are building incredible applications. So I would say if you wanna just, if you wanna be a software engineer, you wanna work for a large company, absolutely you should still know the fundamentals of programming.
Does that mean you have to memorize every single piece of syntax? Does it mean you have to write all of this code by hand? Absolutely not, and I think you can now skip maybe a lot of things that I spent a bunch of time learning back, 10 years ago and really accelerate the journey. But ultimately, my kind of test is if I gave you a piece of code and you weren't connected to the internet, could you read through it and explain to me what the code is doing?
So there's a lot of things that you do need to know in order to do that, and there's some things that now you can skip. You don't need to know, the exact method name and all the parameters and things that maybe before would've actually helped you speed up and write code a lot faster as a developer.
So that's where I'm standing. I would say now, and even myself, pretty much all the code I write is with AI. I try to do it in smaller pieces so I can actually review it and have, still be in the driver's seat in terms of what's going on and the high-level decisions. And it's tricky 'cause if I were to just to recommend, "Hey, do everything with AI," people get this massive mess that's not maintainable in the future.
So it's a really weird place that we're at right now. Yeah, and it's really tricky to navigate and I don't... It's always difficult for me to suggest to beginners what should you do nowadays. I know that's not the question, but something I'm always raveling with in my mind what is software development gonna look like even six months from now?
And maybe this answer's already gonna be outdated, so who knows?
Richie Cotton: Yeah, it's certainly changing very quickly and even, yeah, a year ago it's like- It was, AI was very unreliable in terms of generating code, but it's got to the point where it's oh yeah, you can actually build something that's pretty good with minimal intervention.
So I guess related to this is do you need to be able to review the code that has been generated by the AI? What sort of skills do you need to be able to do that effectively?
Tim Ruscica: Yeah. To answer that, yes, absolutely, you should be reviewing it. I think first of all, there's a skill in terms of how you get the AI to generate the code and also how much of it you generate at once, because it's just impossible even for experienced software engineers to review 20,000-line pull requests, right?
Y- your mind just can't grasp that much information and review it. So I would say first of all, the first skill is, like, how do we get AI to make small targeted changes that do save us time but actually keep saving us time 'cause it doesn't require us 20 hours to review. So that's the first side of it, how you do that correctly.
And then the second side of it, honestly it's a, I don't know, maybe a bad answer, but the way you get experience reviewing code is reviewing code, right? And how do you do that? You need to just read a lot of code, write a lot of code, and also see a lot of mistakes that you've made yourself or other developers have made so that you don't make those again in the future.
The only reason I know that this function is poorly written is 'cause I've written a function like that before, right? And I've seen what that actually does when I deploy it out or I've had, my mentor at, Microsoft when I worked there rip it apart and tell me, "Never do that again."
So there are a lot of learnings that you really only can get by making those mistakes. So how do you do that? You just gotta make them as fast as possible, right? Push out a lot of code, build a lot of things, see where stuff breaks, and review all of these AI's decisions and realize, hey, this isn't just God.
It doesn't know every single answer, and sometimes you're actually correct and you've gotta guide the AI. And I've had AI make some crazy things that it's 100% confident in, and I'm thinking like, "Okay, if I was a complete beginner, there's no way I would know this mistake." But I know from my experience we can't do this.
Let's fix that and let's go back. So I would say just racing to get that experience as quickly as possible and put yourself in an environment where you're working with other developers who already have the experience so they can rip apart all the stuff that you're doing that you might not already know, right?
Richie Cotton: Yeah, I love that idea of just trying lots of things, just building lots of things and then, Take having that feedback loop of "Okay, this broke, and how can I do things better?" I guess related to this, so we've talked about some technical skills, and one thing that's commonly suggested is you need some domain skills as well.
What does that mean, and what might you need to learn? Yeah, so when I think of domain skills, I think of the maybe auxiliary skills that aren't specifically software engineering. So that could be even how do you communicate effectively as an engineer with other people? How do you send a Slack message that's actually gonna get your point across, right?
Tim Ruscica: Or if we're talking about a specific industry, let's say you're building... You're an AI engineer for a robotics company, you probably need to know a little bit about robotics, right? Or what's the hardware stack they're using, or what's the goal you're actually trying to achieve. So I think it's super vague, and we'd have to narrow down on what role are we talking about, but it's everything outside of that.
And I would say now especially, those social skills, the way you work with people, the way you communicate, even how you formulate an email, there are these small little things that really do make you stand out as a developer, especially as the coding stuff is becoming more redundant and done a lot by AI.
And just the way you work with people, that's the thing I notice right away when I work with anyone. How do they communicate? How clear are they? What do they ask for? What kind of questions do they ask me? Do they have a deep understanding of the problem? So that's what I would focus on outside of, again, there's small little details you'll need to know about any industry depending on what you're writing the code for.
Richie Cotton: Absolutely. I feel like you just terrified a lot of people who are like, "Oh social skills? I'm just I wanted to talk to the AI, not to other humans." But it is incredibly important, like you're always gonna be working as part of a team, so yeah, those team working skills do seem incredibly essential in, in most roles.
Okay so yeah I like the idea of having like some robotics skills if you work in robotics or whatever you need to understand what the business is you're in. Are there any more soft skills that you think are useful to have?
Tim Ruscica: Yeah, I think- Again I always just go back to communication because ultimately what sets you apart from an AI model is what you say, right?
The way you communicate, like the fact that your little box pops up in the Slack message and says something, not an AI model, and people trust you more because of who you are, right? The fact that you're actually a human being. So I would say really just focusing on being really clear in the way that you communicate.
I've been in a lot of engineering teams where it's very messy. There's ... People aren't very clear. They're very vague, where we spend 10 minutes just trying to understand what question someone's asking or what the bug was or what's actually going on, and just having a logical structured thinking process when it comes to even giving an update, right?
Or asking a question or d- describing a blocker or how you communicate on a standup, right? Someone comes to you, "Hey, Tim, can you give me an update on, what you worked on last week?" Having that kind of prepped, ready to go, and just giving the important information that someone needs to know to proceed.
It's hard for me to go into many other skills. Again, depends what it is you're working on. I guess a small one I could say is maybe not soft skill, but how you work with Git and GitHub I think especially now is super, super important when we have so many rapid changes happening all the time.
So especially now understanding branches, being able to revert back to something, merge conflicts, that's one that I've seen become more and more important in that while AI can do some of that, you've still gotta know a lot of those commands and how you don't completely mess up, the work tree that you're on.
So I guess I'd throw that out as a, a kind of a bonus there.
Richie Cotton: Absolutely, yeah. Git and GitHub or the sort of version control tools is incredibly important for anything if you're writing code. But also you mentioned just how to communicate within a standard meeting. Meeting skills in general, I think this is broadly applicable even beyond whether or not you want to an AI, want to be an AI engineer.
So yeah, do you wanna talk me through what are your top tips for doing well in meetings?
Tim Ruscica: Yeah, again, it's specific 'cause it depends where you're working. I would just say- Being clear and unambiguous. And it's funny 'cause I remember when I was in university, I actually took a class, like technical writing for engineers.
And I used to think, and most people still do university is useless. You're learning a bunch of stuff you're never gonna use. But the one takeaway I had from that class that I still try to apply today is writing things and speaking in such a way that there's no way that someone could misinterpret or misunderstand you, right?
And you just say something so clearly where you've actually really thought through the way that you're gonna describe it and the way you're gonna discuss it, so that you can just get the point across quickly, and you don't have any potential mistakes or make up- mix-ups based on kind of the way you've communicated something.
Blanking on a great example for you right here on this call, but even the way that I would write an update, for example, in a Slack channel, which now is happening all the time, I would start with a quick header. Okay, Tim's update for this week, right? And put like 07/31, but even rather than that, I might do something like, oh, July 31st, just so it's clear and we don't have any mix-up on day, month, year, whatever.
Then I'd have a quick bullet point like, hey, this is a quick summary of whatever I'm talking about, some action items, questions, blockers, and put like subheadings, formatting, just so it's really easy for someone to parse through it and read it, and just try to be consistent with that format, even if it's just the way that I speak, so that they know, hey, this is what Tim's update's gonna look like.
This is how I can parse it. This is what I can expect in the future. Even if you're writing an email, at the end of the email, having what I need from you, three quick things, just so they can quickly go to that and give you the answer, and making things as easy for people as possible. In a meeting, I would say have your own little notes on the side, Notepad file, in a Claude Code session, whatever.
Hey, this is my update. You can literally just read off of that or at least have some bullet points that you wanna hit, so you're not rambling, like I am on this answer, and you give, the direct point. 'Cause in meetings, everyone just sits there and wanna talk forever. Let's just get through the important stuff.
In these 30-minute meetings, we can make five minutes if everyone comes prepped with what it is they wanna share, right?
Richie Cotton: No, I love that. Everyone's just deluged by information, so being concise and being kind to the people who are receiving your information, so you keep it short and clear is yeah, that, that's gonna take you a long way, I think as a skill.
Tim Ruscica: And it will just make you stand out. A lot of people just send these huge, big paragraphs, and it's "What's the point? Give me the TLDR. What do you need from me?" So I like to just lead with that, and if there's other details someone else wants to read, fine. But ultimately, I just wanna move things as quickly as possible, so that's typically the way I communicate that I find most people appreciate, generally.
Richie Cotton: Yeah, I definitely have colleagues where I'm like, sometimes I'll copy and paste their Slack message and into a, a AI and just be like, "Can you summarize this message for me, please?" Yeah that's one of the, one of the great uses yeah less rambling from the, your colleagues. All right before you mentioned that just building a lot of stuff is incredibly useful for getting hired.
I suppose related to this is the idea that you can have a, a portfolio to show off your work. Do you have a sense of what goes into a good AI engineer portfolio?
Tim Ruscica: Sure. So- Portfolio is a difficult thing because there's, especially in AI engineering, there's a lot of really interesting stuff you can build that doesn't really present that way, right?
If someone's gonna look at it. So the first rule I typically have with a portfolio Is it needs to be, like, dead simple to understand and to access. I was hiring software engineers before, and even AI-adjacent guys, and they would send me just a GitHub link. And I'd have no idea how do I run it, how do I view it.
Is the project up here? What's actually going on? It's like they expected me to spin up a Docker container on my own computer and get a deployment of a VPS and have a MongoDB database and put in some keys in an ENV file. If you have anything like that, no one's ever gonna view it or ever gonna run it, and the most it's gonna do for you is just be a talking point if you actually get into an interview, right?
So the first thing with portfolio is just make sure whatever it is that you're building, build some kind of visual layer and interface on it, even if it's just an animation showing what's going on in the backend, so that someone can really quickly understand what it is that you've actually done.
That's the biggest point I can give, 'cause most portfolios never even get viewed 'cause they don't have that, right? The second side of things is I would just make sure that whatever you do solves a clear problem, and again just makes sense to the interviewer. If you do some really random, obscure, crazy backend thing and it takes you five minutes to explain it, it doesn't matter how complicated it is, they're just not gonna get the point.
So for example, one of my best projects I had, it was actually an AI project, was AI Plays Flappy Bird. That's literally what I called the project. It's one of my most viewed videos on YouTube. And if you read that on my resume, you're like, "Oh, I get it. It's an AI that learns how to play Flappy Bird."
And then I just added a few details. Oh, I used the NEAT algorithm in Python to build a self-evolution loop of AI models that, evolved it and learned how to play the game. And you get it right away, and you can view it and you can see the cool animation and it's a graphic. And that got a lot of looks and a lot of questions when I was interviewing, even though that was, like, five or six years ago.
So from there, I would then say just make sure you have some of those kind of big keywords right in the description so they get it. Hey, integrated with OpenAI API, connected with LangGraph to build a simple AI agent that handles emails for 1,000 people. Whatever, right? Something like that.
And then the rest of the portfolio project you can explain. It will be a talking point that you can go into in the interviews. 'Cause generally speaking, the portfolio might get you in the door. It might get someone interested. They're not gonna dig through and read all the GitHub code.
It's gonna then be up to you to explain it, talk about the challenges, the mistakes. You get the idea. So make sure it's deployed, make sure it's simple to understand, make sure it's visual, and then of course, try to build something that's unique, that not a million other people have built, with some of the keywords, languages, and technologies that company's gonna be hiring for.
If they're asking you need Docker and Kubernetes deploy it with Docker, right? Have a Kubernetes cluster set up, and then you can talk about that and prove that you have those competencies for the company, right?
Richie Cotton: No I love that idea of just make it really simple for people to understand, because I think a lot of hiring managers, like the whole point of looking at a portfolio is just to check that you not a moron, but you do have the skills you claim to have.
So they just wanna do that as quickly as possible. So beyond creating your own projects, do you think there's a role for contributing to open source projects or contributing to other pieces of software that are maybe not owned by you?
Tim Ruscica: Absolutely. That's obviously a great thing to do, and it's gonna make you stand out from 99% of people, 'cause most people just won't do that.
That said, it's not easy to do that, right? And most of your contributions are gonna be super small. You're probably not gonna be, like, a lead contributor on some, you know, random open source project that's out there. So while if you can do that, I would recommend it, to be honest, I don't have that much experience working on that.
I don't even really know how I would guide you on which project to work on or how you could get involved with that. If you can figure it out, great, but I do acknowledge that's fairly challenging to just, oh, yeah, go contribute to an open source project, and probably there's some other steps you could do that might bring you a little bit further.
If you had three kickass portfolio projects that were super clear, deployed, had some real users, for example, and that was shown on your what is it? On your resume or whatever, I would imagine that would stand out a lot more than made a 40-line pull request for VS Code or something as an open source project
Richie Cotton: Absolutely, yeah.
Generally you've got to be, like, using the open source project, like the, the software for a long time before you're like, "Oh yeah, maybe I can contribute to this." Okay, so related to the idea of a portfolio is the idea- is qualifications. So what sort of qualifications do you need to become an AI engineer?
Tim Ruscica: For sure. So when it comes to qualifications, I think that these can be useful and they can show first of all you put some effort into something, that you've gone through a program, that you're, like, more committed because you've actually gone through with the process. Okay, I'm gonna probably pay for this, go spend the time doing it.
But generally speaking, companies will probably still value your ability to demonstrate those skills and prove them over the qualification. That said, for certain roles, there's very specific qualifications that companies will look for, right? If you want to go work at AWS, probably it's a good idea that you've completed some of the AWS certifications that are kind of industry-known.
You can go through. You get the idea. If you want to be an AI engineer, of course it should be related to AI engineering. You should probably have maybe a Python certificate. You should have something like LLMOps. You might have calling LLM APIs. Obviously, I know we're with DataCamp here. They've got a bunch of great certifications with their courses that I recommend all the time.
You got to look at what role you specifically want to see which ones are going to make the most amount of sense. And then for kind of some very specific AI engineering roles and other dev roles, there's a whole kind of heap of them that apply for A, C++ with Microsoft and they've got their .NET whatever line.
You've got Google Cloud certifications. You've got Azure certifications. But I wouldn't go collecting a ton of them. If you get just the ones you think are genuinely useful and that you need, stop there and then just try to build some real practical skills, because that's going to bring you further. So if you tell me you got 20 certifications, okay, probably we've gone down a little bit too far.
Two or three, that makes a bit more sense to me, right?
Richie Cotton: Yeah, it certainly seems like all the big tech companies you mentioned have their own extensive suite of certification. Then of course DataCamp has some as, as well. So thank you for the mention. But yeah I can certainly see how 20 certifications, that's not going to help you over having two or three that are targeted to the job that you want to do.
Tim Ruscica: Exactly, and it's a nice to have, but it's not ... If you don't have one, don't feel bad. It's not going to rule you out. It's just oh, okay, I see this guy's put some effort in. Oh, specifically AWS. Okay, at least that proves this point. Okay, he's got some experience with LLMs. Okay, that's nice to have, but it's maybe two or 3% of that 100% picture that's going to get you in, get you hired, get you an interview, right?
Richie Cotton: Absolutely, and I get the sense that the certifications generally work a lot better in when you're earlier in your career rather than later on.
Tim Ruscica: Yeah, 100%.
Richie Cotton: Okay. All right talk me through, what does the hiring process look like? What- once you get you put in your application, they say, "Okay come for an interview."
What is involved there? Yeah, and this is AI engineering specifically you're talking about, right?
Sure.
Tim Ruscica: Cool. So I actually ran a program, I shut it down in January, but it's called DevLaunch, where we help developers land developer positions, whether it's their first position or like a better position upgrading from where they're at.
And we had a handful of people that actually did get hired as AI engineers or they were working towards that. So I'll just walk you through practically what I saw. And keep in mind, things change constantly, and I'm not actively, interviewing, so I probably don't have all the most up-to-date info.
But here are some changes that I noticed compared to what I would see in other fields. So firstly, a lot of these companies were obviously looking for people that had strong software engineering skills with that AI layer, like I talked about. So a lot of people actually thought that they were excluded from applying to AI engineering roles 'cause they didn't have a PhD or they didn't know all the advanced math, when realistically, all these companies really wanted was a few AI-specific skills that really just built on top of strong software engineering skills.
And 80 or 90% of the skills that I would see in the requirements list were, like, Docker, Kubernetes, design systems, Python. You get the idea. Big O notation, data structures. So most people already have a lot of the skills, and they just need to add kind of that small layer that we touched on before. So assuming that you created your resume in a way where it spoke to you being an AI engineer, it's specifically tailored to that type of job posting, you had all of the keywords, and you got called in like some of our students did, what I would typically see is the first round would just be a quick recruiter chat, a fit check to make sure they're not gonna waste, an engineer's time interviewing you.
20, 30 minutes, walk me through your resume, explain this gap. "Okay, why are you interested in this position?" And I'd say 80% of people will pass those pretty easily as long as you have some decent social skills and you can explain everything that you have and you're not bullshitting what's on your resume.
From there, you typically get called in to a first-round interview. First-round interview, same thing, a little bit of a lighter round where typically they're just gonna ask you maybe some technical questions. "Hey, tell me about your experience here. Walk me through a portfolio project. Why do you want this role?
Okay, are you comfortable with this technology?" Where it's a little bit more challenging. You're gonna have to know your technical stuff. But I didn't see that many people getting asked real technical challenges or coding problems in kinda that first, let's call it real round. Then after they pass the first round, the second round is where I saw a lot more coding challenges.
Now, if we're talking Microsoft, Apple, Amazon, big tech companies, they're always giving you these LeetCode-style rounds, and you're gonna get, multiple of those. But for more of the practical companies, I would say, large enterprises, ones that aren't just big tech, they actually had very practical interviews.
So I'll give you an example of what I saw for a second round for one of my students. He was actually asked to implement a call to an LLM and wrap it into an existing API. So effectively, they had their own, I don't know, some endpoint for some LLM that they wanted to call or some internal model, and they said, "Hey, here's the endpoint.
Here's how it works. I want you to build an API around this that will cache different requests. We'll do some rate limiting. We'll make sure that we have a polling response available for getting the API callbacks." It can take one or two minutes for the response. And he was responsible for designing that API, right?
And fortunately, he did well on that, made it to the next round, and then they asked him, I think, to actually sit with another engineer and break down an existing code base and try to find a bug in some AI Again, really just like a system around some AI model that existed. So that's typically what I was seeing.
I saw some other people get again, those logic puzzle LeetCode-y type stuffs, but usually it was actually pretty practical, and it really was just core software engineering skills with some endpoint related to some ML thing, and maybe they asked you "Oh, when would you use RAG versus using fine-tuning?"
Or some, some quick questions like that. So yeah, hopefully that gives you a, a good sense, but that's typically what I'm seeing for AI engineering roles. I'm sure it changes all the time now. Answer some theory questions, write some code. You actually, in this case, they let you use AI to write the code, but they wanted to see how you used it and if you were reviewing the code and what editor and what tooling you were in.
And yeah that, that's what I noticed.
Richie Cotton: No, that's very cool. And actually it does sound like quite a fun problem. It's oh, yeah, you're building this API and figuring out all the, the system architecture, things like that. Nice. Yeah, that does seem you've got a mix of you need to understand the basic theory around AI, but also you need to be able to build stuff as well, maybe with AI assistance.
Actually, that sort of that's quite closely aligned with how a lot of data camp roles are hired for, is like you can use AI during the takeaway, but then you get grilled on whatever the result is in an interview afterwards, so you've got to be sure you understand what was generated.
Tim Ruscica: Okay.
Richie Cotton: Suppose you get the job. How is success measured? What's gonna happen in the first few months, and how do you prove that you are worthwhile as a, an AI engineer?
Tim Ruscica: Yeah. I think AI engineers typically are also coming in at more of a mid-level as opposed to a junior or an intern.
I'm sure those roles exist and there's some of them junior AI engineer whatever, but typically it's hey, you should already have three, four, five years experience. You've been a software engineer before. And I see a lot of people transitioning to that role, so let's just keep that framing when I explain the, what's expected.
Generally what I've seen is a lot of companies hiring these are also, like, fast-growing startups. They're maybe not as big, right? They're not building their own AI from scratch. The reason they're hiring this role is they want someone to be able to come in, especially if it's a smaller company, and integrate AI into their product, right?
So how is success measured? How well are you able to do that, right? Can you provide the impact? Can you come in and can you take charge, and do you have your own autonomy, and can you build some things without being handheld, right? Are you always constantly going up to, whatever your mentor or senior manager and asking for help or saying you're blocked or XYZ, that's gonna be a pretty quick way, I think, for them to be looking for someone else.
So generally what I've seen, and with one of my students who landed the role there, is it's very-- it was a lot-- very hands-off. "Hey, this is the problem we have. This is what we need you to take care of. Sure, work with other teams, ask us questions," but after the first month or two ramp up understanding the code base, it's "Hey, we're looking for you, looking to you to make a lot of these decisions."
And of course, at a bigger, in a bigger company, you're gonna have those different layers of bureaucracy, your senior engineers, your managers, where they're probably gonna do a lot of the architecture and kind of hand off to you the steps to complete. But because I know that this is a role that is popping up a lot and at smaller orgs where they might only have one, two, three, four, AI engineers, you gotta be comfortable kind of deciding what it is to actually build, making the decisions, breaking down the plan, maybe handing it off to an intern or someone junior.
And I think those are skills that a lot of engineers don't have because they're used to working underneath someone or being told exactly what to do. And in AI, when things are changing so quickly as well, you need to be up to date with the current trend. Because someone might come to you and say, "Hey, why are we using GPT-4 Nano?
I thought we're at 5.5 now." And if you weren't the one to figure that out and change that over or update the code I don't know, I don't think that looks that good. So I would say staying up to date in the current industry, right? Being able to make decisions on your own and fight for yourself and justify why you decided to do what you did, and just overall provide impact in whatever way that can be.
And again, most of the time that just ends up being, like, writing a normal software system that happens to have some AI integration that you just knew to use this integration versus another one 'cause of whatever experience you have with AI engineering, right?
Richie Cotton: Absolutely. For all the the sort of drama around, oh, AI is taking over everything, it's yeah, it's actually a software engineer role with a few little tweaks to it.
A lot of the same sort of metrics for success apply there. But also interesting how you talked about the, the differences in, like, how bosses portray the, the problems to you. If there's a le- I guess, yeah maybe at, at a junior level they tell you how to solve the problem, but at a mid to senior level it's like here's the problem, go figure it out.
And yeah that, that's a skill you need to learn.
Tim Ruscica: 100%, and like just break, having also some of that like system architecture, some of that forethought for the future as well, like not just these kind of one file solutions, like the whole system as a whole. And that's what I've noticed with a lot of these AI engineers is like really it's just doing a lot of system design that happens to revolve around some kind of LLM or ML model or whatever th- that's happening in the background.
So it's almost like just a senior role condensed into this AI one that's around this new topic. So it's still funny to me that we call it that 'cause it's really just software engineer who happens to do 10% of work with AI. That's what I see.
Richie Cotton: Absolutely. While we're on the subject, have you got any more tips for success at work in general?
Tim Ruscica: I would say, sometimes you have to play the game to some extent, right? Like you have to advocate for yourself, you have to demonstrate the work that you're doing. You have to talk to the right people, know what's going on. You can't just be in your own little bubble, sitting in the corner doing some work, whatever, pushing it out.
Like at least when I've been successful at work and when I've gotten praise or whatever, it's like, "Hey, Tim takes initiative. Hey, he asks good questions. Hey, he's organized, structured, speaks clearly," whatever, right? Like a lot of those communication skills come up, but it's also because I'm actively trying to make myself look as good as possible and not just complaining that I'm not appreciated or saying, "Oh, he doesn't know like all the stuff that I'm doing."
I think a lot of people, they don't really stick up for themselves as much as they can in a workplace environment, not in a combative way, but they just don't give themselves all the advantages that they should have in order to maybe get a promotion or get praise or get a return offer or whatever the situation may be.
Ultimately, what I say is no one's gonna look out for you as much as you need to look out for yourself, right? No one cares about you as much as you care about yourself. So you've got to do everything in your power to, not in a bad way or a boastful way, but just make sure people understand what value you bring, the contributions you're making, and also if are making decisions or You feel like you're worth more, you have a problem, like you need to bring that up proactively and set targets.
Like even now when I do kind of freelance work or other work, I'll chat with whoever's in charge, "Hey, what would, what do you need from me for this to be successful," right? "What does it look like in the first three months of where would you want me to be at? How quickly are we like expecting this to get done?"
Like setting the expectations really clearly so then you have something objective that you can always compare back to if you do ever make an ask in the future to say, "Hey, I want a raise," or, "Hey, I want a few extra days off," or, "Hey, I want this person under me," or, like you need to have something to go back to, which most people never have, and then they make the ask without any metrics and they're starting from square one,
Richie Cotton: absolutely. I think this is a, a very common problem with technical roles. Certainly I-- that resonated a lot with me earlier in my career where I was like, "Oh yeah, I'm doing the work," but somehow don't feel like people recognize it. And it's oh I didn't, the, I didn't tell people about all the cool stuff I was doing.
Yeah that does seem very important to, to play the game a, a little bit.
Tim Ruscica: It's a balance obviously. It's tricky, but just advocate for yourself, and just show people what it is that you're actually doing, and don't be shy or nervous. Which I know is easier said than done in the tech space.
But the more that you can be I don't know, understand those social dynamics in the workplace, just ultimately the better off you're gonna be in pretty much any role, but especially tech when most people suck at the social side of things. If you're even a five out of 10, you're already ahead of most engineers and use that to your advantage, right?
Richie Cotton: Oh, yeah. There's the old joke about, like, how do you tell if a software engineer's extroverted? It's like they look at your shoes when they're talking to you instead of their own. Actually, no one of my, one of my tips for playing the game, sometimes I will send a Slack message in a publicly visible channel with lots of people in it at 9:00 PM or something 'cause it looks like I'm hard at work.
Actually, I'm on the sofa just watching TV, and I've just sent it from my mobile phone. But it looks like I'm, concentrating on work things.
Tim Ruscica: That's actually a, a really good point. Sorry to cut you off, but if you can also just be quick to reply so many people take so long to reply to everything.
For me, I don't have that much of a work-life balance, but I'm always on my phone constantly. So if you ask me something, even if it's 11, 11:00 PM at night, if I see it and I can answer it really quickly, I will. I don't set the hard rule of "Oh, I'm not doing any work after 5:00 PM."
Some people might not like that, they might disagree with me, but that's a really easy way to push yourself ahead when people know 'Hey, I can get a quick answer from this guy and we can move things forward really fast," and that's helped me drastically in pretty much any role I've had.
Richie Cotton: Absolutely. Certainly if you're in an organization where it's spread across multiple time zones, which I think a lot of companies now, it's yeah, just being a- available at a broader set of hours works pretty well. All right. Do you have any final tips for how to get a job as an AI engineer?
Tim Ruscica: It's gonna be f- It's gonna sound like maybe I don't know a, a mean tip, a harsh tip, but generally speaking everything's in your control. You know what I mean? And you just have to have that mindset if you want to be successful at pretty much anything in life, and that is the exact same for getting a job.
We could sit here on this podcast and we could complain that AI's taking over and it's harder for juniors, and college sucks, and the industry's bad, and people are getting paid less, and inflation's here. There's a million things that we could go through, right? And that would be a pretty shitty podcast to listen to, and also just like It doesn't help anyone in any way.
We're just sitting here observing what's going on and complaining. But a lot of people like to put the blame on anyone other than themselves. "Oh these companies don't appreciate me," or, "Oh, they don't like my role," or, "Oh, things are changing too quickly." Ultimately, it's all your fault. You're the only one who can help yourself.
If you do wanna get a job, you need to change something in your approach, you need to take accountability for it, right? I'm telling you, if you apply to 20,000 companies, someone's gonna call you back. I'm telling you, if you build a really cool app that gets 100 users, somebody's gonna notice. If you post on LinkedIn for six months and share stuff that you're doing, that's gonna help you.
You know what I mean? There's lots of things you can do to improve your situation, and so many people that are probably a lot dumber than you have gotten tech jobs simply because they put in more work, and they didn't complain about the environment. They just put their head down and did what needed to be done.
I get it's frustrating. I get it's annoying. It's not easy. It's probably gonna take a long amount of time. But anyone who's done this for one or two years, they do get a job. They do find it, and the reason is 'cause they're actually taking accountability and trying to better themselves and change things in their life.
And the worst-case scenario is you don't get a tech job, but you find some other job or you find something else, and you've proven to yourself that you can do all of this work. It's only gonna better you. So that's just generally the mindset you have to have. You can't be a victim. You can't just complain.
Things are gonna change. Things are gonna get tough, and the only people who succeed are the ones that have that kind of self-accountability mindset And that's just how you have to do it. That, that's the answer and that's, I would say 90% of the battle is purely mental in that it's just doing the work and doing the things that need to be done, right?
Richie Cotton: Oh, man. That was tough love. But I could s- a lot of people need to hear that. And oh so your point about maybe you don't get a tech job. Actually, one of the great things about AI being everywhere is every single industry needs people who have some AI skills. So yeah the, there is more than just a few tech companies to apply to.
Tim Ruscica: There, there's lots of stuff you can do, if you told me, "Tim, you need to get a new tech job in the next 30 days, and you can't use Tech With Tim or any of your branding," I would figure it out, i'm gonna do what I, needs to be done and just go through the work and not complain about it.
And all the people I know and all the people that I've helped that I told them, "Hey, do this. It's a lot of work. It's a pain. It's gonna take you a while," every single one of them that actually did that and didn't give up got a job. Now, it took a different amount of time for each of them, and some of them got unlucky, and some of them failed interviews, and some of them had a weird situation or whatever, but they got through it.
But all the people who just said, "Oh, it's too hard," where are they right now? They're back where they were at the beginning. So that's why I just frame it like it is so mental, and I get how frustrating it is, but that's just the situation we're in. And if you wanna be in this field, which is still one of the best jobs to be in, some of the best benefits, some of the best work-life balance, some of the coolest stuff you can possibly work on, at least in my opinion it's gonna be hard, and people are gonna be competing for it, and it shouldn't be easy.
If it was easy, you wouldn't even be fulfilled if you got the job, and you probably wouldn't be going for the job because you wouldn't have all the great benefits that you get, right? That's the way I look at it.
Richie Cotton: Absolutely. Yeah. So there's a worthwhile prize. You just gotta put in the effort.
Tim Ruscica: Exactly.
Richie Cotton: Nice. All right to finish up, I always need more people to learn from, so whose work are you most excited about at the moment?
Tim Ruscica: That's interesting. Honestly, a lot of what I'm doing right now is just AI content, AI tools. I think there's a lot of interesting people on YouTube that are purely in the AI space 'cause I've at least for me, gone through a lot of my dev stuff already and I'm no longer interested in Python tutorials online.
So I like guys like Nate Hurk David Andrej Jack Roberts, I believe. These are, like, some of the up-and-coming AI... they're pretty established content creators, I would say. They do some pretty interesting stuff like AI workflows, AI coding, all kinds of integrations, and they're less, like, pure dev focused and more kind of new era vibe coding stuff, if and then in terms of just the classics one channel I always like to keep up with is called Sendax. Not sure if you've heard of him, but he's a big Python developer. He's actually was my inspiration for starting my YouTube channel like 10 plus years ago now, and he does really low-level robotics and hardware and building an LLM from scratch and building neural networks from scratch and some more hardcore coding stuff.
So if you guys like that, then I would check out that channel. And then, of course, I actually have done a few DataCamp tracks recently just to keep up to date with some of the the LLM stuff. You guys have been a massive partner on my channel can't go without sharing that. And yeah, that, that's kinda where I'm at right now.
Richie Cotton: That's cool. And I'm impressed that you've done some the DataCamp tracks. That's, Good for you. I hope you learned something useful. Nice. 100%. All right. Thank you so much for your time, Tim.
Tim Ruscica: 100%. Thanks for having me. Let's do it again.
Richie Cotton: Hi Tim, welcome to the show.
Tim Ruscica: Thanks very much for having me. Excited to chat.
Richie Cotton: Yeah, great to have you here. AI engineering is maybe the hottest role around at the moment, but it feels like it's lots of different roles smushed into one job title. So do you wanna talk me through like what are the different facets of being an AI engineer?
Tim Ruscica: Yeah, it's funny, like AI engineer can mean so many different things depending on where you're working or who you ask. So I would say that- No, okay, maybe we can break it into two or three different categories. I would say one of them is gonna be more your math heavy, more PhD level, doing, like, actual, building an LLM, right?
Or writing ML models or doing, like, all this kind of fancy technical stuff that, to be honest, probably neither of us really know how to do and most people are not doing commonly unless they went to school for this. And then you have the much more practical side where you're taking all of that work that's been done by kind of the geniuses of the world and integrating it into applications.
And I would say that's where most AI engineers are lying nowadays, where you're using an LLM, you're using a model, you're using a Hugging Face transformer, whatever, and you're building it into an app that already exists. And actually, what that means, and I'm sure we're gonna dive into that, is that a lot of the work you're doing isn't really raw AI, ML related stuff.
It's more kind of gluing the pieces together and knowing some of










Tim Ruscica is the founder of Tech With Tim, a YouTube channel and brand teaching programming and AI skills, and of Kernel, a management company for tech and coding creators. He previously worked at Microsoft and ran DevLaunch, a program that helped developers land their first or next developer role.