Hello Reader, In today's post, let's look at a correct but average answer and a great answer that gets you hired to common cloud interview questions. This should give you pointers on how to improve your interview answers. Also Lambda turned 10 years, should you still learn it? We got a packed newsletter, let's get started. Interview question - Can you tell me about a microservice you have designed on AWS? Common but average answer - I will use ALB with EC2 with Auto Scaling Group, ALB with EKS, or API Gateway with Lambda. Why is it average - What the interviewer is looking for is how the microservice design works. Even a monolith can be run using ALB with EC2 with ASG, ALB with EKS etc. Just saying those doesn’t mean it’s a microservice design. You need to highlight microservice characteristics in the design. Sample good answer - There are many ways to implement a microservice, but the most common pattern is the one below, with Application Load Balancer (ALB). Then explain the core concepts:
If you get this question in your interview, make sure to knock it out of the park! Now, let's introspect Lambda's Big Birthday. Lambda turned 10 years 🍰When AWS Lambda was announced in 2014, it created lot of buzz. But where are we now, after 10 years. As always, we take a pragmatic look to maximize your preparation for SA interview and real-world projects. Just for reference, I have been working with Serverless for a very long time, since 2016. I deployed a Serverless application in production at a large enterprise company, Verizon. Whatever I am sharing is based on my actual experience and from working with actual customers, and not just theory crafting.
I want to end this newsletter with some fun memories. After I deployed a Lambda application in Prod in 2017, my talk was selected for a conference in San Francisco. This was my very first conference talk! I became so passionate about Lambda, that I created a Serverless course on 2018, and also put a Lambda light on my home office wall! It's still shines brightly today and present on my videos and customer calls. Here's to next 10 years of AWS Lambda 🙌🚀 If you have found this newsletter helpful, and want to support me 🙏: Checkout my bestselling courses on AWS, System Design, Kubernetes, DevOps, and more: Max discounted links AWS SA Bootcamp with Live Classes, Mock Interviews, Hands-On, Resume Improvement and more: https://www.sabootcamp.com/
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 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 experience Your 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...
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...