Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Break Into Cloud Architecture
Transcript
- Lucas: So Luna, I was looking at job postings this morning, and something jumped out at me: cloud architect roles are popping up everywhere, and the requirements aren't as rigid as you'd think. Luna: Really? I always thought cloud architecture was one of those senior roles you need a computer science degree for. Lucas: That's exactly the myth I want to bust today. I spoke with a guy named Marcus who went from a six-month web dev bootcamp to a cloud architect role in under three years. No CS degree, no prior IT background — he was a restaurant manager before. Luna: Okay, that's a story I need to hear. How did he swing that? Lucas: So Marcus's path wasn't linear. After the bootcamp, he took a junior DevOps job at a small startup. That's where he got hands-on with AWS — deploying apps, setting up pipelines, dealing with outages at 2 AM. And he just kept learning on the job. Luna: So it's less about the degree and more about the practical experience. Lucas: Exactly. And that's the theme of this episode: how bootcamp grads can break into cloud architecture. The key isn't just knowing the services — it's about demonstrating that you can design systems that are secure, scalable, and cost-effective. Luna: But how do you demonstrate that without a job that lets you touch production systems? Lucas: That's where side projects come in — but not the typical todo app. Marcus built a mock e-commerce platform on AWS with auto-scaling groups, a load balancer, and a database that could handle traffic spikes. He documented every decision in a blog post. Luna: So he was essentially building a case study for his skills. Lucas: Right. And he shared it on LinkedIn, which got him noticed by a recruiter for a cloud architect role at a fintech company. The interview wasn't about memorizing services; they asked him to design a system for a hypothetical use case. Luna: What kind of questions did they ask? I imagine they wanted to see how he'd handle failure or scale. Lucas: Exactly. They asked things like, 'How would you design a system that needs to handle a spike in traffic during a product launch?' And he walked them through his thought process, referencing the mistakes he'd made in his own projects. Luna: Mistakes? That's interesting. So being honest about failures actually helped? Lucas: Definitely. He mentioned a time he forgot to set up a security group and exposed a database. He caught it, fixed it, and wrote about it. That showed he could learn from mistakes — which is huge in architecture. Luna: So it's about showing you can think through problems, not just know the tools. Lucas: Right. And that's why certifications can help, but they're not the whole story. Marcus had the AWS Solutions Architect Associate cert, but he also had the project experience to back it up. He said the cert opened doors, but the projects got him through them. Luna: That makes sense. I've heard that certs without practical experience look thin on a resume. Lucas: Exactly. If you're a bootcamp grad, you need to show you can apply what you know. And one way to do that is to contribute to open source projects. Marcus contributed to a Terraform module for managing AWS resources — that gave him real-world experience with infrastructure as code. Luna: Terraform is that tool for defining infrastructure in code, right? So that's a big skill to have. Lucas: Absolutely. And it's something you can learn on your own. There are tons of free resources. The key is to build a portfolio that shows you've deployed something real, even if it's small. Start with a simple serverless app and then scale it up. Luna: So what's the typical timeline for a bootcamp grad to land a cloud architect role? Lucas: Marcus did it in about two and a half years. But that included a year and a half as a DevOps engineer, then a promotion to cloud architect within the same company. It's not a direct jump, but it's achievable if you're strategic. Luna: And what about networking? I imagine that played a role too. Lucas: Huge. He attended local cloud meetups and joined online communities. He even reached out to a few architects on LinkedIn for informational interviews. One of those connections referred him to the fintech company. Luna: So it's not just about the technical skills. It's about being visible and building relationships. Lucas: Exactly. And that's a theme we've touched on before, but it's worth repeating. Tech hiring is often about who you know. Luna: Alright, so let's say I'm a bootcamp grad listening to this. What's the first step I should take tomorrow? Lucas: Start by creating a free tier account on AWS or Azure, and build something. It doesn't have to be complex. Maybe a static website hosted on S3 with a CloudFront distribution. Then add a database and a simple API. The point is to get hands-on. Luna: And document it, right? Write a blog post or record a video explaining your choices. Lucas: Exactly. That documentation is what shows potential employers how you think. And if you can make a mistake and fix it, that's even better. It shows resilience. Luna: I love that. And it's a great way to build a portfolio that stands out. Lucas: Before we go deeper into the interview process, I want to mention something. If today was useful to you, the way these episodes stay ad-free is listener support. You can buy me a coffee at buy me a coffee dot com slash fexingo. It's a small way to keep the show going. Luna: Yeah, it really helps us keep making these deep dives. Even a few bucks makes a difference. Lucas: So back to the interview process. Marcus said the key was to think out loud. When they gave him a scenario, he talked through his reasoning, even when he wasn't sure. That showed them how he approaches problems. Luna: That's a good tip. So what are some common mistakes bootcamp grads make when interviewing for cloud roles? Lucas: The biggest one is trying to memorize every AWS service. You don't need to know all 200. You need to know the core ones well and understand trade-offs. Like when to use a relational database versus a NoSQL database, or how to design for high availability. Luna: So it's about depth over breadth. Lucas: Exactly. And also, don't underestimate soft skills. As a cloud architect, you'll be communicating with stakeholders, explaining costs, and getting buy-in. So practice explaining technical concepts to non-technical people. Luna: That's something you can practice even without a job. Maybe by writing blog posts or giving a talk at a meetup. Lucas: Absolutely. Marcus did a lightning talk at a local cloud meetup about his side project, and that's actually how he got his first referral. So you never know what will open a door. Luna: So the takeaway is that bootcamp grads can absolutely break into cloud architecture — it just takes a mix of hands-on projects, certifications, and networking. Lucas: And a willingness to start in a related role like DevOps or cloud support. That's how you get your foot in the door. Once you're in, you can work your way up. Luna: That's reassuring for anyone who feels like they're not ready for the big role right away. Lucas: Right. The path isn't always straight, but it's there. And with the demand for cloud skills growing, it's a smart bet for a career change.