Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Break Into Site Reliability Engineering
Transcript
- Lucas: When you think about the highest-leverage roles in tech right now, Site Reliability Engineering is one of those fields where demand keeps growing faster than supply. And for bootcamp graduates, it's actually a surprisingly accessible path — if you know where to focus. Luna: I've heard SRE described as 'what happens when you treat operations like a software engineering problem.' But a lot of bootcamp grads I talk to don't even know what the day-to-day looks like. Lucas: Yeah, and that's partly because the title can be a bit opaque. At its core, SRE is about keeping large-scale systems running reliably. That means automating away manual toil, building monitoring and alerting, running incident response, and constantly improving system resilience. Luna: So it's not just being on-call and restarting servers? That's what I used to think. Lucas: No, that's the old-school sysadmin stereotype. Modern SRE is highly software-driven. You write code to automate recovery, you design dashboards, you do capacity planning — it's a blend of development and infrastructure. And that's exactly where bootcamp grads can leverage their coding skills. Luna: But don't most SRE job postings ask for a CS degree or years of experience running production systems? How does a recent bootcamp grad bridge that gap? Lucas: The requirements are often inflated, honestly. What companies really need are people who can think systematically, write scripts, and learn fast. Specific things you can pick up in a few months: Linux command line, a scripting language like Python or Bash, basic networking, and one cloud provider's ecosystem. Luna: Okay, so what's the first concrete step for someone coming out of a web development bootcamp? They know React and Node.js, but maybe not Linux. Lucas: First step: get comfortable with the terminal. Install a Linux virtual machine or use WSL on Windows. Learn to navigate the file system, manage processes, use grep and awk. Then move on to writing Python scripts that interact with APIs — like restarting a service or parsing logs. Luna: And how do they prove that in an interview without real work experience? A lot of bootcamp grads don't have a portfolio of infrastructure projects. Lucas: That's actually an advantage — you can build your own. Pick an open-source application, containerize it with Docker, deploy it to a cloud provider, set up monitoring with Prometheus and Grafana, and write a simple alerting rule. Then document the whole thing on GitHub. That portfolio project speaks volumes. Luna: So basically treat your personal project like a production system. I like that. And what about certifications? Are they worth it? Lucas: They can help get past HR filters. The AWS Certified SysOps Administrator or Google Cloud Professional Cloud DevOps Engineer are solid bets. But don't collect certs — focus on one, build the project, and tie it together in your resume. Luna: You know, this reminds me of something I've been thinking about lately. If today was actually useful to you — and I hope it is — the way we keep this show ad-free is through listener support. People who find value here sometimes toss a coffee our way. Lucas: Yeah, it's at buy me a coffee dot com slash fexingo. Just a simple way to say this content matters to you. It lets us keep digging into practical topics like this without any sponsors calling the shots. Luna: Exactly. And now back to SRE — one thing I've noticed is that a lot of bootcamp grads are scared of on-call rotations. How do you address that? Lucas: Fair concern. But in well-run SRE teams, on-call isn't a fire drill. You have good runbooks, you escalate when needed, and you use incidents as learning opportunities. Plus, the compensation usually reflects the responsibility. Luna: Let's talk numbers. What kind of salary can an entry-level SRE expect, say, in a fintech or e-commerce company in a major city? Lucas: Entry-level SRE roles — often labeled 'Associate SRE' or 'SRE I' — can range from one hundred ten to one hundred forty thousand dollars total compensation. Higher in places like San Francisco or New York. And the growth trajectory is steep; within a few years you can cross two hundred thousand. Luna: That's competitive with software engineering roles, sometimes even higher. And the skill set is more niche, which makes you harder to replace. Lucas: Exactly. And bootcamp grads bring something that traditional ops folks sometimes lack: a developer mindset. You understand version control, CI/CD, testing — those are huge assets. The key is to frame your background as a bridge between dev and ops rather than a lack of experience. Luna: Alright, so if someone listening wants to start this week, what's the single most impactful action they can take? Lucas: Set up a personal monitoring dashboard for your own website or app. Use Prometheus to collect metrics on uptime, latency, and traffic. Configure Grafana to visualize them. Then write a Python script that triggers a Slack notification if something goes down. That's your portfolio piece and your conversation starter. Luna: And after that? Join the SRE community — there are great Slack groups and the SRE Weekly newsletter. Start participating in incident postmortems on open-source projects. Lucas: Right. And when you apply, target companies that have a strong culture of documentation and mentorship. Fintechs like Stripe, e-commerce giants like Shopify, or even traditional enterprises transitioning to cloud — they all need SRE talent. Luna: So the takeaway is: bootcamp grads shouldn't overlook SRE as a 'too hard' field. It's actually a perfect fit for someone who loves problem-solving and wants to see their code have immediate, visible impact on system reliability. Lucas: Exactly. And with the right portfolio project and a bit of cloud know-how, you can absolutely break in. The door is open — you just have to walk through it.