Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Break Into DevOps
Transcript
- Lucas: Let's talk about the role that keeps the lights on when nobody is actually writing new features. It's DevOps. Or more accurately, the modern hybrid of site reliability engineering and platform operations. Luna: Right. And it is arguably the most misunderstood job title in tech right now because people think it means you need to be a senior developer who also knows how to fix servers. Lucas: Exactly. The barrier to entry feels incredibly high on paper. You see job postings asking for five years of experience with Kubernetes, Terraform, and Python automation, yet the actual day-to-day work for an entry-level person is often just keeping the deployment pipeline from breaking. Luna: So where do bootcamp grads fit into that hierarchy if they haven't spent four years studying computer science? Lucas: They fit in at the bottom, specifically in junior system administration or junior release engineering roles. I looked at a recent case study from a mid-sized fintech firm that hired three bootcamp graduates directly into their infrastructure team last quarter. Luna: Wait, without prior professional IT experience? That sounds risky for a company handling financial data. Lucas: It is risky, but they structured the onboarding around a single concrete skill: Linux proficiency. They didn't care that the candidates couldn't write complex algorithms. They cared that those candidates could navigate the terminal, manage file permissions, and understand process management. Luna: That is interesting because most coding bootcamps treat Linux as a footnote after the first week of setup. Lucas: Precisely. The gap is huge. If you want to break into this field, you have to self-teach the operating system layer. The hiring manager I spoke with said he rejects any candidate who still uses the graphical interface to find their files. He wants them comfortable with the command line. Luna: Okay, so let's get practical. What are the non-negotiable technical skills for someone looking to pivot into DevOps today? Lucas: Three things. First, basic networking knowledge. You need to understand what an IP address is, what DNS does, and why ports exist. Second, version control beyond just git commit. You need to understand branching strategies and merge conflicts in a CI environment. Luna: And the third? Lucas: Scripting. Not building apps, but writing small bash or Python scripts to automate repetitive tasks. If you can write a script that backs up a database folder automatically, you are already ahead of eighty percent of applicants. Luna: I have to ask about the cloud certifications. Everyone tells me to get the AWS Solutions Architect cert immediately. Lucas: Ignore that noise for entry-level. The Amazon Web Services certificate is valuable, but it proves you can pass a multiple-choice test, not that you can troubleshoot a server. Hands-on labs matter more than the paper credential at this stage. Luna: So focus on building a home lab instead? Like spinning up a virtual machine and breaking it on purpose? Lucas: Yes. Set up a cheap VPS instance. Install a web server. Configure the firewall. Then intentionally try to hack your own machine using public tutorials. Understanding how security works by failing at it is better than memorizing theory. Luna: That sounds intense. Does the culture shock hit hard when you move from a coding-focused bootcamp to an ops-focused role? Lucas: The biggest shift is mindset. Developers build things to delight users. Ops engineers build things to prevent disasters. You have to become comfortable with being the person who says no to a deployment because it isn't stable enough. Luna: That makes sense. You're the gatekeeper. But don't developers resent that gatekeeping? Lucas: Not if you communicate clearly. The best DevOps engineers I know are actually very empathetic. They realize that friction slows down the whole company. Their goal is to make the developer's life easier, not harder. Luna: Speaking of making lives easier, I want to take a quick second to mention something important about how we keep this conversation going. Lucas: We rely on listeners who value deep dives like this one. A couple of dollars a month is genuinely what keeps these episodes ad-free and allows us to research these specific career paths properly. Luna: If you've found even one tip useful today, consider supporting us directly at buy me a coffee dot com slash fexingo. Lucas: It really helps us stay independent and focus on the details rather than chasing clicks. Thanks for keeping the network running. Luna: Back to the pipeline. How do you actually prove you have these skills during an interview? Lucas: You build a portfolio project that mirrors reality. Do not put a todo list app on GitHub. Build a simple website, then set up automated testing for it, containerize it with Docker, and push it to a cloud server automatically whenever you update the code. Luna: So the code itself doesn't matter as much as the workflow surrounding it? Lucas: Correct. The interviewer wants to see that you understand Continuous Integration and Continuous Deployment. They want to see that you can debug a failed build log. Luna: That is a very specific kind of debugging. Reading error logs from a deployment tool is totally different from reading syntax errors in Python. Lucas: It requires patience. You have to learn to read stack traces backwards. Start at the bottom where the error happened and work your way up to the trigger point. Luna: What about salary expectations? Is there a penalty for starting in ops instead of pure software development? Lucas: Actually, the opposite is often true. Entry-level DevOps roles tend to pay slightly higher because the talent pool is smaller. Companies are desperate for people who can bridge the gap between code and infrastructure. Luna: So it is a strategic advantage to go deeper into the stack rather than wider across the application layer? Lucas: For sure. You become indispensable. Once you know how the server runs the code, you have leverage that pure frontend developers usually don't have until they specialize later in their careers. Luna: Do you recommend learning Kubernetes early on, or should that wait until you have some operational experience? Lucas: Wait. Kubernetes is complex. Try to understand containers first. Learn how Docker works, how images are built, and how networks interact between containers. If you jump straight into orchestration, you will get lost in the configuration files. Luna: Start with the brick, then build the wall. I like that analogy. Lucas: Exactly. Master the fundamentals of Linux and networking. Everything else is just a tool on top of that foundation. Luna: One final question for anyone listening who is currently stuck in a help desk role but wants to move up. Lucas: Take the tickets that involve scripting or automation. Volunteer to document the processes. Those are the bridges to DevOps. Stop fixing printers and start fixing pipelines. Luna: Powerful advice. It changes the entire trajectory of your career in tech. Lucas: It does. The tools change every year, but the logic of how systems interact remains constant. Master that logic.