WEBVTT 00:00:00.000 --> 00:00:01.560 You know, if you look at the headlines right 00:00:01.560 --> 00:00:04.500 now here in what, early 2026, it really feels 00:00:04.500 --> 00:00:06.620 like the sky is falling. You scroll through your 00:00:06.620 --> 00:00:10.220 feed and it's just this this wall of noise. Robots 00:00:10.220 --> 00:00:13.240 are replacing workers or, you know, your degree 00:00:13.240 --> 00:00:15.560 is worthless. It all just screams that automation 00:00:15.560 --> 00:00:18.800 is the end of the road. It's a it's a lot. It 00:00:18.800 --> 00:00:21.500 is loud and it's frankly terrifying for a lot 00:00:21.500 --> 00:00:23.660 of people. Yeah. But if you kind of look past 00:00:23.660 --> 00:00:27.600 all that noise, there's this this quiet group 00:00:27.600 --> 00:00:30.699 of people. who aren't panicking at all. In fact, 00:00:30.699 --> 00:00:34.740 they're securing salaries between like $80 ,000 00:00:34.740 --> 00:00:38.240 and $300 ,000 doing work that, and this is the 00:00:38.240 --> 00:00:41.240 key, didn't even exist five years ago. That is 00:00:41.240 --> 00:00:43.179 the disconnect we need to solve today. It's Sunday, 00:00:43.340 --> 00:00:46.799 February 8th, 2026. This is the deep dive. And 00:00:46.799 --> 00:00:48.359 we're going to try to look away from the panic 00:00:48.359 --> 00:00:50.560 and look directly at the machinery. We're unpacking 00:00:50.560 --> 00:00:52.880 what we're calling the AI labor stack. Right. 00:00:53.659 --> 00:00:56.460 The mission for this deep dive is pretty specific. 00:00:56.579 --> 00:00:58.479 We aren't just talking about learning to code 00:00:58.479 --> 00:01:00.820 in that traditional sense that we do have to 00:01:00.820 --> 00:01:04.400 touch on that. We are breaking down seven specific 00:01:04.400 --> 00:01:08.500 jobs that are hiring right now, today, that place 00:01:08.500 --> 00:01:12.299 humans inside the machine, not outside of it. 00:01:12.379 --> 00:01:14.989 I like that distinction. inside the machine because 00:01:14.989 --> 00:01:16.370 yeah usually it feels like we're just waiting 00:01:16.370 --> 00:01:19.689 to be crushed by it exactly so uh give us the 00:01:19.689 --> 00:01:21.989 road map how are we going to tackle this okay 00:01:21.989 --> 00:01:25.269 so we're visualizing a stack at the bottom you 00:01:25.269 --> 00:01:27.250 have the heavy technical lifting what we're calling 00:01:27.250 --> 00:01:30.450 the brain builders that we move up to the bridge 00:01:30.450 --> 00:01:32.469 builders which is where i think most of our listeners 00:01:32.469 --> 00:01:35.069 will find their footing okay we've got the guardians 00:01:35.069 --> 00:01:38.599 and the fixers and finally And this is important. 00:01:38.739 --> 00:01:41.180 We need to issue a pretty serious warning about 00:01:41.180 --> 00:01:43.760 one specific high paying role that looks great 00:01:43.760 --> 00:01:47.540 now, but it might be a trap. OK, let's unpack 00:01:47.540 --> 00:01:51.099 this. Segment A, the reality check. It feels 00:01:51.099 --> 00:01:54.260 like the the default human response to a massive 00:01:54.260 --> 00:01:58.140 tech shift like this is to just freeze. You know, 00:01:58.159 --> 00:02:00.400 you see the wave coming and you just lock up. 00:02:00.730 --> 00:02:03.329 It is the freeze response. It's biological. Yeah. 00:02:03.430 --> 00:02:05.510 When the environment changes too fast for our 00:02:05.510 --> 00:02:08.110 brains, we just stop moving. Yeah. But the source 00:02:08.110 --> 00:02:10.430 material we're looking at highlights that the 00:02:10.430 --> 00:02:14.189 top 1%, the people capitalizing on this, they 00:02:14.189 --> 00:02:16.530 aren't freezing. They're moving. They're pivoting. 00:02:16.810 --> 00:02:19.550 They're landing these remote first rolls with 00:02:19.550 --> 00:02:22.289 a salary floor that starts around $80 ,000. That's 00:02:22.289 --> 00:02:24.949 a significant floor. But I have to ask the skeptics 00:02:24.949 --> 00:02:27.490 question here. Is this just a bubble? I mean, 00:02:27.509 --> 00:02:30.389 is this window open forever? No. And the sources 00:02:30.389 --> 00:02:33.110 are very clear on this. It's open right now in 00:02:33.110 --> 00:02:36.770 2026 because the technology is still so messy. 00:02:37.050 --> 00:02:41.409 As the tech stabilizes, that window closes. So 00:02:41.409 --> 00:02:43.669 speed really matters here. Okay, let's get into 00:02:43.669 --> 00:02:45.469 the actual jobs then. We're starting at the bottom 00:02:45.469 --> 00:02:47.729 of the stack, job number one. The source calls 00:02:47.729 --> 00:02:50.750 this one building the brain, the AI engineer. 00:02:51.050 --> 00:02:53.569 This is the absolute top of the food chain. We're 00:02:53.569 --> 00:02:57.889 talking about a base salary of $175 ,000, and 00:02:57.889 --> 00:03:00.030 that's often pushing past $200 ,000 with bonuses. 00:03:00.430 --> 00:03:02.550 Okay, but let's be real for a sec. When we say 00:03:02.550 --> 00:03:05.469 AI engineer, we aren't just talking about asking 00:03:05.469 --> 00:03:08.189 ChatGPT to write you some code. What does their 00:03:08.189 --> 00:03:11.479 day actually look like? No, absolutely not. These 00:03:11.479 --> 00:03:13.539 are the architects. These are the people building 00:03:13.539 --> 00:03:17.939 the actual systems like Claude Opus 4 .6 or GPT 00:03:17.939 --> 00:03:20.919 5 .3 Codex. They're designing the recommendation 00:03:20.919 --> 00:03:24.159 engines, the data pipelines. Okay. You mentioned 00:03:24.159 --> 00:03:26.539 data pipelines. For someone who's not technical, 00:03:26.680 --> 00:03:28.819 what does that actually mean? It sounds so abstract. 00:03:29.199 --> 00:03:31.560 Think of it like modern plumbing. Yeah. But for 00:03:31.560 --> 00:03:34.500 information. Yeah. You have, say, a billion gallons 00:03:34.500 --> 00:03:37.199 of water. That's your data. And you need to get 00:03:37.199 --> 00:03:39.300 it to the right faucet at the right temperature 00:03:39.300 --> 00:03:42.560 without the pipes bursting. These engineers build 00:03:42.560 --> 00:03:45.240 those pipes using tools like Python, PyTorch, 00:03:45.240 --> 00:03:47.280 TensorFlow. And honestly, they spend most of 00:03:47.280 --> 00:03:49.560 their day just cleaning the water so the AI doesn't 00:03:49.560 --> 00:03:52.060 get sick. So it's less about talking to the robot 00:03:52.060 --> 00:03:54.479 and way more about building the factory the robot 00:03:54.479 --> 00:03:58.319 lives in. That's it. Exactly. I have to pause 00:03:58.319 --> 00:04:00.819 for a moment of wonder here. When you really 00:04:00.819 --> 00:04:03.680 stop and think about it. Imagine the sheer scale 00:04:03.680 --> 00:04:06.259 of what these engineers are building. A neural 00:04:06.259 --> 00:04:09.120 network that's handling a billion queries at 00:04:09.120 --> 00:04:11.699 once, routing all that information through layers 00:04:11.699 --> 00:04:15.979 of logic that feel almost organic. It's just 00:04:15.979 --> 00:04:18.759 staggering. It is engineering at a level we really 00:04:18.759 --> 00:04:21.720 haven't seen before. It's widely considered the 00:04:21.720 --> 00:04:24.639 hardest cognitive work happening on the planet 00:04:24.639 --> 00:04:26.660 right now. Which brings me to the practical question. 00:04:27.370 --> 00:04:30.550 For our listeners, is this realistic for someone 00:04:30.550 --> 00:04:33.149 who's starting from zero today? Can you just 00:04:33.149 --> 00:04:35.930 boot camp this in three months and jump in? Honestly, 00:04:36.029 --> 00:04:40.449 no. It requires months, usually years, of heavy 00:04:40.449 --> 00:04:42.730 study and certification. If you don't already 00:04:42.730 --> 00:04:44.490 know the difference between a gradient descent 00:04:44.490 --> 00:04:46.810 and a decision tree, this just isn't your starting 00:04:46.810 --> 00:04:48.430 point. Right. This is for the heavy lifters. 00:04:48.779 --> 00:04:50.220 That's what I figured. So if you're not already 00:04:50.220 --> 00:04:51.600 deep in the code, we need to look elsewhere. 00:04:51.740 --> 00:04:53.879 Let's move up the stack to job number two, the 00:04:53.879 --> 00:04:55.839 AI product manager. Now we're getting into the 00:04:55.839 --> 00:04:57.879 bridge builders. The source material uses this 00:04:57.879 --> 00:05:00.339 great analogy of the bridge. And to illustrate 00:05:00.339 --> 00:05:03.040 why we need these bridges, it brings up a painful 00:05:03.040 --> 00:05:06.139 memory for Apple users, the autocorrect disaster 00:05:06.139 --> 00:05:10.439 of 2023. Oh, right. I remember that vividly. 00:05:10.800 --> 00:05:12.800 Messages just getting mangled, sending embarrassing 00:05:12.800 --> 00:05:16.180 typos to your boss. It was a whole cultural moment. 00:05:16.379 --> 00:05:18.459 But here's the thing. Was that a coding failure? 00:05:18.899 --> 00:05:22.199 Did those engineers we just talked about, did 00:05:22.199 --> 00:05:24.339 they mess up? Well, the source makes a fascinating 00:05:24.339 --> 00:05:28.120 point here. Technically, no. The AI did exactly 00:05:28.120 --> 00:05:30.620 what it was mathematically trained to do. Okay. 00:05:31.019 --> 00:05:32.980 It predicted the most likely next word based 00:05:32.980 --> 00:05:35.220 on probability. It was actually a management 00:05:35.220 --> 00:05:37.699 failure. Because nobody checked if the math was 00:05:37.699 --> 00:05:39.959 socially acceptable. Exactly. And that is where 00:05:39.959 --> 00:05:42.980 the AI product manager lives. This role pays 00:05:42.980 --> 00:05:47.399 between $100 ,000 and $140 ,000. And the main 00:05:47.399 --> 00:05:49.699 requirement isn't Python. It's clear thinking. 00:05:50.540 --> 00:05:53.339 You are the person asking, is this actually what 00:05:53.339 --> 00:05:55.879 we want the AI to do before it goes out to a 00:05:55.879 --> 00:05:57.920 million people? So you're the translator. You're 00:05:57.920 --> 00:05:59.680 standing between the engineers who speak math 00:05:59.680 --> 00:06:03.120 and the users who speak while human. That's a 00:06:03.120 --> 00:06:05.259 great way to put it. You're writing product requirements, 00:06:05.519 --> 00:06:07.920 you're flagging issues. It's all about keeping 00:06:07.920 --> 00:06:10.360 these huge AI projects aligned with business 00:06:10.360 --> 00:06:13.519 goals. Your day is spent in meetings, looking 00:06:13.519 --> 00:06:16.439 at user data, and mostly saying no to engineers 00:06:16.439 --> 00:06:18.699 who want to build cool things that nobody actually 00:06:18.699 --> 00:06:21.240 needs. Okay, so if organization is your superpower, 00:06:21.480 --> 00:06:24.959 that's your role. But what if you're more persuasive? 00:06:25.899 --> 00:06:28.720 Let's talk about Job number three, the AI sales 00:06:28.720 --> 00:06:31.660 specialist. The deal closer. Or as the source 00:06:31.660 --> 00:06:34.079 puts it, the bridge that gets paid. Yeah. We're 00:06:34.079 --> 00:06:37.579 looking at $80 ,000 to $140 ,000 plus commission. 00:06:37.819 --> 00:06:39.920 This is an interesting dynamic because usually 00:06:39.920 --> 00:06:45.420 sales is just sales. Why is AI sales different? 00:06:45.600 --> 00:06:48.000 Why can't a normal software salesperson just 00:06:48.000 --> 00:06:50.720 do this? It's a pure arbitrage opportunity. You've 00:06:50.720 --> 00:06:53.500 got law firms, banks, all these massive legacy 00:06:53.500 --> 00:06:56.120 companies. They're desperate for AI because they 00:06:56.120 --> 00:06:57.860 know they're falling behind. Right. But they 00:06:57.860 --> 00:07:00.279 have no idea what to buy. They're totally paralyzed 00:07:00.279 --> 00:07:02.639 by choice. They just know they need the AI. Exactly. 00:07:03.079 --> 00:07:05.560 Now, the engineers we just talked about, they 00:07:05.560 --> 00:07:07.860 usually can't sell. They get lost in the weeds 00:07:07.860 --> 00:07:09.639 explaining neural architecture and all that and 00:07:09.639 --> 00:07:12.720 traditional sales reps. They don't understand 00:07:12.720 --> 00:07:15.339 the tech well enough to explain how it actually 00:07:15.339 --> 00:07:18.420 helps a lawyer draft a contract faster. So there's 00:07:18.420 --> 00:07:21.560 a gap, a competence gap. A huge gap. If you can 00:07:21.560 --> 00:07:23.939 speak plain English and you understand the tech, 00:07:24.079 --> 00:07:28.779 you win. If you can explain AI to a law firm 00:07:28.779 --> 00:07:31.459 partner in a way that connects to their actual 00:07:31.459 --> 00:07:34.279 billable hours, you are incredibly valuable. 00:07:34.500 --> 00:07:36.720 You're not selling software. You're selling a 00:07:36.720 --> 00:07:39.259 solution to their panic. But sales is a grind, 00:07:39.379 --> 00:07:41.660 isn't it? Is this a low -stress role? Definitely 00:07:41.660 --> 00:07:44.379 not. No. You live by your numbers. But because 00:07:44.379 --> 00:07:46.839 the demand is so high right now, the upside is 00:07:46.839 --> 00:07:48.720 just massive. You are the one bringing the money 00:07:48.720 --> 00:07:51.959 in the door. High risk, high reward. Let's shift 00:07:51.959 --> 00:07:55.069 gears to something a bit more structural. Job 00:07:55.069 --> 00:07:57.970 number four, the AI chatbot designer. The conversation 00:07:57.970 --> 00:08:00.350 architect. I love that title, but I want to be 00:08:00.350 --> 00:08:02.589 clear. We aren't talking about picking the colors 00:08:02.589 --> 00:08:04.410 for the chat window, right? This isn't visual 00:08:04.410 --> 00:08:06.990 design. Not at all. This is logic design. The 00:08:06.990 --> 00:08:09.470 source brings up that Air Canada case from a 00:08:09.470 --> 00:08:11.350 few years back. Do you remember this? Oh, the 00:08:11.350 --> 00:08:14.310 chatbot that went rogue. Yes. Air Canada lost 00:08:14.310 --> 00:08:18.110 a court case because their chatbot literally 00:08:18.110 --> 00:08:21.509 invented a refund policy that didn't exist. It 00:08:21.509 --> 00:08:24.230 just made it up. It just promised a guy a refund. 00:08:24.800 --> 00:08:27.240 And the court said, well, your bot said it, so 00:08:27.240 --> 00:08:30.240 you have to pay it. It hallucinated. Wow. And 00:08:30.240 --> 00:08:32.460 that happened because the conversation paths 00:08:32.460 --> 00:08:35.870 weren't fenced in properly. That is what a chatbot 00:08:35.870 --> 00:08:38.769 designer does. You design the logic trees. You 00:08:38.769 --> 00:08:41.210 map out the conversations. You have to anticipate, 00:08:41.429 --> 00:08:44.409 OK, if a user asks for a refund, the bot must 00:08:44.409 --> 00:08:46.730 check the database first. It cannot just say 00:08:46.730 --> 00:08:48.669 yes. So it's almost like you're writing one of 00:08:48.669 --> 00:08:50.690 those choose -your -own -adventure books, but 00:08:50.690 --> 00:08:52.909 you're strictly enforcing the rules so the reader 00:08:52.909 --> 00:08:55.490 doesn't, you know, fall off a cliff. Precisely. 00:08:55.490 --> 00:08:58.149 The source mentions a salary of $80 ,000 to $115 00:08:58.149 --> 00:09:01.610 ,000, and it specifically points to IBM's course. 00:09:02.190 --> 00:09:04.750 Building AI chatbots without programming. So 00:09:04.750 --> 00:09:06.909 if you're the kind of person who spots a plot 00:09:06.909 --> 00:09:08.970 hole in a movie and it just ruins the whole thing 00:09:08.970 --> 00:09:12.049 for you, this is your job. Logic over lyrics? 00:09:12.269 --> 00:09:15.029 Yes. Exactly. You spend your day breaking down 00:09:15.029 --> 00:09:18.490 human conversation into flowcharts. Got it. Okay, 00:09:18.570 --> 00:09:21.190 joke number five. The AI support specialist. 00:09:21.669 --> 00:09:25.009 The fixer. Or the human in the loop. We all know 00:09:25.009 --> 00:09:27.789 customer support has changed. It's mostly AI 00:09:27.789 --> 00:09:30.870 now. But what happens when the AI breaks? That's 00:09:30.870 --> 00:09:33.299 where this role comes in. When the AI gets confused 00:09:33.299 --> 00:09:35.580 or it hits some edge case it hasn't seen before, 00:09:35.759 --> 00:09:39.100 it flags a human. So walk me through that. Is 00:09:39.100 --> 00:09:41.840 this just a call center job with a fancy title? 00:09:42.159 --> 00:09:44.460 Because support specialist usually implies a 00:09:44.460 --> 00:09:47.580 headset and, well, misery. No. And here's the 00:09:47.580 --> 00:09:49.720 key distinction. In a call center, you answer 00:09:49.720 --> 00:09:52.179 the question and you hang up. In this role, you 00:09:52.179 --> 00:09:55.139 review the flag. You correct the mistake and 00:09:55.139 --> 00:09:57.720 then, and this is the important part, you feed 00:09:57.720 --> 00:09:59.539 that correction back into the system. You're 00:09:59.539 --> 00:10:02.299 teaching it. You are training the AI not to make 00:10:02.299 --> 00:10:04.659 that specific mistake again. You aren't just 00:10:04.659 --> 00:10:06.720 solving one customer's problem. You're building 00:10:06.720 --> 00:10:08.840 the system's resilience. The salary is a bit 00:10:08.840 --> 00:10:11.240 lower, maybe $50 ,000 to $80 ,000, but it is 00:10:11.240 --> 00:10:13.559 very remote friendly. So you're essentially an 00:10:13.559 --> 00:10:16.759 on -the -job trainer for the algorithm. That's 00:10:16.759 --> 00:10:19.000 it. You need patience and you have to be good 00:10:19.000 --> 00:10:20.899 at troubleshooting. That's a crucial distinction. 00:10:21.639 --> 00:10:24.960 You're optimizing the machine. Now, joke number 00:10:24.960 --> 00:10:26.940 six, and I want to shift the tone a little here 00:10:26.940 --> 00:10:30.460 because this one is, it's heavy. The AI content 00:10:30.460 --> 00:10:33.580 moderator, the guardian. Yeah. This is the last 00:10:33.580 --> 00:10:36.200 line of defense. The pay is lower, around $40 00:10:36.200 --> 00:10:38.559 ,000 to $50 ,000. Yeah. But the responsibility 00:10:38.559 --> 00:10:41.399 is massive. You are reviewing the outputs that 00:10:41.399 --> 00:10:44.580 are flagged as dangerous, misleading, or just 00:10:44.580 --> 00:10:46.700 inappropriate. And we have to be really honest 00:10:46.700 --> 00:10:49.320 about what that means. The source issues a strong 00:10:49.320 --> 00:10:51.840 mental health warning here. You aren't just checking 00:10:51.840 --> 00:10:54.440 for typos. You are seeing the worst of the Internet. 00:10:54.820 --> 00:10:58.080 Hate speech, violence, all the toxicity. You're 00:10:58.080 --> 00:10:59.879 the one filtering out the sludge so the rest 00:10:59.879 --> 00:11:01.740 of us don't have to see it. It's the janitorial 00:11:01.740 --> 00:11:05.299 work of the digital age. But for toxic content, 00:11:05.600 --> 00:11:07.919 it just sounds incredibly draining. It is. It's 00:11:07.919 --> 00:11:10.539 heavy. It's stable. It's necessary work. But 00:11:10.539 --> 00:11:13.759 the burnout risk is very, very high. It takes 00:11:13.759 --> 00:11:16.120 a specific kind of resilience. It begs the question, 00:11:16.179 --> 00:11:18.590 though, that I think. we have these super advanced 00:11:18.590 --> 00:11:21.809 models why can't ai just moderate itself yet 00:11:21.809 --> 00:11:26.230 because ai still struggles with nuance it doesn't 00:11:26.230 --> 00:11:29.529 get context or sarcasm or safety in the way a 00:11:29.529 --> 00:11:31.809 human does it needs a conscience it is a conscience 00:11:31.809 --> 00:11:33.809 and for now that conscience is a human being 00:11:33.809 --> 00:11:36.610 that's a sobering thought okay let's move to 00:11:36.610 --> 00:11:39.230 the final specific job on the list job number 00:11:39.230 --> 00:11:41.610 seven the one everyone talks about the prompt 00:11:41.610 --> 00:11:45.129 engineer the ai whisperer this one comes with 00:11:45.129 --> 00:11:49.450 a high price tag We're talking $135 ,000. But 00:11:49.450 --> 00:11:51.490 there's a catch. There is a catch. Yeah. But 00:11:51.490 --> 00:11:53.950 first, let's define why it pays that much. You 00:11:53.950 --> 00:11:56.309 know, I have to make a bit of a vulnerable admission 00:11:56.309 --> 00:11:59.309 here. I still wrestle with prompt drift myself. 00:11:59.610 --> 00:12:01.690 Oh, yeah. I'll get a system working perfectly, 00:12:01.789 --> 00:12:04.230 generating a report exactly how I like it. And 00:12:04.230 --> 00:12:06.470 then maybe two weeks later, I use the exact same 00:12:06.470 --> 00:12:09.970 prompt and the AI just. It goes off the rails. 00:12:10.049 --> 00:12:11.750 It gives me something totally different. That 00:12:11.750 --> 00:12:14.669 is drift. And for a casual user like you, it's 00:12:14.669 --> 00:12:17.269 annoying. For a law firm or a medical group, 00:12:17.389 --> 00:12:20.409 it's a complete disaster. Right. They need consistent, 00:12:20.490 --> 00:12:23.830 reliable outputs every single time. They can't 00:12:23.830 --> 00:12:25.529 have a contract clause just changing because 00:12:25.529 --> 00:12:28.110 the AI felt creative that day. So the prompt 00:12:28.110 --> 00:12:30.419 engineer is the one who locks that down. You 00:12:30.419 --> 00:12:33.299 design the inputs to lock down the outputs. You're 00:12:33.299 --> 00:12:35.220 the one struggling with that drift so that the 00:12:35.220 --> 00:12:37.759 lawyers don't have to. You're creating the templates 00:12:37.759 --> 00:12:39.419 that the rest of the company is going to use. 00:12:39.580 --> 00:12:41.860 But the source material warns us pretty clearly. 00:12:42.139 --> 00:12:45.820 This might not be a 20 -year career. No. As the 00:12:45.820 --> 00:12:48.480 models get smarter, they just need less whispering. 00:12:49.019 --> 00:12:52.039 They understand intent better. So this role, 00:12:52.200 --> 00:12:55.360 it's a right now opportunity. It's a gold rush. 00:12:55.690 --> 00:12:58.110 So don't plan your retirement around this particular 00:12:58.110 --> 00:13:00.809 job title. Exactly. Take the money while the 00:13:00.809 --> 00:13:03.529 gap exists, but you have to be ready to evolve. 00:13:03.870 --> 00:13:07.169 The source is very clear. This skill will eventually 00:13:07.169 --> 00:13:10.129 just be part of everyone's job, not a job title 00:13:10.129 --> 00:13:12.610 on its own. Clear enough. Grab it while you can. 00:13:13.090 --> 00:13:16.009 Now, before we wrap up the list, the source mentions 00:13:16.009 --> 00:13:19.470 a bonus category, the non -jobs. Right. This 00:13:19.470 --> 00:13:21.049 is for the people who are listening to this whole 00:13:21.049 --> 00:13:23.070 list and thinking, yeah, but I don't want a boss. 00:13:23.549 --> 00:13:25.450 This is the leverage play. So we're talking about 00:13:25.450 --> 00:13:28.610 things like being an AI automation builder, going 00:13:28.610 --> 00:13:30.669 into a small business and cleaning up their messy 00:13:30.669 --> 00:13:34.629 systems. Or building a micro SaaS. You know, 00:13:34.629 --> 00:13:37.909 solving one tiny painful problem with a dedicated 00:13:37.909 --> 00:13:41.850 AI tool. Or being an AI asset builder, selling 00:13:41.850 --> 00:13:44.590 your prompts and templates online. The core concept 00:13:44.590 --> 00:13:47.789 here is income bending upward. What does that 00:13:47.789 --> 00:13:50.070 mean in practice? Right. So in a normal job. 00:13:50.509 --> 00:13:52.450 Even the high paying ones we just listed. Yeah. 00:13:52.529 --> 00:13:54.610 You work an hour. You get paid for an hour. Sure. 00:13:54.690 --> 00:13:57.889 In these roles, you are building leverage. One 00:13:57.889 --> 00:13:59.990 person can now do the work of a 10 person team. 00:14:00.230 --> 00:14:02.570 You build the system once and it keeps paying 00:14:02.570 --> 00:14:05.389 you over and over. And that is a completely different 00:14:05.389 --> 00:14:07.289 game than just trading your time for money. You're 00:14:07.289 --> 00:14:09.730 building an asset, not just filling a seat. Exactly. 00:14:10.009 --> 00:14:11.669 OK, let's bring this all back together. We've 00:14:11.669 --> 00:14:13.490 covered a lot of ground here. We've got the brain 00:14:13.490 --> 00:14:15.330 builders, the bridge builders, the guardians. 00:14:15.669 --> 00:14:18.850 Well, if we synthesize this labor stack, it really 00:14:18.850 --> 00:14:21.379 looks like an ecosystem. The engineers build 00:14:21.379 --> 00:14:23.519 the brain. The product managers make sure the 00:14:23.519 --> 00:14:25.639 brain is thinking clearly. The salespeople convince 00:14:25.639 --> 00:14:29.320 the world to use it. And then the designers support 00:14:29.320 --> 00:14:32.600 and moderators, they train it and they fix it 00:14:32.600 --> 00:14:35.200 when it breaks. And the core takeaway here feels 00:14:35.200 --> 00:14:37.879 pretty simple. Stop trying to compete against 00:14:37.879 --> 00:14:41.240 AI. Right. Don't try to be faster than the robot. 00:14:41.500 --> 00:14:44.080 You will lose. You have to position yourself 00:14:44.080 --> 00:14:47.019 inside the system that makes the AI work. That's 00:14:47.019 --> 00:14:49.600 the entire shift from competitor to operator. 00:14:50.240 --> 00:14:52.220 So for the listener sitting here, maybe feeling 00:14:52.220 --> 00:14:54.340 a little less frozen than they were 20 minutes 00:14:54.340 --> 00:14:57.600 ago, what's the next move? Pick a lane that actually 00:14:57.600 --> 00:14:59.679 fits your personality. Don't try to force it. 00:14:59.740 --> 00:15:01.899 If you're an extrovert who loves people, go for 00:15:01.899 --> 00:15:05.019 sales. If you're super logical but you hate code, 00:15:05.679 --> 00:15:08.659 chatbot designer. If you want to see the big 00:15:08.659 --> 00:15:11.600 picture, product manager. And what about credentials? 00:15:11.759 --> 00:15:13.700 Are we talking about going back for a four -year 00:15:13.700 --> 00:15:15.659 degree here? No, and that's the beauty of it 00:15:15.659 --> 00:15:19.720 right now. Coursera, Google, IBM. The credentials 00:15:19.720 --> 00:15:22.460 exist and they are accessible. Employers are 00:15:22.460 --> 00:15:25.039 looking for proving competence, not just a fancy 00:15:25.039 --> 00:15:27.419 pedigree. The final thought from our source material 00:15:27.419 --> 00:15:29.779 is one that really sticks with me. The best time 00:15:29.779 --> 00:15:32.360 to start was yesterday, but the window is closing. 00:15:32.580 --> 00:15:35.000 It won't stay open forever. The labor market 00:15:35.000 --> 00:15:37.460 will adjust. Supply will eventually meet demand. 00:15:37.700 --> 00:15:39.960 So don't wait. Thank you for diving in with us 00:15:39.960 --> 00:15:42.000 today. Always a pleasure. See you in the deep 00:15:42.000 --> 00:15:42.259 end.