Back to Home
career

Unlocking the Architect: A Journey of Compounding Effort

June 10, 2026

2019: The Loop of Silence

My journey didn't start with a clear roadmap or a series of wins. Looking back, 2019 was a brutal year. I spent months in a job search that felt like a loop of silence and rejection. It was a period of deep uncertainty, the kind where it feels like the goalposts are moving further away every time you take a step forward.


I threw myself into various courses, hoping for a spark that would change my trajectory, but the results remained the same. I felt stuck.


In a final attempt to find a way in, I attended a job fair, hoping to land an apprenticeship or a role in ICT or media. That’s where I first encountered the Prince's Trust, now known as The King's Trust. At the time, it felt like just another application, but in hindsight, it was the first real turning point.


Around the same time, I discovered Amazon re:Start. I’ve always loved computers, using them, building them, and breaking them, so it felt like a natural fit. However, my first attempt to get in was a failure. It was a hit to my confidence and a reminder of the "no's" I had been hearing all year.


Instead of giving up, I started the "Grow Your Skills and Confidence" program with the Trust in September. I didn't realize it then, but this was where the real work began. It wasn't just about technical skills; it was about realizing that I was capable of far more than I had given myself credit for.


Through the activities and the people I met, I slowly began to open up. I've never been the most social person in the room, but I learned a vital lesson: that showing a genuine interest in others is the fastest way to grow as a person.


2020: The path forward

By January and February, something had shifted. After giving a speech about my own growth, I felt a spark of hope return. I knew I wanted to move forward, and that's when I remembered AWS re:Start.

When I discovered there was an upcoming event, I dove into preparation. I didn't want to leave this to chance; I was determined to secure a spot on the course. I even had a backup plan, applying to university for ICT, but my heart was set on this opportunity.

When the news finally arrived that I had been accepted, a wave of relief washed over me. For the first time in a long while, I felt like I was actually making progress. I knew this was my moment, and I vowed to put everything I had into the course, taking every lesson I had learned from The King's Trust and applying it to this new chapter.


2020: A time of knowledge

During my time at Amazon re:Start, I focused entirely on learning. I wanted to get a real understanding of the field, and I pushed myself to get out of my comfort zone by attending user events. Looking back, it was lucky timing because I managed to get out there and connect with people just before the world shut down.


When lockdown happened, my life became very small. Outside of a one-hour daily walk and the occasional trip to the store, I was devoted to my studies. I heard stories about people spending their days watching Netflix or playing games to pass the time, and while I did play a few games in the evening or went on my walks to clear my head, my main focus was the work.


For the short time we had on the course, it was incredibly impactful. It wasn't just the technical side of things; the advice I received from my mentor during that time is something I still apply to my life today, and it's advice I now share with others. I realized that while the world had paused, I was using that time to build something for myself.


2020: A new path after the course

All good things must come to an end, and so did the course. As we said our goodbyes and went our separate ways, I was left with a question: "What next?"


I began reading and putting together a website. At the time, I was proud of it and really happy with the result. I remember wanting the colors to change because I wanted it to stand out; looking back now, I can see that it was a UX nightmare.


I poured my energy into my portfolio and switched to Linux for most of my time, only using Windows for multiplayer games. I leaned into the lockdown; instead of taking long breaks, I used my walks to clear my head, but 90% of my time was spent focusing on landing a job.


During the rest of the summer, my efforts began to manifest. I became a case study for the King's Trust and was featured on BBC Manchester radio. I am still proud of both events because they were proof that my efforts were paying off.


2020: New Horizons

On October 5, 2020, I started at ANS Group as an apprentice. Looking back, I remember thinking I had bombed the interview, but I got the role anyway.


As an apprentice, I wore many hats. I handled on-prem tickets, worked a bit with WAN, and focused heavily on Cloud tickets across Azure and AWS. Whenever I encountered something I didn't know, I would find someone with the answer, ask questions, and document every detail of what I learned. I also helped customers calling in, striving to provide a service that left them happy and supported.


2021: A Season of Giving Back

Transitioned into the role of Associate Cloud Engineer for Azure. For almost a full year, I focused solely on Azure customers, handling P1 and P2 tickets while maintaining my drive to learn and improve. I also began mentoring the new apprentices, wanting to share the knowledge I had gained.


In my free time, I started learning Terraform as I worked toward my goal of becoming a DevOps Engineer. This year was a turning point in recognition; I was nominated for Apprentice of the Year by City & Guilds and was a nominee for the Rising Star award with the King's Trust.


2022: The Pride of the Struggle

Driven by a desire to return to my AWS roots, I transitioned back to the AWS side of the business. This role demanded a higher level of DevOps tooling and a deeper utility of Terraform.


Being surrounded by more senior engineers, I spent my first few weeks immersing myself in the estates and asking as many questions as possible. I remember the pride I felt closing my first few tickets; they felt significantly harder than what I was used to, but that difficulty was exactly why they were rewarding.


2023: The Quiet Improvement

2023 shared a similar theme with the previous year. I continued to tackle tickets, and with every one I closed, I could see myself slowly improving. During this time, I learned that success isn't always about having the answer immediately, but about knowing how to ask the right questions at the right time. As I refined this skill, I moved into handling more critical P1 and P2 tickets, managing higher pressure and more complex environments.


2024: Architecting a New Path

2024 began with the same cloud engineering focus, but I felt a call for a change of pace. I applied for a new role as an Associate Solutions Architect, a move that would completely change the way I viewed customer engagements.


While still performing my engineering work, I spent my time learning the art of architecture. I sat in on calls, took endless notes, and tried to understand exactly what the role entailed. By March 2025, the transition was complete, and I officially became a Solutions Architect.


2025: Lessons in Humility

Stepping into the role of a Solutions Architect brought a new wave of wins and losses. It was a year of deep learning. Some of the most important lessons I learned were about remaining humble and understanding that mastery takes time. I realized that the way I approached tasks needed to evolve. Rather than being taught through a manual, I learned these lessons through the results of my actions, learning from the outcomes of my successes and my mistakes.


2026: Uncharted Waters

If I were to describe this year so far, I would call it a push in the right direction. I chose the title "Uncharted Waters" because I don't know exactly what the future holds, but I know that it will be interesting. My goal now is to ensure that I remain the same bright-eyed person I was in 2019, continuing to move forward and learning a few more important lessons along the way.

Lessons Learnt

  1. Grace in Failure
    Mistakes and setbacks are not dead ends; they are data points. Allow yourself and others the grace to fail.
  2. The Power of Hope
    Hope is not a passive wish; it is the fuel that carries you through the "brutal silence."
  3. Curiosity First
    Approach life with wonder and "starry-eyed" curiosity. It keeps you open to opportunities you didn't know existed.
  4. Intentionality
    Ensure every action is rooted in the best possible intentions.
  5. Decisive Motion
    There are times when you do everything right and still fail. In those moments, if there is no lesson to be found, the only solution is motion. Staying still leads to overthinking; moving forward leads to discovery.
  6. Sustainable Solutions
    Whether in life or in code, resist the urge to rush to the finish line. Prioritize long-term stability over short-term fixes.