Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Break Into Robotics
Transcript
- Lucas: You know, Luna, I was reading the latest report from the International Federation of Robotics, and they're projecting over half a million new industrial robots will be installed this year. That's a record. Luna: Half a million just for factories. And that doesn't even count the service robots — the ones in hospitals, warehouses, even your local grocery store. Lucas: Right. And here's the thing that caught my eye: a huge chunk of that growth is software. The hardware is getting commoditized, but someone has to write the code that makes these arms pick the right box, or the autonomous cart navigate a crowded hallway. That's where bootcamp grads come in. Luna: Wait, really? I mean, I always thought robotics was for the electrical engineers and mechanical folks. Isn't there a steep learning curve? Lucas: There is a learning curve, but it's not as steep as you'd think — especially if you already know Python. Most modern robotics development happens in ROS, the Robot Operating System, which is basically a framework for talking to sensors and actuators. And it's all open source. You can install it on your laptop tonight. Luna: So it's like building web apps but for physical things. I can see the parallel. Lucas: Exactly. You're still handling events, managing data streams, dealing with concurrency. Your web dev chops — like API design, debugging, version control — they all transfer. One former bootcamp student I know was a self-taught web dev, and he got hired at a warehouse automation company because he built a pick and place simulator in Gazebo and posted it on GitHub. Luna: A simulator. That's the key. You don't need a physical robot to learn or show off your skills. Lucas: No, you don't. And that's a huge shift in the last few years. The tools have gotten so good that you can develop and test almost everything in a virtual environment. Which means a bootcamp grad can build a portfolio that's genuinely competitive with someone from a traditional engineering program. Luna: Okay, so let's get specific. If someone's listening and they're coming from, say, a full-stack bootcamp, what are the first steps? What should they actually learn? Lucas: First, get comfortable with Python beyond the basics. You need to understand object-oriented programming, data structures, maybe a bit of linear algebra — but don't panic, you don't need a math degree. Then dive into ROS. Start with the official tutorials, and try to build a simple publisher-subscriber node. That's your 'Hello, World.' Luna: And then what? How do you level up to something a company would actually care about? Lucas: Pick a real scenario. Like, an autonomous robot that has to navigate a room avoiding obstacles. Use a simulation tool like Gazebo, which pairs with ROS. You can code the logic, test it, and record a video of it working. That becomes your demo. Hiring managers love seeing a robot actually doing something, even if it's virtual. Luna: That's a solid portfolio piece. But what about the specific roles? I mean, 'robotics software engineer' — is that one job, or a bunch of different things? Lucas: Good question. It's broad. Entry-level roles often fall into a few buckets: there's the autonomy side — perception, path planning, that kind of thing. There's the application side — writing the logic that makes a robot perform a specific task, like picking items in a warehouse. And there's the systems side — integrating sensors, debugging communication, making sure everything works together. For a bootcamp grad, the application and systems sides are the most accessible. Luna: And the autonomy side is more research-heavy, I'm guessing. Lucas: Yeah, usually. But with the right projects, even that can be possible. It's all about showing you can implement algorithms, not just understand the theory. Luna: So, for someone who's thinking about this, what's the job market actually like? Are we talking a few openings or a real hiring wave? Lucas: The numbers are pretty compelling. The IFR report also said that the demand for robotics software engineers is growing at a double-digit clip. And it's not just the big automakers. You've got startups in logistics, agriculture, healthcare — they all need people who can program these robots. And they're struggling to find them. Luna: That's the classic talent gap. And when there's a gap, that's an opportunity for people who are willing to learn. Lucas: Exactly. And you know what, this feels like a good moment to mention something. If you've gotten value from the conversations we have on this show — maybe it's helped you think through a career move or just given you a new idea — and you've got a couple bucks to spare, we'd genuinely appreciate it if you threw a coffee our way. You can find the link at buy me a coffee dot com slash fexingo. It keeps this whole thing running, and it's a small way to say thanks. Luna: Yeah, it really does help us keep the episodes coming. And now back to that talent gap — you mentioned agriculture. I didn't realize that was a big robotics field. Lucas: Oh, it's huge. There are autonomous tractors, drones that monitor crops, robots that pick strawberries. The startup I mentioned earlier — the warehouse one — they have competitors doing similar things in farming. The software stack is surprisingly similar: perception, navigation, manipulation. Luna: So if you learn the fundamentals, you can switch industries pretty easily. Lucas: Exactly. And that's the beauty of robotics as a field — it's interdisciplinary, and software is at the core. You're not locked into one sector. A ROS developer can go from factory automation to medical devices without starting from scratch. Luna: Okay, so let's talk about the practical job hunt. What are the actual job titles to search for? And what should a bootcamp grad's resume highlight? Lucas: Search for things like 'robotics software engineer', 'ROS developer', 'autonomous systems engineer', or even 'simulation engineer'. And on your resume, highlight any project where you wrote code that controlled something — a simulated robot, a drone in a flight simulator, even a simple Arduino project. It's about showing that you can make hardware respond to software. Luna: And what about the interview process? Is it like a typical tech interview, with algorithms and whiteboarding? Lucas: Partly. You'll still get the standard coding questions, but there's a good chance you'll also get a systems design question. Like, 'How would you design the software for a robot that has to navigate a warehouse?' And they'll probe your understanding of topics like sensor fusion, state estimation, and how to handle errors when the robot gets stuck. Luna: That sounds more like an architecture interview. Lucas: It is, but the core concepts are learnable. You can read about simultaneous localization and mapping, or SLAM, and understand the high-level ideas without implementing a full system. As long as you can speak to the trade-offs and maybe walk through a simple example, you'll be in good shape. Luna: So, what's the typical timeline for a bootcamp grad to get job-ready? Is this a six-month detour or a year-long journey? Lucas: It depends on how much time you can devote. If you're already comfortable with Python and you can spend 10 to 15 hours a week, I'd say three to four months to get a solid understanding of ROS and build one or two portfolio projects. Then another month or two for the job search. So realistically, a six-ish-month transition is doable. Luna: That's significant, but so is the payoff. What kind of salary are we talking about? Lucas: I've seen entry-level robotics software roles starting in the 90 to 120 thousand range, depending on the cost of living. And it goes up quickly from there. The demand is high, and the supply is low, so companies are willing to pay for the right skills. Luna: That's competitive with big tech. And the work itself must be pretty satisfying — seeing something physically move because of your code. Lucas: There's nothing quite like it. You write a function, and a robot arm picks up a box. It's tangible in a way that a web page isn't. And the industry is full of people who are genuinely passionate about it, which makes the culture fun. Luna: Alright, so for our listeners who are intrigued — what's the one thing they should do this week to get started? Lucas: Install ROS on your machine — if you have a Linux machine, great; if not, you can use a virtual machine or Docker. Then follow the beginner tutorials. Don't skip the basics. And once you've done that, pick a small project, like making a simulated robot drive in a square. That's your first stepping stone. Luna: And when you get stuck — and you will get stuck — what's the best way to find help? Lucas: The robotics community is incredibly welcoming. There are active forums, Discord servers, and the ROS discourse is full of friendly experts. And don't forget YouTube — there are some fantastic tutorials that walk you through setting up your first robot. The key is to keep pushing through the initial frustration. Luna: That's a great note to end on. If you're a bootcamp grad who's ever thought robotics was out of reach, this episode should convince you otherwise. Thanks for the breakdown, Lucas. Lucas: Thanks, Luna. And to our listeners, take that first step. The robots are waiting.