Free YouTube Transcribe

Video transcript

Is Software Engineering Dying in 2026? (What the Data Actually Says)

Tech With Tim · 2,509 words · 12 min read

Want to search this transcript, jump the video from any line, or download it as TXT, SRT, or VTT?

Open in the transcript tool

Full transcript

| The Data

0:00Junior developer job postings are down somewhere between

0:0360 and 70% since 2022.

0:06And at the same time, the Bureau of Labor Statistics is still projecting

0:11for software developers over the next decade.

0:14That's about five times the average across all industries.

0:17So which is it?

0:18Is software engineering dying or is it growing?

0:21Now both the numbers are true at the same time.

0:23And if you understand why,

0:25you'll know exactly what to focus on and what to stop wasting your time on.

0:29If software engineering isn't dying, but it is changing faster than at any

0:33point in my career,

0:34and the people getting hurt right now are mostly making the same mistake.

0:38They're optimizing

0:39for the version of this job that existed three years ago, not today.

0:42So let me break down what's actually happening.

0:45And then the four things that matter the most right now,

0:48if you want to become a software engineer, let's dive in.

0:51Okay. So what's actually happening?

0:53Well, first I want to give you the owner's picture.

0:55And I don't want to sugarcoat it here.

0:56Around 77% of professional developers now say they use AI coding tools.

1:02And these tools are genuinely good at a specific category of work.

1:06Now that's boilerplate.

1:07Simple Crud endpoints, basic bug fixing test,

1:10scaffolding, routine, front end work.

1:12You get the idea.

1:13Now, that category is exactly what junior developers used to get hired to do.

1:18It was the bottom rung of the ladder, and AI kind of just soared all of that off.

1:22Now, Stanford researchers found that employment for developers aged

1:2522 to 25 dropped nearly 20% between 2022 and mid 2025.

1:31And once we have the data for 2026, I expect that's going to be even higher

1:35now over the same period, employment for workers over 30 in

1:39AI heavy roles actually grew, so the jobs didn't disappear.

1:43They simply moved, and they actually moved up the stack away

1:47from writing routine code and towards things that AI can't do.

1:50So effectively.

1:51All of these junior jobs moved over to more

1:53AI related roles that are more for mid and senior level employees.

1:57Now, even the companies that are betting on junior

1:59developers are proving this point.

2:01IBM announced that they're tripling entry level hiring, and their reasoning is that

2:05the junior role is shifting away

2:07from routine coding towards judgment and customer facing work.

2:10So everyone on both sides of the debate here agrees on the same underlying fact.

2:15The fact is that this job is being redefined.

2:18So let's talk about what it's being redefined into.

2:21Because once you understand that, you can know how to navigate this market.

| Systems not Code

2:24So the first thing that actually matters

2:26here is owning systems instead of just writing lines of code.

2:30AI has made writing code cheap.

2:33Now this is a big deal

2:34because in the past, most of what you did as a developer was actually write code.

2:38You had to mononymously sit there writing

2:40thousands of lines of code, and your typing speed genuinely mattered.

2:44How productive you were in IDE was actually a selling point,

2:47and most junior developers spent most of their day writing boilerplate test

2:51scripts and actually just entering values into the computer.

2:54Now, at this point, that's no longer a skill that you're being hired for.

2:58However, you are still being hired for understanding a system.

3:01So knowing why the architecture is shaped the way it is.

3:04What breaks when you change something,

3:06How the pieces are talking together and what the data flow looks like.

3:10Now that knowledge is what companies are really paying for, especially now.

3:14So double down on things like system design, taking a vague requirement and

3:18turning it into components, trade offs and making decisions that you can defend.

3:23You also want to double down

3:24on debugging real systems, because when production goes down, an

3:29but a human is the one

3:30who has to diagnose this and ultimately come up with the decision.

3:33And then of course on reading code.

3:34Because honestly, right now, reading code is actually more important

3:37than writing it, especially when AI is generating so much

3:41that the bottleneck is actually how quickly you can review.

3:44So if you're c, you understand pull requests.

3:47You know how to quickly get through a code base, navigate different commits,

3:50go through various files.

3:51That is going to level you up now.

3:53Today, a senior engineer with these skills plus AI tools

3:57is shipping at multiples of what was possible just a few years ago.

4:00And that's why their employment is growing while routine coding work is shrinking.

4:05So the leverage has really moved to the people who understand the systems.

4:08And I don't want to use the same word, but understand their leverage,

4:11how they can get the most amount done with the fewest resources.

| Using AI Tools Professionally

4:15Now let's talk about the second thing that matters a lot now that is using

4:19AI tools like a professional.

4:21Now there's a right way of doing this

4:22and there's absolutely a wrong way of doing this.

4:25Now the wrong version of this is vibe coding your entire job.

4:28So you accept whatever the model spits out and then you just ship it.

4:31Now that's how you end up with code bases that nobody understands.

4:34And that's what companies are already getting burned by.

4:37A bunch of junior developers

4:38coming in with vibe coding knowledge is not going to last very long.

4:42Now, the professional version of this is treating AI like a very fast

4:46junior developer.

4:47It's something that you can supervise,

4:48that can get a lot done, but that you can't implicitly trust.

4:51So you use copilot, cursor cloud code, whatever fits your stack to move quickly.

4:55But you review everything, you test everything,

4:58and you never merge code that you could not explain.

5:01Now, this is actually something employers are screening for explicitly.

5:04Now they want people who are fast with AI,

5:06but also skeptical of what it's producing.

5:08And to be clear here, being good with AI doesn't make you special in 2026,

5:13but being bad with it absolutely will filter you out.

5:16So it's no longer oh, I know how to use AI tools, so hire me.

5:19It's like you better know how to use AI tools.

5:21You're not even going to make it to the second interview.

| Agentic AI Layer

5:23Now, the third thing I want to discuss, and honestly,

5:25one of the biggest opportunities on this list is learning to build with AI,

5:29not just alongside it.

5:30Now, using cursor to write code faster is AI helping you build software?

5:35But what I'm talking about now is software,

5:37where AI is part of the features.

5:39So apps that call language models through APIs, systems that answer

5:43questions over companies, documents, agents that automate multi-step workflows.

5:47Basically, every company right now is trying to ship AI related features,

5:51and the number of engineers who can do this

5:53well is still really, really small because it's relatively new.

5:56Now, that gap is why AI engineering roles in the United States

5:59are averaging somewhere between 100 and 70 5 to $200,000 per year,

6:04and why this has been one of the fastest growing skills in today's market.

6:08And this is not a career restart here, right?

6:10If you can already code, this AI layer is a set of learnable

6:13skills that sits on top of all of the skills you already have.

6:16So things like calling model APIs properly, prompt engineering,

6:20structured outputs, Rag vector databases, right?

6:24Actually designing systems and having agent orchestration

6:27evaluations, observability so you can tell what's actually going on.

6:31None of these things require a PhD or a heavy math or genius level IQ.

6:35This is engineering.

6:36It's easy to learn relatively if you have the right path.

6:39And these are the skills that people are getting hired,

6:41literally hundreds of thousands of dollars per year. For now.

| How to Learn This

6:44The obvious question at this point is how do you actually learn that layer,

6:47especially if that's one of the biggest opportunities,

6:49because watching videos about it, even including

6:51this one, is not going to get you there.

6:53No studies show that

6:54when you passively watch tutorials, you only retain about 20% of the material.

6:58But when you learn actively by actually writing code and building

7:02things like projects, your retention jumps to 75 to 90%.

7:06Now for a shift this important for your career.

7:08That difference is literally everything.

7:10Now that's why I partnered with Data Camp for this video.

7:13Now, I've used their platform for years to sharpen my own Python, an AI skills way

7:17before they ever sponsored any videos. So this is something

7:20I can actually recommend from my own legitimate experience.

7:23Now there are so cute!

7:24AI engineer for developers track is built for exactly what we just talked about.

7:28Someone who can already code and wants to add the AI layer fast.

7:32Now it's 29 hours of hands on learning where you build real applications

7:36like chatbots, semantic search, recommendation systems using things

7:40like OpenAI API, Lang chain hugging face, pinecone vector databases.

7:44You get the idea.

7:45Now it covers the production side as well.

7:47They have things like LM ops, which most people actually end up skipping.

7:51That goes over rate limiting

7:52API errors, structured model outputs so you can build reliable systems.

7:56And this track was actually just refreshed in July of 2026.

7:59So the content is current which really matters in this space.

8:02Now once you finish

8:03that there's an AI engineer for developers associate certification.

8:07And it's not just multiple choice.

8:09There's a four hour practical exam where you build a real working AI application.

8:13So it certifies that you can do the job and not just talk about it.

8:17Now, the first chapter of every course is free.

8:19So you can start course one today and by link in the description

8:21will give you 25% off when you decide to upgrade.

8:24Now, if everything in this video is telling you

8:26the is moving, this is the most direct way that I know to actually move with it.

8:31Okay, so let's move on to the fourth thing that matters, which is proof, right?

| Proof You Can Ship

8:35In a market that's this

8:36competitive claims are worthless and evidence is literally everything.

8:40The strongest evidence is a shipped project.

8:43So either 1 or 2 projects that solve a real problem, end to end,

8:47that are deployed live with a link that someone can actually click.

8:51Now ideally this is with an AI component to connect that

8:53AI layer that we talked about, because that's

8:55what a lot of these hiring managers are scanning for and actively hiring for.

8:59The most important part here is that you build something practical

9:02that real people actually use that's deployed.

9:05If you do that, even having one project is going to be

9:08ten half assed projects that don't solve a legitimate problem.

9:11Now, if you're not looking for a job and you're already employed, the highest

9:15leverage move that you can possibly make is to become the AI person on your team.

9:19So volunteer for the AI feature that nobody else wants to own.

9:22Ship one real thing with a model that's actually inside of your current job,

9:26and have something on your resume so that you can prove

9:29you know what you're doing now.

9:30An internal move into AI work is almost always easier than landing it

9:34cold for mode side, and you get paid while you do it with pretty much zero risk

9:38and it gives you the evidence.

9:39Then go land something better at another company.

9:42I've said this many times before, but it's always easier to shift

9:45internally and then once you have the evidence, move to something better.

| What to Ignore

9:48Okay, so those are what you should worry about, but what should you skip?

9:51So first thing, stop grinding LeetCode as your entire interview strategy.

9:56Now interview prep matters.

9:57You should do a bit of leetcode, but algorithms alone are the old game, right?

10:01Yes, companies are still testing them, but they're increasingly testing

10:05practical building and your judgment instead.

10:07So stop chasing every new framework, because the framework stuff

10:11is going to change constantly and really focus more on the fundamentals.

10:14So system design, data, APIs, testing.

10:17Right.

10:18These things have never mattered more and they're not going away.

10:21Now also you want to stop doom scrolling.

10:23All of the coding is dead headlines.

10:25Now look, I'm a YouTuber. I'm guilty of doing it as well.

10:28But generally speaking, this is not something you can control

10:31unless you're going to completely change industries.

10:33You're kind of stuck going into software engineering, so all you can do is play

10:37the game to the best of your ability.

10:39Focus on what's actually changing in the industry right now, and adapt

10:43just like everyone else has for the past 30 years to land a job.

10:46I know software engineers now

10:48that have never been paid more than they have before,

10:50and that's simply because they saw this coming.

10:52They adapted and they focused on it early.

10:54One thing I can tell you 100% is that nobody cares.

10:57Nobody feels sorry for you.

10:58If you want to complain and moan and just worry about the industry,

11:02you can do that, but you're going to get left behind

11:04with all of the people who don't do that

11:05and just take the steps to actually better themselves.

11:08Software engineering is still a fantastic job.

11:10There are so many great benefits.

11:12It is one of the best jobs, in my opinion, in the world,

11:14even if we compare it to pretty much everything else.

11:17And while it has gotten more difficult to get a job, you still absolutely can.

11:21And the only way you're going to do that is by taking accountability in action.

11:24Again, it's kind of some tough love, but that's all I can say.

11:26And the people that have done that, pretty much everyone

11:29I know has been able to find something.

11:30It just took maybe a little bit longer than it did in the past.

11:33So yes, software engineering is changing.

11:35It's been changing drastically and especially now.

11:38But you know what?

11:39It's changing into system design, ownership using AI tools,

11:43the engineering layer building prove all of these things have been changing

11:47for the past 3 or 4 years, and if you've looked into them,

11:50you've been able to get into a better role where you're probably making more money

11:53than you ever had before.

11:54So I hope this video isn't dissuading you.

11:56All I'm trying to say

11:57is that there are certain things to focus on, certain things to not focus on.

12:00If you follow the guidance here, I hope that

12:02that's going to help get you back on track.

12:04Let me know what you think of the industry and all of the changes

12:06in the comments down below, and I will see you in the next one.

More from Tech With Tim

Recently added transcripts

Browse the whole transcript library

This transcript was generated from the captions YouTube publishes for this video. Get the transcript of any YouTube video atfreeyoutubetranscribe.com, free, unlimited, no sign-up.