Hello Reader, In today's newsletter, I am going to share three tips that helped me and many of my students switch careers to the cloud and get high-paying jobs. I will also share an update about the upcoming Sep cohort of the AWS SA Bootcamp. Tip 1: Leverage your IT experienceYour existing IT experience is NOT throwaway. Don't think you can't reuse components of your existing knowledge in your cloud journey. For example, my mentee and SA Bootcamper Rukmani, came from software engineering background without any SA experience. She showcased how to develop, test, and deploy his code on the cloud. And after she learned the associated AWS components for interviews, she was able to get into AWS as a Solutions Architect with a significant salary hike. Another bootcamper, Abhisekh has deep knowledge of the telecom domain. He associated his cloud knowledge with telecom use cases. He learned how other telecom companies use AWS, learned the related concepts, and started augmenting his existing knowledge with AWS learnings. And soon, he got a telecom cloud architect position. In my case, I worked with SQL databases and COBOL on the mainframe for 10+ years. I learned what SQL databases are available on AWS, the differences between them and DB2 (Mainframe SQL database), how to migrate data, etc. To my surprise, the approach to cost-optimizing DB2 is the same as that of RDS: check utilization, adjust underlying VM sizes, tune queries, and some additional AWS concepts. In the same way, I learned how we can modernize legacy workflows to Step Functions and did projects on that. Because I am not showing these use cases in a vacuum, instead building on top of my existing expertise, it's more appealing to recruiters, and I can handle interview questions better. If you are currently a tech lead who has to influence many team members in a certain direction, you can leverage it for Solutions Architect roles. I have many such examples from my SA bootcamp, where candidates used their existing experience to switch careers to the cloud. Tip 2: "Delight" recruiters and interviewersA lot of you reached out to me and said that recruiters are not picking you. You’ve given multiple interviews, but you’re failing. This is where many strong technical candidates stumble. They think they answered the question. After the rejection, they believe the interviewer just did not like them. I used to believe that too, until I started sitting in the debrief sessions after interviews, and I saw the real reason candidates were rejected. SA bootcamper, Anuj, was in this boat. He gave multiple interviews, and he answered the questions right, but he repeatedly got rejected, before joining the bootcamp. You have to delight the recruiter and interviewer and not just meet. Giving “just the right answer” or average answer is not enough. What it comes down to is that there is so much competition in the market. You have to set yourself apart at every stage. You work hard, and you do a lot of projects, but being good is not enough! You have to prove you’re good to the recruiter and interviewer. How do you do that? Think about how you can set yourself apart. For example, instead of saying, “I have done cost optimization on AWS,” which is too generic, say, “I saved over 30% in costs quarterly using tools like Compute Optimizer, spot instances, and reserved instances.” Similarly, for a question like, “Can you tell me about a microservice you’ve designed on AWS?” avoid generic responses like “I used an application load balancer with EC2 auto-scaling.” A better answer could be: “I designed a microservices system with Route 53 directing traffic to a load balancer, using path-based routing to independent, scalable microservices. Each microservice used different technologies and scaling criteria, ensuring flexibility and minimal interdependencies.” Ohh and Anuj, he just cracked a Senior VP role at JP Morgan Chase with 60% hike, after finishing my bootcamp. Yep, you heard that right. Tip 3: Be focused on a pathIn 2021, my friend told me that if I invested in crypto, I'd make money, so I bought a bunch of altcoins. Another friend told me to learn day trading. Another told me that real estate is the only way to become rich. I tried them all at the same time, and nothing worked out. We saw above that to get a job, you need to delight the interviewer. And to delight, you have to go beyond surface-level answers. There are so many people with surface-level knowledge on the market; anyone focusing on one thing is beating the folks trying different things. Pick a path based on your interests, and which augments your existing experience. True story - 10 years back I read hedge fund quants make lot of money, so I tried to become one, and that was wasted 6 months because neither I like advanced ML, nor I was deep enough to crack quant interviews. A person with a passion for a specific domain will always beat someone who is studying different things. When Yinon came to my bootcamp, he had his hands in everything in the fear of FOMO - Gen AI, analytics, data engineering, ML, SRE, AWS. As a result, he succeeded in none. And after Yinon focused on one guided structured path in Bootcamp, he got into one of the hottest companies right now, Databricks. SA BootCamp UpdateI run SA Bootcamp with Live Classes covering Technical, Behavioral, Mock Interviews, 1:1, Hands-On, LinkedIn/Resume Improvement, latest Gen AI topics, and more. Past students got high paying jobs including at AWS, Microsoft, Google, Databricks, JPMC, Reddit and more.
Keep learning and keep rocking 🚀, Raj |
Free Cloud Interview Guide to crush your next interview. Plus, real-world answers for cloud interviews, and system design from a top Solutions Architect at AWS.
Hello Reader, I have been a Cloud Solutions Architect for 10 years - 4 years at Verizon, 6.5 years at AWS. I was an Application Cloud Architect at Verizon, and then I joined AWS, where I had two different SA roles - first a General SA (Enterprise Architect) and then a Specialist SA. In this post, I will review my responsibilities as an SA in all these companies, including the hardest parts of the job (in my humble opinion). Let's get started: Solutions Architect at Verizon I became a SA at...
Hello Reader, In today’s post, let’s look at another correct but average answer and a great answer that gets you hired for common cloud interview questions. And this ties to a larger thread - most candidates fail their Solutions Architect interviews - not because they’re underqualified… But because they don’t know how to communicate like a Solutions Architect. How to stand out as a must-hire? Let's start with a common question, and we will go from there! Question - What's the difference...
Hello Reader, Not all questions are equal in interviews and real-world projects. There are some questions that you simply can't mess up, because these concepts are so fundamental, they are used in almost ALL projects. One such concept is high availability. Surprisingly, I hear wrong answers on this all the time. In this edition, let's go over the common bad answers, a good answer, and then some! Question: What is High Availability? Bad Answers Even if a component fails, application should...