#158 From Gas Station to Google with Self-Taught Cloud Engineer Rishab Kumar
en
January 31, 2025
TLDR: Quincy Larson interviews Rishab Kumar, cloud engineer and developer advocate at Twillio, discussing how he taught himself to code and build cloud infrastructure, his struggles with FAANG rejections, filling up the Infinity Guantlet with cloud certifications, and persistence. They also talk about his Terraform course, LangChain LLM deployment course on freeCodeCamp, Learn to Cloud guide, and his YouTube channel.

In episode #158 of the podcast, Quincy Larson interviews Rishab Kumar, a self-taught cloud engineer who has successfully transitioned from working minimum-wage jobs to securing a position at Google. This inspiring episode covers Rishab's journey, insights into cloud engineering, the importance of persistence, and practical advice for aspiring tech professionals.
Who is Rishab Kumar?
- Background: Rishab grew up in India and moved to Canada for studies. Financial struggles prevented him from completing his education, which led him to work as a pizza delivery driver and at a gas station.
- Self-education: Despite setbacks, Rishab dedicated himself to learning programming and cloud technologies through free resources, including freeCodeCamp.
- Career trajectory: Through hard work and determination, he eventually landed a role at Google.
Key Takeaways from the Episode
1. The Essence of Cloud Engineering
- Understanding Cloud Engineering: Cloud engineers design, build, and manage cloud-based systems. Cloud services are essentially rented computing resources provided by companies like Amazon AWS, Google Cloud Platform (GCP), and Microsoft Azure.
- Networking Fundamentals: Rishab emphasizes learning networking fundamentals, including how DNS works and how data packets travel. These concepts are crucial for anyone wanting to work in cloud engineering.
- Importance of Linux Knowledge: Rishab notes that a strong grasp of Linux is essential, as most servers operate on this OS. Understanding command line tools is critical for cloud engineers.
2. Overcoming Challenges and Persistence
- Rejections from FAANG Jobs: Rishab shares his experience of getting rejected from major tech companies multiple times before finally succeeding. His story illustrates the importance of resilience and learning from failures.
- Cloud Certifications: Throughout his journey, Rishab gained numerous cloud certifications to bolster his skills, referring to this as "filling the Infinity Gauntlet" with credentials. Each certification serves to validate his expertise and commitment to the field.
3. Continuous Learning and Growth
- Stay Curious: Rishab's natural curiosity and willingness to learn drove him to seek out opportunities beyond his comfort zone, such as taking on projects at work that were not initially assigned to him.
- Networking and Mentorship: He highlights the importance of seeking mentorship and networking with professionals in the industry, which became pivotal in his career advancement.
4. Practical Advice for Aspiring Cloud Engineers
- Foundational Skills: Rishab recommends aspiring engineers to focus on:
- Networking basics
- Learning Linux
- Gaining proficiency in a programming language (Python is suggested).
- Getting Certified: He urges individuals to pursue at least one associate-level cloud certification relevant to their chosen cloud platform (AWS, Azure, or GCP) to enhance job prospects.
- Embrace Automation: Knowledge of tools like Terraform for infrastructure as code can greatly benefit cloud professionals.
5. The Future of Cloud Engineering
- AI Influence on Cloud: Rishab anticipates that as AI-demand grows, the cloud engineering field will expand as companies look to leverage cloud services for compute-heavy tasks.
- Operational Excellence: Companies are becoming more cost-conscious regarding cloud expenses, thus seeking engineers who can help optimize resource allocation.
Conclusion
Rishab Kumar’s journey from humble beginnings to working as a cloud engineer at Google exemplifies the power of resilience, continuous learning, and leveraging available resources. This episode of the podcast delivers profound insights into the nature of cloud engineering and offers practical strategies for those looking to break into tech, underscoring that with passion and persistence, anyone can achieve their dreams.
Key Links Mentioned
- Terraform and LangChain Courses on freeCodeCamp
- Learn to Cloud guide – a free resource to help individuals get into cloud engineering.
This summary encapsulates Rishab's experiences and the practical steps he offers to help aspiring cloud engineers navigate their journeys successfully.
Was this summary helpful?
If I was gonna start from zero, where I have zero context, I was gonna learn some of the IT fundamentals on how networking works. So like how internet works, first of all, DNS, how packets transfer, how computers communicate to each other, because at the end of the day, all these servers live in the cloud.
You know, they use networking to talk to each other. The second skill I would really spend my time is on how Linux works. Welcome back to the free code camp podcast, your source for raw, unedited interviews with developers. This week's musical intro with yours truly on the drums, bass, guitar and keys. We're going back to 1989.
Nintendo Entertainment System Classic duct tails theme from the moon.
Welcome back to the free code camp podcast. I'm Quincy Larson, teacher and founder of free code camp.org. Each week we're bringing you insight from developers, founders and ambitious people in tech. This week we're talking with Rishab Kumar. He's a cloud engineer and developer advocate at Twilio. Rishab grew up in India and moved to Canada for school
But he couldn't afford to finish. He resorted to delivering pizzas and working at a gas station, but he worked hard to teach himself how to code using websites like freecoacamp.org and how to build cloud infrastructure and eventually he got a job at Google. Before we talk to ReShop, support for this podcast comes from a grant from Wix Studio. Wix Studio provides developers tools to rapidly build websites with
Everything out of the box, then extend, replace, and break boundaries with code. Learn more at wixstudio.com. Support also comes from the 11,043 kind folks who support free code camp through a monthly donation. Join these kind folks and help our mission by going to free code camp.org slash donate. Rishab, welcome to the podcast. Hi Quincy. Thank you. Thank you for having me.
Thank you for your many contributions to the free code camp community, which we'll talk about later. But first, I want to talk a little bit about what cloud engineering is for people who are uninitiated before we get into your backstory, which is fantastic, like hero's journey. What exactly is cloud engineering? Okay, so my understanding of it is that cloud engineers are IT professionals. Like it's a segment with an IT or
People, design, build, and architect on cloud. So cloud, if you don't know what it is, it's basically someone else's computer. There are a lot of public clouds available right now. So think of Amazon AWS, Google's DCP in Microsoft's Azure. So basically you're renting out a compute from these vendors instead of buying compute, like having your own servers.
So anything in regards to cloud, whether it's designing, building, or architecting on top of it is called cloud engineering. Yeah. And so that's the specialization you've gone down as a more generalist dev. You've got into like cloud engineering and like often you'll hear the term DevOps, which would you consider it like basically a synonym DevOps kind of like maybe predates the full move to the cloud. But nowadays,
Almost everybody's using the cloud, right? Yeah, like free cooking. We have more than a hundred cloud servers around the world. So we can have like really good uptime and we can have various services available in various places and all that. And low, not just uptime. We're very proud of our 99.99% uptime, but four nines. It's not six nines like Amazon would have necessarily.
But also, of course, just latency and stuff like that, like making sure that like people who are in Punjab, where you grew up, have fast access to free code camp and making sure people in Nairobi have fast access, people who are in Buenos Aires, you know, various parts of the world that they have a good connection in that they can quickly access learning resources.
So you built a career around this and I'm very excited to get into your backstory. What pushed you in the direction specifically of cloud engineering versus more general software engineering?
That is a really good question. I'm trying to go back to like the 18, 19 year old me of what was going on in my head. I think so I got into tech by doing tech support. So tech support or IT help desk was my first role. So I was doing tech support for a SaaS company.
and was helping customers with the issues varied from being product issues to sometimes networking issue or OS specific issues. So the amount of things you learn, like you need to have like a, you wear multiple hats because sometimes you're running command line tools to figure out why this particular port is not working or is not open.
And the other times, it's basically permission issues on the US level. And during that time, I found out how the RSS, which I was supporting, was using AWS because of one of the tickets needed escalation, I needed access to like our database. And that's when like,
The flow was that I escalated to a cloud engineer who will grant me access to run a specific SQL statement. I'm like, interesting. Like, I don't know what AWS, like I've heard the term, but I don't know what it really is. And that's when this specific engineer started explaining to me, it's like, oh, we have our servers. It's basically we're renting servers from them. And I'm like, oh, very interesting.
So I definitely was always fascinated with like server administration, server management and Linux had a really, you know, soft spot in my heart. And I loved networking aspects of it too. Talking about like general IT back in 2015, 16. Yeah. And.
I'm like, this is really cool that you don't have to have servers on-prem. You can just rent them out. So that got me interested. And there was a spark. I'm like, I need to learn about this more. And that's when I started asking this cloud engineering team more questions. I'm like, oh, OK. They were very kind to take me to a regional conference in Toronto.
Mm hmm. I took you to a conference. Yeah, these people are super chill. Like I talked to a lot of devs and they're kind of almost afraid of IT people. Like, oh, don't screw up my computer somehow with some weird, you know, software that the company needs to install in there, right? Like, like, uh, I have just one anecdote of a person who's like, who like literally like whenever IT's coming by, they'll like figure out an excuse to be out of the office and they don't have to interact with them. I'm afraid. Oh my God.
I'm sad that's the like the notion, but no, I would consider myself very fortunate that I had people who I could really rely on when it came to like, you know, mentorship stuff.
So even before they took me to the conference, at this point, I was six, seven months in tech support. And I was like, I don't want to do tech support for like my entire career. There's nothing wrong with that, but it was just not me. And like, I want to do something more. So I asked for advice. And they're like, if you don't know what you want to do yet,
maybe shadow different roles that we have at the company. And that's what I did. I shadowed software engineers for a week. They had like a front end and a backend team. I'm like, no, after a week, I was like, no, this is not for me. Then I shadowed QA engineers for a week. I realized you need a lot of experience to be a QA engineer with us when specifically when the QA team is very small. Yeah.
And then the last team that I had to shadow was the cloud engineering team. These were the all three engineering teams they had, or sub teams within the engineering department. And the cloud, again, I was kind of biased previously too.
I shadow that I'm like, a lot of this makes sense. I have a lot of transferable skills. Instead of managing servers on-prem, I'll be doing it on the cloud. The only gap is learning terminology that AWS or Azure, GCP uses. Apart from that, everything else makes sense. And that's when after that week, they're like, oh, we have a spare ticket to this conference about cloud. Would you like to go? And I'm like, sure, if the expenses are covered, why not?
I went to the conference and saw all these passionate people talking about cloud. I'm like, this is serious. I can't pursue this as a career. And I think going to that conference, talking to a lot of people outside of my company made me realize, okay, I need to, now is the time to make this change. And this was late 2018.
Okay, so you've been work. So we're going to rewind and talk a little bit more about your career in a second. But do you think that the cloud, cloud engineering roles like DevOps, like that that field is growing? Do you think it has a bright feature or do you think like a lot of it's going to be automated or consolidated? Like what is your take on whether people should be getting into cloud in 2025? Great question. I think cloud is.
You know, there is a term I heard about like how every company is a data company now because the amount of data we have. Um, I think that is also true for cloud. So like every company right now is a cloud company because in some way or form you're using cloud computing, whether it's through SAS, like using Gmail software service.
software as a service, whether it's to platform as a service or infrastructure as a service. And with the rise in like all the AI stuff that we are seeing, I think the need for having compute that can handle workloads for AI and LLMs. I think it's only going to increase. Of course, the use case is different now, but if you find a balance between how you can
you know, be proficient and how like AI and machine learning and LLMs use compute and then kind of like have that in scale, set along with cloud skills. I think that would be my like advice. But yeah, cloud is cloud is definitely here to stay and it'll be.
What you just said makes a lot of sense to me because like quantum computing, for example, let's say hypothetically, that does get traction right now. It's more speculative. But you're not going to actually want to have a quantum computer. You're going to want to rent access to it because it's going to force in to maintain those things. Right. Similarly, if you're doing like machine learning, you're training your own model. You're not going to want to buy a whole bunch of
super expensive graphic cards and build your own, you know, that would be a tremendous expense. Like these things cost a fortune. And if you can just use, you know, like a cloud service to access them to train or even just have an ongoing like GPU cluster that you're imprints on, that's so much more economically viable for like a typical business. Only the largest businesses would want to maintain their own data center of
really anything in my opinion and I definitely a lot of critics of cloud engineering and stuffs are just like just buy your own server and put it on a rack and like use you know put it in like rack space or something like that there are lots of companies where you basically just bring your own hardware and you put it in their data centers yeah and I definitely hear you like the using the cloud is expensive and but
If you want to have really good uptime and you don't want to have to worry about like some power outage or some flood or some any number of things that you wanted to be somebody else's problem. And also if you have unpredictable demand scanning or things like that, like there's so many reasons to embrace the more expensive, but more convenient and more robust option of just, you know, using cloud servers. And of course, like you've got Google, you've got, of course,
Amazon, AWS, you've got like even companies like DigitalOcean and places like that that have options. And then like there's so many different vendors you can choose from and you can even go multi-cloud and like distribute your servers across a whole bunch of different clouds to further mitigate risk and things like that.
And it is a truly deep skill going into cloud engineering. So my impression of talking to a lot of cloud engineers and DevOps over the years is that it's going to get more and more complicated and the tooling won't necessarily keep up with the changes in the rigors of what you actually have to know how to do and what you're doing day to day.
and there's only so much that can be automated when things are changing rapidly, and you have completely different types of compute coming online. For example, you taught a Langchain LLM development course. For example, in your cloud engineer who's dipping their toes into machine learning.
and in teaching those concepts. And you've also taught a very popular course on Terraform and deploying websites to Google Cloud using Terraform. And so I'm going to be linking to both of these courses in the description if you want to benefit from some of Richard's expertise.
where I want to go now is for those people that are sitting in a gas station listening to this, you know, handing people, you know, like checking people out and stuff, uh, going in and, you know, making sure the bathroom's clean and hasn't flooded or something like that. Like I've worked a lot of retail jobs. I worked at like a grocery store for a couple of years. I worked at, uh, Taco Bell, like a year or two. Uh, you know, I know that it kind of sucks.
Yeah. But the movie Clerks is very accurate in terms of just sitting around waiting for people dealing with customers and stuff like that. And that was a big part of your life after you had to drop out for economic reasons from university. Let's go back. I'm not going to go all the way back because I grew up in Punjab. You studied at pretty good public schools. Your dad is an engineer. He's somebody who values education. So you went to good schools in Punjab. And then you immigrated to Canada.
Right and that is like an excellent place like that country is like very receptive to smart people coming over and living there and Yeah, so I want to I want you to take me back to that moment, right? We could skip a lot of the childhood and jump forward to you arriving as an Indian Canadian or soon to be Indian Canadian What was that like those first few years in Canada?
For sure. I think did the personality that I have developed, mind you, I was 17 when I migrated here, almost 18. And I think the values and personality that I've developed and what I am today is it is a lot of what I've gone through in those two, two and a half years as soon as I moved here.
I don't regret any of it. I just want to preface that even though there were challenges, struggles, and I'm so glad I had to go through them because that's what made the re-ship that I am today. The thought process, I think, when I am trying to go back to that time and see how
what Rishabat that time was thinking and what was going on in his mind. Studies, at least for the first semester, was not. Because I went to college, so I did a two-year diploma in Canada instead of a four-year degree.
Studies were not my priority at least for the first semester. The reason being like I realized that, oh, I got a job at a gas station, I was doing night shifts, and in the day I was going to the college, but
For a 17 year old kid, when you realize that you're making $10, $11 an hour, it's very simple math. Like, oh, the more amount of hours I put in, the more amount of money I'm going to make. So I think that kind of got to my head and I prioritized work over studies until the first semester ended. I got my results and the GPA didn't look good. And I'm like, oh,
And also, as you said, my dad really values good education. And he's like, I know you're not doing a degree, but I want you to take this seriously, because I don't want you to be stuck at a gas station. There's nothing bad, but I think of it from a perspective of a father who wants his son to succeed in life.
And that really hit me and I'm like, yeah, like all this hard work that he did so that we could have like a, you know, comfortable life, um, will be down the drain if I don't take full advantage of it. So try, try to like prioritize studies and like I was still working. I worked at a gas station for two and a half years, but I look, uh, it took like, I did lesser shifts and, um, started prioritizing studies over it. And like,
I saw the results and I also like it became really interesting. I think second semester we had intro to networking, we had intro to operating system and intro to Linux. So it was very like interesting for me. I'm like, oh, this is how the tech works underneath because a good thing about college or universities is they go really deep.
And, you know, understanding how the technology works, whether it's the day-to-day computer user to like how TCP three-way handshake works. Like it just fascinated me so much. And I was very curious. I've been very curious throughout my life. I think like curiosity is one of the really good traits that I like about myself is like I get curious and then go down a rabbit hole of researching through that.
And yeah, that's how the next three semesters went. I was able to land a co-op opportunity. So co-op is basically like internships, but for college, like community college and stuff, they're unpaid. They're part of your diploma, basically, so that you're industry ready. So in order to get your diploma,
from the college, you have to do a two-month co-op or internship. And I did that as an IT admin, like a junior IT admin at a company called Print Fleet. And I'm so glad I did that because I even loved it more than my education. I'm like, oh, this is how you apply all the knowledge you have gained.
Um, and I like killed it in my internship. They were really happy that I took initiative, like a few of the projects, they were not even projects until like I initiated them at this company. So they were really happy with my willingness to work and how passionate I was about IT. Yeah. So they were like, Oh, we don't have an IT admin role open, but would you be willing to do tech support for the SaaS?
And I'm like, at this point, anything is better than gas station and delivering pizzas. So sure. And then that's when I realized the salary they were offering was definitely more than what I was making at a gas station. So that was the added bonus to it. And that's how I started my tech support role, basically.
So to recap, uh, you, you kind of like hit a plateau where you felt comfortable. You're making good money, working at the gas station. It's not like working in those types of jobs. It's not like completely taking all your brain power. You can still think about things you can read. You can listen to music potentially. You can do lots of things. So it's kind of like a fun job, but the compensation is much lower, but back then, you know, of course, before the inflation we've experienced. Yes.
You know, $10, $11 an hour wasn't, wasn't that bad. I mean, that was enough to have money to go out and like, you know, having stuff. Oh, definitely. Definitely. Yeah. Like I was able to like also help with like some of the tuition that was left, even at $10 and $11. And I was living comfortably, like, you know, rent, living expenses and stuff. So yeah, definitely I was like getting in that comfort zone of like, Oh, this is gonna work out. Yeah.
Well, and it was your kind of your ancestral duty. Your father worked very hard to provide this opportunity for you and you would need to do something similar to your family down the road and also your natural curiosity. So once you got that curiosity going, and once you actually genuinely got interested in computers, it sounds like your curiosity just carried you the rest of the way, even on the job, going out and finding exciting projects that hadn't been started and starting them.
just to continue to expand your learning and your experience. And it sounds like you made excellent use of the opportunity you were given through that internship. And also the humility to not necessarily take like a higher level, but just take whatever work was available. It was still a step up from working in a gas station. And it sounds like you recognize those opportunities and you didn't like shop around. You just took the one right in front of you and started getting to work, which I think there's some match of that in this situation.
Let's fast forward a little bit to you're getting into your career. You talked about getting into cloud engineering from IT and Just having some champions within your own company who like first of all your company sounds super chill The fact that they let you shop around and figure out what specialization you wanted to go into they clearly saw Promise in you and they wanted to nurture that and
And I think so many companies just will, when they need somebody new, they'll go and hire somebody completely new. They don't necessarily invest in the people they already have. And I think that's a big mistake managers make. And I'm a manager and I always want to build up and train and cross train and have people pivot between roles and things like that. And I think that's great. And you've been able to pivot between roles.
And this is a testament not only to your own ability but to the flexibility and the wisdom of your employers. So shout out to them. So you were able to transition into cloud engineering as a result of doing this conference and then just learning like how did the transition happen? How did that pivot happen?
Yeah, so got back from the conference and I remember sitting in the cloud operations manager office. She had an office and I was talking to her. I'm like, I'm serious about this. I want to transition to cloud. And as you said, like shout out to them, they were very supportive. And she's like, OK, I have this.
We primarily use AWS. So I'm going to, like you don't have to, like that decision is kind of made for you. If you want to transition here, you'll have to be skilled in AWS as a cloud provider. I'm like, cool. She gave me a roadmap. So like she's like, study for a cloud practitioner that's going to get you up to speed with all the cloud terminology, you know,
like infrastructure, software, software, I didn't know what all these terms meant, costs, like how billing works and stuff like that. CapEx, which is capital expenditure to OpEx, which is operational expenditures, a lot of terms. I'm like, okay, this is going to take time. She's like, yeah, yeah, take your time. Go through the cloud practitioner material.
If you want to sit the exam, sit the exam, but also like build projects like get hands on. It's not just theoretical. I'm like, okay. So after I got the roadmap, she also gave me some books that they already had that I could study from.
She invited me to the team meeting. So this is pre COVID, you know, we were in office five days a week. Um, they had a team meeting every week and I was invited to those, even though I'm just, you know, a tech support person. That's pretty cool. So they were like grooming you to ascend essentially and making sure that you had sufficient contacts and everything like that, even though you were still studying to earn these certifications.
Yeah, yeah, and I think that was very valuable because that just kind of showed me how this team worked. What are the problems that they're facing? Where is like not at the beginning, but later like down for five months, I was able to kind of map it in my head that how I can come on this team and help them. I think if you have that kind of mindset, it's very easy to market yourself to be part of.
like to be part of a new job that you're applying for or to be part of a existing team that is in your company. So it took me five months, five to six months to like
not just clear the examination, so the cloud practitioner certification from AWS, but also to have like, I had two projects that I built and also how AWS was being utilized at this company. I knew it to like very deep extent on how every service is being used by the SaaS.
And that's when, and at this point, it was a year into the tech support role. There was an opening for a cloud engineer role for within the same team. And before applying to it, like, of course, I asked my manager who, like the tech support manager is like, yeah, you have been like, putting in the extra time for like last six months, you have been shadowing them, like,
I know about your intentions, so you're good to, like, lead onto this path. Then, even before applying, I asked all the Cloud engineers when that team head, do you think I should apply for this role? Like, I don't know if you're looking for someone senior.
And I'm like, nope, we are ready to put in the word for you if it comes down to that. Wow, you did the groundwork, man. You totally laid out the groundwork. The fact that you've got the blessing of your current boss and you talk to everybody, like this is textbook, how to do a pivot job. I mean, I really can't think of a better scenario. You're working alongside both of these teams and you're gaining the respect of everybody involved.
And of course, your IT manager probably wants to keep you ideally, but they can't hold you back from your destiny, which is to become a specialist in cloud development. And they see the writing on the wall that you're ready and that you are going to eventually move on. And they don't try to like clip your wings or hold you back. Yeah, that's amazing. Yeah, shout out to them.
And that's when I applied after I got the blessing and I'm like, okay, I'm gonna shoot my shot. At this point, so previously we were a small company, we were 38 people, entire company, three people on the cloud team. During somewhere this time, we got acquired by an enterprise from the US and we went from 38 people company to being 2500.
What? Yeah. And that is why, oh, because you were a subsidiary, not like the team didn't grow that much. Okay. But you now are part of a much larger hierarchy. Yes. And they have their own like, um, they brought in their own management. So one of the challenges I had is the interview was going to be with this new, you know, management team and leadership team, which they didn't know anything about. They had like zero context on what I have been doing.
My resume had only experienced from like tech support, but a shout out to the cloud engineering team that I did shadow they were like able to vouch and they're like, no, you should definitely, you know, I know we have like three, they had three external candidates who were like a solid candidates with experience and stuff. But they really vouched for me to be like, let's just have him for the interview.
I knew my selling point was telling them that I know the SaaS inside out and how we use AWS. External candidates, they at this point, they don't know how AWS is being utilized here. So I tried to stick to that and I'm glad I did. We had like a 45 minute discussion on.
um, uh, the architecture pattern that we use and the He was the director of engineering and he was really impressed. He was like, um, you'll probably hear back by end of this week I was very nervous until like I saw the email that you're in Because it's to me like, you know, you feel like an imposter because you have these, um,
people that you're competing against who are, I know, specifically there was one individual that had eight years of cloud experience. Wow. That's a stiff competition. And several of them probably had university degrees, too, which you did not have. So I mean, like, regardless of what people say, like managers will say, oh, we don't really care about degrees, but like that is definitely like weighted in favor of the candidates who have university degrees. They're just seen as less risky.
Yeah, yeah, yeah. It's a good filter, I guess, when it comes to hiring. But the other upper hand I had is they don't have to pay me as much as they would have to pay someone with a university degree and eight years of experience.
For me, if you give me a significant jump from what I was making in textbook, I'm going to be happy. And that's what happened is they gave me a good jump from what I was making in textbook. To this day, I remember even though I have progressed through my career pretty decently, like salary-wise and compensation-wise.
I haven't never felt that happy. Like that was I still remember how I felt seeing that offer letter and the jump from like making tech support salary to a cloud and junior salary. Even now when I look back it was not.
to the market standards. It was not that much, but I also know what value I brought. Like, you know, I didn't have a cloud experience as like, if you consider professional experience and they were just taking a chance on me to see how he will do. But yeah, that's how that's how I transitioned.
Yeah. What certifications did you ultimately earn as a cloud? Like, I'm just curious if you can list some of the certifications you have currently or like have had. You may not necessarily keep them current. They generally expire after three years. But like the vendor certifications, any more general certifications, people who are in IT may be thinking or or people who just want to work in cloud engineering, who aren't even working in tech or if you're a software engineering, you want to transition into a cloud engineering, like,
What certifications have you earned and what would you recommend? So it's a two-part question, I guess. Which ones have you earned over the course of your career? So the very first certification that I did is funnily, not even funnily, but it's the free code camp responsive web design. The reason why, and this was during my tech support time, is I did do intro to HTML and JavaScript in my two-year diploma.
But I wanted to build like a website as a project for my transition to cloud engineering and I wanted to host that in AWS. But I didn't know how to build a website apart from like a simple HTML page. So I did the responsive web design.
from free code camp. I loved it. Like that blew my mind that resources like this exist for free. And that is for like, you know, an 18 year old kid who paid huge amounts of tuition to a coffee. So when I realized that, I'm like, Oh, this is so cool. Because it was so practical, you know, because you had assignments at the end where you build projects apart from the live coding challenge that you do every day. Like the at the end, you get
an assignment that you build and it gets checked and stuff. So very college-like experience. So that was the first certification I did. The second one was the cloud practitioner from AWS, which is the foundational.
Yeah, I'm sorry. I was going to jump in and say, like, that's more of the foundation. It's less technical. It's more like how the cloud works, like understanding how different services work and different options you have when you deploy to AWS. And yeah. So, so that one, even if you're not a software engineer, you could potentially go and get that certification. Definitely.
And free code camp has several preps. Yes. Most of which are taught by Andrew Brown who is this legendary. Like he's a CTO who just is obsessed with taking certification exams and passing. I think I've got an interview on him with him on the podcast, by the way, if you're curious, I can't remember what episode it is. But Andrew Brown created this company called exam pro also Canadian, by the way, he's in Toronto.
And so he publishes regularly. He's covered all the AWS certs, all the Azure certs, all of the Google certs. He's covered like some of the new GitHub certs. He's covered a lot of stuff, Kubernetes. I think he's covered chair form. Yeah, lots of stuff.
So anyway, I didn't mean to interrupt your flow. I was going to mention because I used Andrew's Cloud Practitioner course on free code camp. So all of this is available on free code camp YouTube. If you just type AWS, all of his AWS courses are going to show up. So I used his course to prepare for that. And then also one side transition into the Cloud engineer role. I got my solutions architect.
which is a bit more associate level than the Cloud practitioner. I got my developer associate and my sysadmin, or sorry, I think it's called sysadmin. Yeah. So there are three associate level certifications from AWS. So I got all three of them.
Then, because we were acquired by this big enterprise company, they used Azure and some of GCP as well. Hey, Google Cloud Compute. These are the big three. Yes, multi-cloud. Basically, they had
they were like this big corporation that acquired different companies. So depending on which company they acquired, if they're using Azure, if they're using GCP, you don't really know. You'll know once the acquisition process has started and stuff like that. But basically we had sister companies and they wanted to consolidate the engineering teams. So instead of just
our cloud engineering supporting just our SaaS. They wanted to support at the enterprise level, which meant if there are people who are willing to upskill in Azure, you know, you had incentive of what you're going to stay with the company for longer and be part of a bigger engineering team. Did you opt to earn Azure certifications as well then?
Yeah, so I started up skilling in Azure, did the AZ 900, which is the fundamentals, the Azure fundamentals. Did the AZ 104, which is Azure administrator, AZ 204, which is developer associate, AZ 400, which is the DevOps engineering expert.
For the 900s, there is like SC900, which is security, AI900, which is AI fundamentals. I did all the 900s, so I did all the fundamentals, which are I think four or five Azure certifications in themselves. And then I went on to the associate once. The toughest one is the expert, so which is the easy 400, which is the DevOps engineer expert.
Because later on in my career, I transitioned to a DevOps role. Wow. So I've been keeping count and it sounds like you've gotten at least a dozen. Last I checked. I think I have around 19. Wow. Yeah.
It's not quite the 50 that Andrew Brown has, but his whole company is based around him passing the certification exam, helping you pass them. Yeah. You're just taking these to be able to continue to progress in your career. That's really impressive. Man, you must be really good at taking exams after all this time. I think so. I think so. Also, it really helps as you progress through your career.
I have made like few blog posts and videos about this. I recently took the AWS DevOps engineering professional, which is considered a very tough exam. I didn't study for it at all and passed it. The reason is because now I have
like the amount of experience that I have just speaks for itself. And like I have the underlying knowledge for most of these exams that I can just sit down. And if I have to do like few prep, like it usually takes me a week to just look at things that I'm not using day to day. And then I just sit my exam compared to like me just starting out learning about this new cloud. What is the cloud? You know, it's very different.
Yeah, I mean, that's a testament to the accuracy of the certification, if a professional who can go in without any prep, completely cold and still pass it just based off of things they do day in, day out. Yes. So it sounds like it's pretty well designed. And you said that's the AWS DevOps professional. Congrats on passing that. Thank you. Man, it sounds like you're like filling up the entire infinity gauntlet with different certifications. Did you ever give a Google Cloud search?
I did as part of when I went to Google, because I was going to work on the GCP team. You were required to get the associate cloud engineer within your probation period. So I was able to get it within the first 20 days of joining Google. I'm like, OK, I'm just going to sit this exam in a past. So for GCP, I only have the
associate cloud engineer that too, because it was kind of like a job requirement. Yeah. Well, working, let's talk about Google. So a lot of people are like, Oh, Google's just a big tech company. And like, I talked to a lot of people that work at Google. It's just another big tech company. It's not that big a deal. But like for like the average kid in India or China or even in the United States, like thinking about like, where do you want to apply? What would be your dream job? I bet you like probably like,
seven out of 10 of them would say Google would be the company they wouldn't work at. You've made it if you work at Google, right? Definitely. And a lot of people for them, it's like, there's like kind of your job application process before you've gotten a job at Google and then your job application process when you're an ex-googler.
It represents this Rubicon, after which you cross it, you're just completely different in the eyes of recruiters and hiring managers and people like that, because you've gone through that gauntlet and you've worked there. Maybe you can talk a little bit about your experience at Google and what it was like being there and getting into that role. I'd be excited to hear it.
For sure, for sure. I think the story is kind of out there, but for a bit of context, COVID happened and everyone was stuck at home. Specifically, Canada, at least our state or our province had pretty good, you know, strict regulations. So I was just stuck at home now having more than
ample of time to be on my computer. And I landed on like these day in a life videos of people working at Google and then you go down the rabbit hole off. There are people who are kind enough to share their compensation, the amount of money they make at Google or any other fan company. And to me, that was like a light bulb moment. I'm like, Oh,
I should apply for big tech companies because I think I'm skilled enough now. And later on, so I didn't start up right away applying after watching a day in a life vlog, but I started preparing for
You know, big tech interviews and stuff. Like, what is all that they ask? Like, system design is one of my, I would say, strengths because of the background I have. So I started learning about how Google Maps work, like to very small detail how Netflix does streaming.
There are a lot of good videos available on YouTube and free code camp itself on how these, how basically architecture patterns work and how they have been able to architect these big services that are used by billions of people. And luckily, I think it was June, May or June, a recruiter reads out to me,
on LinkedIn from Google that, hey, we have this team called TSC in Canada that is looking for candidates. And I think it will be a good fit. And I think that works out really good when a recruiter reaches out, then you applying to Google's career site. So I'm like, yeah, I'll definitely be interested. And so they started the loop. The loop was six interviews. It's interview as well.
And I was working full time, so I had to be like, oh, we can only do like one interview a day kind of thing. And it took me like two weeks, I think, to go through all of them two or three weeks.
I also asked them for one week for prep before starting the loop. So the entire process took me four weeks until I got a rejection. So the reason I got a rejection, I knew this, I bombed my coding challenge interview.
Yeah, that didn't go well. But every other thing, I think I was pretty confident. And I was like, maybe they'll ignore the coding challenge because how the other interviews went. But no. So I got a rejection and I was bummed out because for me, I thought this was my only chance. This was my only shot to get into a big tech company.
Before this, I was also talking to an AWS recruiter for a cloud developer role, and that one was also tragic because
I bombed my first interview which was like general text screen. So it was not like specific to like coding challenge or networking. They were just going to ask multiple questions that could be anything like how to optimize the SQL server or like there were some networking questions and stuff. I bombed like for some reason they
There were a few questions that I found challenging, but basically they didn't put me through the next round. And a lot of these interviews, my understanding, not having guns were a lot of them myself, is it is kind of a luck of the draw. Like if you get lucky and they ask you the questions that you have a good understanding of the domain and you can answer them well, then
Yeah, you got in. If you get unlucky in the ask you, you know, that you don't have a lot of expertise in, then, you know, so to some extent it is kind of a numbers game just by virtue of the sheer arbitrariness of a lot of these interviews and, you know, which way the dominoes can fall.
Definitely. Now that I look back, I definitely think that. After having my rejection at Google previously also being rejected at Amazon, I was not in a good place. I still remember I was just a sad person for
At least a week. It was affecting me in ways that it shouldn't have. Now that I think back and...
Yeah, I just dusted myself up and I'm like, OK, so these big tech companies, they have a cool down period. So you can't really apply for new roles until six months. And that was what I was told by both Amazon and Google. And I'm like, OK, we'll revisit this in 2021 because at this point it was August. Yeah. And out of a sudden in December, like early December, first week of December, a recruiter reached out from Google again.
And they're like, we have like an adjacent team to the role that you interviewed for. They call technical solutions specialist. I'm like, okay. And they briefly explained me how this team is adjacent and stuff. And then they're like, are you willing to hop on a call? I'm like, sure. So I hopped on a call and then they're like, hey, we know. So because they didn't provide me any feedback back when they rejected me.
Companies don't provide feedback on how you did in each one. And generally, that's just because they don't want to get sued for discrimination. Yes. But this time, you did really good on your system design, your network troubleshooting. And there was another one that you did really good. The ratings were really good from Googlers. The coding challenge is what you bombed.
But because this is just a team that don't really need the coding, like the interview process doesn't have a coding challenge. I'm like, okay. They're like, if you want to consider this team, we can move on with the interview process. Okay. So you have to repeat all those other things that you've previously done.
Exactly. That's what was surprising to me. They're like, since you did this three and a half months ago, we have that rating that we are going to use. And you only have to sit down with the hiring manager to see if you're a team match or not. And they have this entry we call Googliness, which is basically behavioral. Yeah, it's like cultural cultural thing. Yeah. So I did that. And that was like just one 45 minute call. That went really good. And
instead of taking it four weeks like the last time. This time, the first week I talked to a recruiter, had my googliness. Second week I got my offer. It was so quick.
And I'm like, oh, um, and then, you know, it was surreal for me. I'm like, I have an offer from Google. Obviously it had like it was good pay bump stocks and stuff. Like I was also not used to that. Like the previously for four and a half years, I only made like base salary. I didn't know like total compensation is a tank where at big tech companies, you get stocks, bonuses, and then
apart from your just be a salary. So that was really good. I think not just from monetary perspective, but also career aspect of it too. And yeah, and I joined Google. Yeah. And what happened during the time that you were Google? I think the first month went by really quick. As I said, like the onboarding
It was like a hose, you know, just too much information. Yeah. Drinking from a fire hose. It was just too much, too much information. I think the things that I loved was the structure they had and you would like, you know,
Assume that because of how big Google is. They already have a really good structure on how the onboarding is going to happen. Whereas I come from working at smaller companies. It was not that structured. So that was really good experience. The team was great. My manager was great. Were you working fully remotely still?
For the first month, yeah, but I was required to relocate to one of the office towns. So I chose Waterloo or Kitchener area. And then they basically covered the relocation stuff. So I relocated to a new city. That's when I started going into the office.
And I really enjoyed it because the perks and the offices that Google has built, they're just mind-blowing. And the food was amazing. And our setups, obviously, were amazing and stuff. They create a good workplace environment for you to be feel comfortable and have everything that you need while you are working or whatever, hours.
They might be, but that's also when the unfortunate time of layoffs started happening. A lot of companies obviously Google did their own and a lot of the teams that were adjacent to us and direct the our teams were also affected by these layoffs, which caused like a lot of uncertainty.
And there were just decisions that were being made at the leadership level, like outsourcing to low cost of living countries and cities, specifically for this role. And I had my own reservations about it. On top of that, I didn't enjoy the role as much, because a lot of it was
supporting GCP customers, whereas I had the idea, talking to the recruiter, that it's going to be more of a consultant role, where you will be architecting GCP infrastructure for a GCP client.
but it was more of supporting people or supporting customers. And someone who has worked in tech support previously, to me, it felt like I started feeling like I'm back four years.
in my own career. Nothing wrong with the role, nothing wrong with the people that were like, I walked with like, they were amazing people. Oh, my manager was amazing. It was just me not being happy about it. It sounds like you weren't able to use a lot of the knowledge that you've built up over the past four years. You were just going back to stuff like, yeah, I can, I can imagine how that would feel like a big step backward.
Yeah. So I started looking at what I could do still because Google is like, I didn't want to leave Google. That was my first thought at least. Um, and right after my probation and date, which was 90 days or three months, I told my dad, like how, and it started affecting my day to day to like my personal life as well. Like I was unhappy and not, you know, if you don't have a fulfilling job, it affects other aspects. I mean, it's a huge part of your working life.
Exactly. And I told my dad about this and he, he thought I was going mad or something. Um, I mean, you, you achieved the dream. Like he's an engineer and he probably wants you to have financial stability and be able to provide for your family and have prestige and all these things. Yes. And here you are. You've achieved the dream, but it's not exactly what you were, what you thought it was going to be.
Exactly, exactly. But to his advice, I spent another month. I'm like, OK, maybe this is just a change that I'm not comfortable with. I'll take some time, get used to it. But that was not the case. I also tried transitioning within Google. But obviously, there are policies that you have to stay in the role for a year before you can pivot to something else. You need performance ratings and stuff.
Um, and I guess I was just not ready to wait like another 10 months, um, for a move, uh, and I couldn't bear in this role. Like I couldn't spend the 10 months in this role. And that's when Twilio happened. So Twilio saw what I was doing on the side, you know, creating technical content on my own YouTube or my blog. And Twilio is like, Hey, we have this role open and we think it will be a great fit.
Yeah. And I'm going to give people some context in Twilio as a company. Like it is a really awesome company. Like I have a profound amount of respect. I've been to their headquarters a few times. I've talked with tons of Twilio engineers over the years. I've used Twilio for a lot of hackathon projects. Recooking doesn't currently use Twilio for anything.
But if you're doing anything that interfaces with phones, like sending text messages, making automated calls, receiving calls from clients and routing them, there's an incredible amount of telephony that is opened up through their various APIs and things like that. And you can kind of completely leapfrog having your own switchboard and all the other stuff that you used to have to have and using just interface with APIs as a dev.
There you go. We're not sponsored by Twilio, but I wanted to give people some context. This is like a big tech company. It's a big deal. They have very high standards in who you bring on. So even if you haven't heard of it because they're doing like a pretty niche thing that a lot of devs may not be familiar with, it is a big deal. It's not as widely known as Google, but I would imagine they have similar standards in terms of bringing on engineers and developer advocates and cloud engineers.
Definitely, definitely. And yeah, that's how like, I'm like, oh, I already do this in my personal time. Maybe it's time to test it out if I like it as a career, because I am someone who is passionate about teaching. I am ready to solve.
If I can make any devs live or any engineers life easier with my content, why not? So I think that the purpose was already there. The passion was there. It was just like the timing and the opportunity kind of like came at the right time and place. I was not happy at Google. So I'm like, okay, I'll try it out. And then I went through the interviews and
Yeah, I got the role and I'm like, okay, it's time to say bye to Google. So after four and a half months, I accepted an offer at Twilio and joined them as a developer advocate.
You know, that's great that you were able to kind of smoothly transition without like a long period of having to go back on the job market. So very smart of you. Like I always tell people like no matter how dissatisfied you are to job, unless you're literally being like abused by your manager or like losing sleep or over stressing or something like that.
Generally, you want to stay in that role. It's much easier to find a job if you have a job. Because employers don't have to be like, OK, so why don't you have a job currently? It just removes one little checkbox that they're going to have to investigate. So it's the saying about conventional wisdom from the 50s or 60s. Less contemporary time, obviously. But there was like,
Always married men who are always higher men who are married. Then you know that there's at least one person who could tolerate the bastards. Interesting. Of course, that was back from the gay man era. Like if you watch Mad Men, one of my favorite shows and stuff like that. But yeah, you were able to transition. You're a Twilio. Let's
We don't have to go too deep into what you do day-to-day, but I am kind of curious. Developer advocacy is kind of like a hybrid developer role and kind of a marketing role in the sense that you're getting out in front of people and you're showing them what the tools can do and you're inspiring people to pick up those APIs and start incorporating them into their own projects. I hope that's good.
No, I think that's a really good explanation. On a broader level, it comes down to that day-to-day gets trickier because it is different depending on different seasons. Why I say that is...
Fall is usually like conference season, summer and fall. So you'll see me going to a lot of conferences, giving talks about REPIs and our products. As you said, it's a mix between marketing. So I do kind of showcase how REPIs can be utilized to make your lives easier. As you said, if you're dealing with anything that's related to telephones,
like SMS voice or WhatsApp or even email. Yeah.
Yeah. Awesome. And so I want to get some context into like where you think things are going. Like you are working at one of the bigger tech companies and you've worked at arguably like the biggest or second biggest tech company. And then you've also worked at like small, like a small startup. They got acquired by a slightly larger company. Like you, you've had just in your, how many years has it been since, since you were working in the gas station? Like, since you finished your, your college diploma.
Um, seven, almost six, like almost seven years. It's been six years. Yeah. You've jammed a ton of experience into a pretty short period of time. What sort of things do you see changing and what are you most excited about in terms of cloud? In terms of cloud, I think, um, I want to take the discussion back to what you were mentioning. There are people
who are trying to not advocate, but say that like, oh, having your own server in like a facility makes more sense than just going the cloud route. And I think
Operational excellence is something that we are gonna see. People, not people like companies have realized that they have spent a lot of dollars on cloud, specifically when it comes to compute and storage. So they wanna see how they can minimize the cost, but also make sure that they're using all the resources that they have allocated within the cloud.
Um, so like if, if there is a VM, there's a scale of, or there's a group of like VM, so virtual machines within a specific cloud that a company is using, that they're going to make sure that all of them are at like at least 80 to 90% capacity instead of just being there at like, I don't know, 40 or 50%. So they're going to look for engineers, specifically cloud engineers who can help them.
achieve that kind of operational excellence. And that will come only if you have the skill set if you know how.
budgeting and costs within the cloud model works. Because cloud has different models. There is pay as you go. But if you look into like serverless and other stuff, they're like different architectures have different pricing models. So I think that's where the big shift is going to happen specifically within the small and medium businesses is that companies are going to be spending their money very
Carefully when it comes to cloud. I think 2015 to 2020 or 19 2020 was a time where every company was just pouring money into cloud. They like, you know, get these contracts. Let's move everything to cloud and
Well, like keeping the bills somehow. But now they're paying more attention and being more strategic about how they spend their resources. That is the first shift, I think, that's going to happen. Yeah, so essentially just being more mindful of how expensive it is to use cloud services. The second I already mentioned is
Every company is trying to get on the AI bandwagon and running all these AI either harsh language models or training your own models. As you said, all of this, not everyone has.
The resources are even the money to have those resources in their own data centers locations. So they're going to rely on a lot of these public cloud vendors to run those workloads. So if you can gain expertise in how these AI workloads can be run in the cloud on like, you know,
given infrastructure, like a specific kind of infrastructure with keeping the costs in mind in like a, you know.
optimal way. I think that is another area that is going to grow and a lot of the jobs are going to mention that as a skill set. Interesting. So at the same time that people are trying to go back to on premise or, you know, have the owning their own servers, this is a big movement in like a lot of smaller teams. Yes. We built our own servers like here it is. This is the machine that you're actually interfacing with and they'll take a picture and they'll tweet it and stuff like that.
Certainly for like build servers and things like that that don't need to be in the cloud that that can absolutely make sense This said there's there's a tension between like we don't want to be on the cloud We want to save money and we want to own our own hardware and all this stuff And then there's also the tension that we can't own our own hardware You can't own a quantum computer unless you are a multi-billion dollar company basically because they cost a fortune right you you can't Own like a cluster of GPUs because even if you have the money like it's
Like the production is so backed up right now that you would be in on a waiting list to be able to get, uh, you know, your H 100s and stuff like that. So, um, so I, it's interesting right now that there's that tension and there's that push in that pole. Um, are there any other big overarching mega trends to use a silly word, um, in the, um, in the cloud space right now that you've observed?
mega trends. Hmm. Are there any tools? Let's shift the tools. Are there any tools that are having a moment? I think a lot of it's not something that
is trending right now. I think it's been a few years, but the automation, and we saw that with the DevOps kind of like roles, but also it shifted to like platform engineering, you know, tools like Backstage, like having internal developer like portals and stuff for managing infrastructure. I think a lot of more companies are investing in that.
Again, this comes from that comment about operational excellence like the companies want to be mindful on how they are using all of these resources within the cloud. So I think that it kind of like ties in together where we are headed with the trends.
And we also saw a lot of shift into traditional setup of using VMs to more of containerized environments and use of Kubernetes, even if it is Kubernetes, but also managed container services like AWS has ECS.
Yeah, last container service. So containers are also something that are going to be trending specifically with the AI use case. So not just, you know, ordering your compute power by getting.
GPUs from NVIDIA and then some kind of compute from Dell or other vendors. But how you can, even if it's on-prem or cloud doesn't matter, but how you can leverage more of like a containerized environment for different workloads for that optimal use of the money that has been spent on the infrastructure.
Yeah, and a lot of DevOps in cloud engineering really does come down to figuring out a budget and like figuring out how to make things work within that budget or figuring out clever ways to automate your way to a reduced budget or making more crafty use of a resource like serverless is a pretty big innovation in that.
It's been around for like 10 years, but basically, uh, Amazon Lambda, like where you can just run like functions in the cloud instead of having servers standing by, you can just, yeah, and you can have things done incredibly inexpensively unless you're doing those at a vast scale. So it's like, I think you get like thousands of free Lambda. Oh, yeah, I think, yeah.
the last I remember it was a million a million a month per month in vocations and that's like a lot of my stuff specifically for APIs and like event driven stuff is running on Lambda or functions as service Microsoft has Azure functions GCP has Google Cloud functions
But it boils down to the use case. So if there is a use case for you using serverless, you should definitely leverage it because it's such a cost effective method. And a lot of the management of infrastructure is abstracted away. You just give them your code and it runs it whenever you want.
Yeah, yeah, absolutely. Awesome. So let's say, hypothetically, you are starting out, you're looking back, everything you know about cloud competing, and maybe you're just going to completely skip the diploma you got, the technical college where you went, community college, where you studied like networking and databases, and those kind of more nuts and bolts type skills. Let's say, hypothetically, you had zero formal school.
What would you do if you wanted to get where you are today and you want to get there as quickly as possible and you Ideally didn't want to spend money To actually earn these certifications like to take this certification exam might be like 200 bucks for per certification exam So we're gonna treat it like those certifications you have money to pay for those But you don't want to spend a bunch of money on anything else or or maybe you have a minimal budget like you know $200 a month or something for your training or less than that
No, for sure. I think that $200 per month, I'm going to use that for your cloud builds. So what I mean by cloud builds is I want I would create like AWS or Azure account and then start building stuff. This would be a later part of the process, but since you have given me that $200, I think that's where it will be most used is just spinning stuff up in the in given cloud provider and then.
because it's going to cost money once you run out of free tier services, that is where it's going to go. And I think you can literally do it by even within, like, you can have a good project running in cloud for less than $20 a month, even if it's like it involves multiple services at a personal level, because you're not going to get as big of a traffic
As some of these enterprise companies get but I would start if I was gonna start from zero where I have zero context This I was gonna learn some of the ID fundamentals on how
like networking works, so like how internet works, first of all, DNS, how packets transfer, how computers communicate to each other, because at the end of the day, all these servers within the cloud, they use networking to talk to each other. The second skill I would really spend my time is on how Linux works, because I think there was a
I saw this photograph somewhere. I think it was Twitter.
I don't know, 80% of servers on the internet are Linux or something like that. I mean, at least 80%. Yeah, because people don't want to have to pay like a license. Like, you know, Microsoft, I'm not sure, like NT, I'm not even sure what options there are on Linux. Yeah, every server free code campus every year used, we probably deployed thousands of servers and spun them down over the years. We have more than 100 servers in operators right now.
Every single server has been I believe like Ubuntu. Yeah, because that's just like a widely available image and it's battle tested and yeah, and so Ubuntu is a specific variant of Linux that has just become Particularly popular is based on Debian which is another distro, but like they added a bunch of additional stuff and
And it doesn't really matter that much, but you can definitely geek out and choose a very specific flavor of Linux that you like if it's more security focused or more performance focused or something like that. But yes, I will quickly second the notion that you should learn Linux if you want to work as a cloud engineer, because every cloud engineer I know basically is doing stuff in Linux all day long. Definitely. Definitely.
And I think, yeah, when you look back, once you become a Cloud Engineer, you'll tank yourself if you have those Linux skills. I don't even know if it is possible in today's time to land a Cloud Engineer role without the Linux skills. But yes, that would be my second skill. The third, I want to focus a bit more on at least having one programming language under your belt.
I highly recommend Python because if you're new, it's very easy to understand. There is a great community behind Python. There are ample of resources available online. There are communities that you can join to get yourself skilled in Python and get it to a point where you can do scripting in Python because a lot of Cloud and DevOps engineers do scripting for automation and stuff.
That's when I'll start pivoting towards learning a cloud provider. So pick, I think the greatest advice I've given is see the market that
see the market in your city. So if you're in Toronto, look at the job listings of the cloud engineers and watch cloud provider is being mentioned the most. If AWS is more popular, then Azure in your area, go with that provider if you don't already have made the decision.
So pick one provider, go through like the foundational certification. You don't have to set the exam. The reason why I say go through the certification is because they have built a good roadmap of what you should learn first, what services you should learn like in a good roadmap. So if they give you a structure and I think you should follow that.
Then after you've done the foundational level, go for the associate level, um, certification, just prepare for it. Don't like send the exam if money is a problem. I have to sit the exam, but when you're, when it comes to actually applying for jobs, it is, would you say it's good to have the actual exam? Like, do you think the certification is worth actually earning? Definitely. I think, I think having at least, um,
I would skip like if money is really a problem, I would skip the practitioner have at least one associate level. So that would be like solutions architect for.
AWS is E104 for Azure and GCP is associated cloud engineer. So depending on what cloud provider you pick, like go with at least this certification. If you want to increase your chances, I think it helps to a certain extent. Again, like having it on the resume will help, but.
What do you say actually in the interview again, you know, it all comes down to that. So just having the paper doesn't matter like, like have the knowledge underneath that certification.
Awesome. So I want to I want to break all that down because you've covered three very important things. I've been taking detailed notes. So first thing that you recommend anybody who wants to become a cloud engineer, regardless of your background, learn networking, learn fundamentally how computers communicate with one another because that's what the cloud is. A whole bunch of computers communicating with another. Second one, learn Linux pretty well. The third one, learn at least one high level scripting language.
Python seems to be an excellent one. I strongly encourage everybody to learn Python. If it's, you know, JavaScript is arguably like easier to learn just because it's a little bit more visual than you can do as part of web dev, but there's no harm in just diving into Python and frequently it has a ton of resources on learning Python. And Python is, in my humble opinion, one of the easier languages to learn. It's arguably like the easiest major programming language that's in wide use to pick up because it has like lots of different features that kind of force you into
coding right. Whereas JavaScript, you can just code whatever you want and it can be a completely ball of spaghetti and it can still work. But, you know, Python kind of, it has patterns that push you toward actually like learning how to do things right. So those would be the big three things, anything else that you would strongly recommend people do. Oh, and the three certifications that you recommended based on your
cloud of choice, which they are very comparable functionally and how they work. They have different services names. They have probably different little quirks between them. But you can skip the first certification that's usually less technical and you go for one of the associates. Yes. And that way, you know, a single associate certification. Like if you have that, they probably assume you know everything from the more junior certification, right?
Definitely, yeah. Yeah, I think the, the only thing I would add is some kind of DevOps practices into it. So like think of Terraform. So Terraform does infrastructure as code. Um, you know, any of the companies you apply for, they'll have some kind of automation. Nobody goes through the portal and click through, uh, deploying an easy to instance, when there are hundreds like in free code camps, example, like if you want to deploy a hundred,
VMs, you're not going to do it 100 times through a console. So learn all these cloud providers have their own CLI or a command line. So either you can start diving into that. And also on top of that, I think Terraform is a great example for infrastructure as code because it's cloud agnostic. So it doesn't matter which cloud provider you work with, you can write Terraform code to deploy your infrastructure in any of these cloud providers. So any kind of automation
in respect to the DevOps practices, I would say, so Terraform and command line for that Cloud provider and GitHub actions. Since you will be building a project, I highly recommend it to have it in a GitHub repository or GitLab repository so that you can share it with your employer, like when you're applying for jobs, make sure it's well-documented.
automation is only good when you can deploy stuff automatically when changes happen in your code repository. That's where GitHub actions come in. So like start diving into how you can apply multiple, like if you want to do, you can build a end-to-end project, but how you can apply these DevOps practices into your cloud project, I think would be like a cherry on top and would really make you ready for like an actual job at a company.
All of this is a roadmap on our Learn to Cloud. So Learn to Cloud is an open source guide or platform where you can learn Cloud. It's free. It was built by my friend who works at Microsoft and me because we have had this self-taught kind of journey into the Cloud. So we kind of saw like,
All of this was kind of missing in our journey. So let's create a resource that helps people get into cloud, basically. So all of the technologies that I mentioned from networking, Linux, scripting language, Python, and even DevOps towards the end. All of this is kind of covered there. So I highly recommend it to check it out. It's learntocloud.guide. It's a web app that you can
Access. Awesome. I'm linking to that in the show notes. Well, Reshop, I think it's awesome. Everything you've shared with everybody here. I love that you have this amazing origin story that you are proof that you don't need to get a four-year degree to potentially work as a DevOps, as a cloud engineer, as a developer advocate, and that you can just go the certification route and that you can
Not necessarily have to constantly change jobs or shop around for jobs, but actually find opportunities within your own current company. I love to see people do that and take advantage of any sort of lifeline from above like mentorship, anything that they can get.
I think it's a testament to how scrappy you are and how resourceful you are. And I also really appreciate you sharing like all that really actionable advice on how to get into tech. I'm going to encourage everybody to check out Rishob's courses that we published on Freeco Camp. Check out his YouTube channel. Check out his Learn to Cloud website, which is awesome. It covers Linux, Bash,
programming, cloud platform fundamentals, DevOps fundamentals, cloud security, very important topic. So yeah, man, just thank you so much for being such a sharing person. Like a lot of people are probably in a similar boat and they've gotten to where you are in their career and they don't necessarily take the time to help other people get to where they are. You know, it's easy to just relax and enjoy your knowledge, work or lifestyle with your interesting work and your high income and all these things. But you,
take the time to share that wisdom and to make sure that other people have a nice clear path forward and you help reduce the ambiguity. Is there any advice you would send back in time to yourself? If you were sitting in that gas station for a long day, like looking at that money that you've been making, which is enough to provide for yourself, and it's easy to just imagine like an alternate timeline where Rishab is, you know, seven years later, you're still in that gas station. What advice would you send back to yourself?
Hmm, I think I would probably say that
keep dreaming big, but also just like don't forget your dreams. So like, I remember me being a teenager and like, what all dreams I had, like just don't don't forget like what you have pictured for yourself in life, even when life gets comfortable. So that is the only advice I think I would give myself. And also like,
Things are going to happen at their own pace, like just be consistent with like whatever I was trying to do at that time. So if it's learning a new skill, just like be consistent, like showing up every day or whatever cadence you have built. But yeah, so remember your dreams and then being consistent. Awesome. Well, thank you again so much for making time to come on the free code camp podcast.
No, thank you. Thank you for creating, you know, this platform, um, not only for like teaching and stuff, but also having so many amazing people can share their story and, you know, kind of inspire and give road maps to other. Thank you. Awesome. Thanks for your shop. Everybody still tuning in until next week. Happy coding.
Was this transcript helpful?
Recent Episodes
#159 From freeCodeCamp to CTO with Robotics Engineer Peggy Wang

freeCodeCamp Podcast
On this week's episode of the podcast, freeCodeCamp founder Quincy Larson interviews Peggy Wang. She used freeCodeCamp to learn coding. She then worked in Big Tech as a robotics engineer. And now she's cofounder and CTO of Ego AI, a Y-Combinator-backed startup that builds human-like agents for video games. We talk about: - How she grew up a first generation American and public school kid in Milwaukee - How her love of robotics helped her get into Stanford - How freeCodeCamp served as a key resource to build her developer chops - The near future of humanoid robots, self-driving cars, and human-like AI agents in games Support for this podcast comes from a grant from Wix Studio. Wix Studio provides developers tools to rapidly build websites with everything out-of-the-box, then extend, replace, and break boundaries with code. Learn more at https://wixstudio.com. Support also comes from the 11,224 kind folks who support freeCodeCamp through a monthly donation. Join these kind folks and help our mission by going to https://www.freecodecamp.org/donate Links we talk about during our conversation: - Peggy's GameDev company, Ego AI: https://www.egoai.com/ - Quincy's interview with hardware engineer Bruno Haid that he mentions toward the end of this episode: https://www.freecodecamp.org/news/podcast-hardware-engineering-bruno-haid/
February 07, 2025
#157 Getting a developer job in 2025 with Lane Wagner

freeCodeCamp Podcast
Quincy Larson interviews Lane Wagner, a software engineer and founder of Boot.dev, discussing his views on college education, enthusiasm for Go, insights about learning strategies, and the scarcity of US engineering graduates compared to India and China. Lane shares resources like a 4-hour course on getting a developer job, an HTTP Networking course, SQL for Web Developers course, and freely available books published through freeCodeCamp Press.
January 25, 2025
#156 AI Reality VS Speculation with Google Machine Learning Engineer Jiquan Ngiam

freeCodeCamp Podcast
Quincy Larson interviews Jiquan Ngiam, a Google Brain former engineer, who discusses AI practical applications, its future, and how non-developers/developers can leverage it. Topics include AI agent functionality, AI's limitations, generative agentic interfaces for large spreadsheets, OODA loops for AI agents, and the Executable Code Actions paper.
January 17, 2025
#155 CUDA and GPU Programming with Elliot Arledge

freeCodeCamp Podcast
20-year old computer science student Elliot Arledge discusses his creation of popular freeCodeCamp courses on LLMs, Mojo programming language, and GPU programming with CUDA; shares insights on building AI systems, rapid learning methods, reading academic papers, and college coursework vs self-directed learning.
January 10, 2025

Ask this episodeAI Anything

Hi! You're chatting with freeCodeCamp Podcast AI.
I can answer your questions from this episode and play episode clips relevant to your question.
You can ask a direct question or get started with below questions -
What was the main topic of the podcast episode?
Summarise the key points discussed in the episode?
Were there any notable quotes or insights from the speakers?
Which popular books were mentioned in this episode?
Were there any points particularly controversial or thought-provoking discussed in the episode?
Were any current events or trending topics addressed in the episode?
Sign In to save message history