Part 1/4 - From a restaurant business owner to an AWS TAM role
How Amir upskilled from a non-IT background on AWS
Hey, Prasad here 👋 I'm the voice behind the weekly newsletter "Big Tech Careers."
Most people think that career at MAANG+/Big Tech is out of reach for them. Certainly, I was one of them until I got a break and cleared the interview process. I want to change that perspective and that’s one of the reason I started writing this newsletter and created the Big Interview Preparation Workshop.
Two of my Big Tech Interview Preparation Workshop participants cleared AWS interviews recently. One of the participants, Amir Malaeb, transitioned from restaurant business owner to Technical Account Manager at AWS. In the next 4 articles, Amir Malaeb will share in his own words, his journey of upskilling on AWS and how he cleared AWS interview process. Hope his story inspires you to achieve your dreams.
If you like the article, click the ❤️ icon. That helps me know you enjoy reading my content.
Over to you Amir!
Introduction: A Leap into the Unknown
If someone had told me in early 2024 that I would transition from running a restaurant to becoming a Cloud Technical Account Manager at AWS, I would have found it hard to believe. Yet here I am, living proof that it’s never too late to reinvent yourself and pursue your passions. My journey into the cloud world wasn’t conventional—it was filled with 80-hour workweeks, juggling a newborn at home, and navigating a steep learning curve. But it’s also a testament to the power of determination and the support of a great community.
Why Cloud Engineering?
The shift to cloud computing wasn’t random; it was driven by my fascination with technology’s transformative potential. In the restaurant, I implemented technology-driven solutions like digital menus and surveillance systems to improve efficiency and reduce costs. These small steps sparked a curiosity that grew into a passion. I wanted to explore how technology—particularly the cloud—could solve complex problems at scale.
AWS stood out as the platform that would allow me to blend creativity, innovation, and impact. In February 2024, I decided to take the plunge and commit to transitioning into cloud engineering. It wasn’t an easy decision, especially given my responsibilities as a business owner and a new father, but I knew this was a challenge worth taking on.
The Intense Balancing Act
The early months of my transition were some of the most challenging in my life. Between managing a restaurant, raising a newborn with my wife, and working 80-hour weeks, I added another layer of complexity: learning cloud computing and machine learning. Every day was a test of endurance and focus.
I quickly realized that success would require meticulous planning and unwavering commitment. I set a strict schedule, dedicating specific hours each day to study, even if it meant sacrificing personal downtime. For eight straight months, I didn’t take a single day off from studying. Whether it was early mornings, late nights, or brief moments of quiet during the day, I made sure to prioritize learning, treating it with the same importance as my other responsibilities.
The reality of my transition was intense and measured in hours, sweat, and dedication:
6 hours of daily focused study for 8 consecutive months, often extending to 10 hours on weekends
40+ end-to-end cloud native projects completed, ranging from simple S3 static websites to complex containerized applications
120 to 130-hour workweeks split between restaurant management and cloud learning
0 days missed in my study routine, even during restaurant emergencies or sleepless nights with my newborn
This wasn't just about putting in the hours—it was about maximizing every minute. During quiet periods at the restaurant, I'd review AWS documentation. While my newborn slept, I'd work on infrastructure-as-code projects. Every spare moment became an opportunity to learn, practice, and grow.
To gain a foundational understanding, I enrolled in the Digital Cloud Training Bootcamp with Neal Davis. This program provided the structured learning I needed to navigate AWS concepts. At the same time, I was participating in the Data Science and Machine Learning program with MIT, which deepened my knowledge of AI and ML while enhancing my analytical skills.
Balancing all these priorities wasn’t easy—it meant missing out on leisure activities and navigating the exhaustion of long days. But the disciplined routine and clear focus on my goals kept me going. This intense commitment to self-improvement eventually paid off, not just in certifications and skills but also in the confidence that I could thrive under pressure.
Building Knowledge and Gaining Skills
My AWS learning journey began with the AWS Certified Cloud Practitioner, a foundational certification that provided a clear roadmap and built my confidence for more advanced challenges. Leveraging the structured guidance of Digital Cloud Training (DCT), I began with Linux fundamentals and gradually advanced to cloud concepts and topics like networking, security, and automation. This step-by-step approach ensured a solid foundation, allowing me to grasp complex concepts more effectively as I progressed.
However, I didn’t limit myself to formal training. I actively explored resources like AWS SkillBuilder, interactive workshops, and hands-on exercises from various online platforms. I treated each project as an opportunity to learn and grow, even when it meant breaking things and troubleshooting until I found a solution. This hands-on experimentation reinforced my technical skills and gave me the confidence to tackle real-world scenarios.
As I gained confidence, I began working on real-world projects, including 3-tier web architectures, to deepen my understanding of AWS services such as networking, compute, and storage. Through these projects, I learned to think like a Solutions Architect, considering scalability, fault tolerance, and cost optimization. Along the way, I also explored tools for diagram creation and infrastructure visualization to make my designs more professional and accessible. While these early projects now seem simple compared to what I can achieve today, they were critical stepping stones in my journey.
A key lesson I embraced was the importance of documenting and celebrating progress, no matter how small. My early LinkedIn posts, often showcasing these projects, initially reached only a handful of people. Over time, as I refined my storytelling and consistently shared updates, I saw my reach grow significantly—some posts now exceed 30,000 impressions. This process helped me create a personal brand that not only highlighted my skills but also inspired others to start their own learning journeys.
Throughout this process, I embraced tools like Generative AI to craft compelling LinkedIn posts, share insights, and celebrate achievements. In just nine months, my LinkedIn profile grew to over 3,000 followers, capturing the attention of potential employers and demonstrating the value of visibility in today’s tech landscape.
This learning phase taught me the importance of persistence, going beyond my comfort zone, and treating every challenge as an opportunity to grow. By combining structured learning with personal exploration, I developed a foundation that continues to drive my passion for cloud computing and innovation.
Joining a Supportive Community
Transitioning to cloud engineering wasn’t a solo journey—it was enriched by the communities and connections I built along the way. Early on, I understood the value of surrounding myself with like-minded individuals who shared the same passion for growth. Whether through LinkedIn, Slack channels, Discord servers, or WhatsApp groups, I actively sought out platforms where I could exchange ideas, seek guidance, and stay motivated.
One of the most transformative connections I made was with Neal Davis and the DCT community. Neal’s structured approach to cloud learning and his consistent encouragement were pivotal in my growth. His support went beyond providing resources—he amplified my journey by sharing my LinkedIn posts and introducing me to a broader network of professionals. This recognition not only validated my efforts but also connected me to opportunities that further accelerated my progress.
I also made it a point to actively contribute to these communities, engaging in discussions, offering solutions, and celebrating the successes of others. This participation reminded me that learning isn’t just an individual pursuit—it’s a collective effort that thrives on collaboration.
One of the most memorable moments in my journey was reaching out to Prasad Rao, a Principal Solutions Architect at AWS, to ask if he’d be open to being tagged in my posts to help amplify my reach. His supportive response reinforced the idea that asking for help can lead to unexpected opportunities. Similarly, attending KubeCon allowed me to connect with experts like James Spurin and Michael Levan, whose insights and encouragement further fueled my motivation. These experiences underscored the importance of building relationships and seeking guidance from those who have already walked the path.
Sharing my journey wasn’t just about personal growth—it was about inspiring others. By documenting my progress and openly discussing my challenges, I contributed to the community while learning from it. Cloud-focused groups on platforms like Slack and Discord became invaluable for real-time support, resource sharing, and fostering a sense of camaraderie.
Diving into Personal Projects and Innovation
One of the most transformative aspects of my cloud journey was the hands-on experience gained through personal projects. These projects weren’t just a way to learn—they were a playground for innovation and creativity, providing real-world challenges that honed my technical skills and prepared me for larger responsibilities.
The Value of Every Project
I’ve come to believe that no project is too small to matter. My journey began with simple experiments—like hosting a static website on Amazon S3—where I learned core fundamentals like storage, permissions, and content delivery. While these seemed minor at the time, they built confidence and a deeper understanding of cloud technologies.
The key is documenting and celebrating every step, no matter how small. Early on, I made a habit of sharing my progress on LinkedIn, even when working on basic tasks like configuring a bucket policy or setting up CloudFront. What started as small wins eventually became a portfolio of accomplishments, reflecting my steady growth.
Embracing Innovation: The NBA Stats App
As my cloud skills evolved, I wanted to push beyond structured learning and apply my knowledge in a real-world use case. As an NBA fan, I was frustrated by how cluttered most sports apps were with ads and unnecessary features. I just wanted a clean, distraction-free way to check player stats.
At the same time, I was learning Kubernetes and wanted to go beyond my study requirements. This app became the perfect opportunity to merge my personal passion with technical learning, reinforcing cloud-native concepts in an engaging, meaningful way.
I built the app using Streamlit and deployed it on Kubernetes with Minikube, integrating cloud-native features like:
Dynamic Configuration: Used Kubernetes ConfigMaps to allow customization without modifying the code.
Scalability: Designed the app with Horizontal Pod Autoscaling (HPA) to handle fluctuating traffic.
Monitoring & Optimization: Implemented Prometheus and Grafana to track CPU, memory, and system performance.
While I’ve worked on many projects, I highlight this one because it embodies the importance of curiosity and execution. Great ideas often come from everyday frustrations, and the best way to solidify learning is by building real things. Sharing this project on LinkedIn led to insightful conversations and proved that when you take the initiative, opportunities follow.
Building Confidence Through Projects
Projects like 3-tier web applications, NBA Stats App, AI-powered image description generator, and many more that you can find on my LinkedIn profile weren’t just about gaining technical skills—they were about building confidence in my ability to solve real-world problems. Each project became a tangible proof of progress, shaping my journey and serving as a portfolio to showcase my growth.
Through this process, I realized that innovation doesn’t require massive resources—it requires curiosity, dedication, and a willingness to learn. Each project—whether a simple static website or a complex cloud-native app—was a step toward becoming a cloud professional. And each lesson learned became a foundation for future success.
Overcoming Doubts and Imposter Syndrome
Despite my structured approach and unwavering commitment, there were moments of self-doubt. Transitioning into an entirely new field, especially after over 15 years in business, came with its challenges. I often questioned whether I had started too late or whether I could keep up with the fast-paced world of cloud computing.
The turning point came when I shared my progress publicly. Seeing others resonate with my journey and hearing their stories of persistence reminded me that I wasn’t alone. Everyone faces challenges, but what matters is how you navigate them. Each time I completed a project, passed a certification, or received positive feedback from my posts, I silenced the voice of imposter syndrome a little more.
Reflecting on this chapter of my journey, I’ve learned that growth is rarely linear—it’s a series of small steps, each contributing to a bigger transformation. Overcoming challenges, documenting progress, and building a supportive network proved invaluable as I navigated this transition. This experience taught me that it’s never too late to reinvent yourself, as long as you’re willing to put in the work and stay curious.
In the next part of this series, I’ll dive into how these efforts translated into tangible opportunities, from crafting a standout resume to preparing for technical assessments. Stay tuned for insights, lessons, and actionable tips for taking the next steps in your cloud journey!
Key Takeaways for Aspiring Cloud Engineers
1. Start Simple: Don’t underestimate the value of starting small. Even a static website can teach you the basics of storage, security, and scalability.
2. Document Everything: Every project, no matter how simple, is a stepping stone. Documenting your journey not only helps you track your progress but also inspires others.
3. Embrace Challenges: Take on projects that push you outside your comfort zone. Break things, fix them, and learn from the process.
4. Innovate Boldly: Use projects as a platform to experiment with new technologies. Whether it’s AI, containerization, or serverless computing, let your curiosity guide you.
5. Share Your Journey: Sharing your work publicly creates opportunities for feedback, connections, and growth.
I would like to extend a big thank you to Amir for sharing his journey with Big Tech Careers readers. Stay tuned for the upcoming three parts where he will be sharing following:
Part 2/4: How to get resume shortlisted and clear online assessments
Part 3/4: How to prepare and clear AWS technical phone screen
Part 4/4: How to prepare and clear AWS Loop interview
I also encourage you to follow Amir on LinkedIn for further insights.
Great article very informative and inspirational.