Three chapters.
One continuous journey.

Pakistan gave me something no degree, no company, and no continent could replicate — grit. Born on 10 January 1979 in Gujranwala, I grew up in Guddu (Sindh) from 1983 to 1996 — a WAPDA colony town near Sukkur, far from the noise of big cities but full of community, curiosity, and a quiet determination to grow. That small-town upbringing shaped my resilience more than anything that followed.

My love for books shaped the earliest version of who I am — a gift from my father, who filled my childhood with fairy tales, magazines, and moral stories. In 1996 I moved to Lahore for university, completing a BSc in Applied Mathematics & Physics at Punjab University (1996–1999), then an MCS at Hamdard University / UMT (Batch 8, 2000–2002). Stories were my first teachers. That hunger to understand why things worked became the foundation of everything that followed.

But my path was never a straight line — and I want to be honest about that. Like so many children in Pakistan, I grew up with only two scripts for a successful life: become a doctor, or become an engineer. In tenth grade, a cousin had just entered medical college and become the family's pride — so I was told, follow him, be a doctor. No one asked what I wanted, and I did not yet have the courage to ask myself. When my marks fell short of the medical cut-off, it landed as a quiet family disappointment.

So I followed my friends into FSc pre-engineering instead. I was strong in mathematics and physics, but chemistry and biology never took hold, and once again my scores fell short of a good engineering seat. I enrolled in a BSc and struggled there too — the two-year annual-exam format never suited the way I actually learned. By around twenty, I was a young man with no clear direction, and no one to hold his hand and point the way.

Then one small thing changed everything. A hostel friend had joined a computer science programme, so I sat the aptitude test for a Master's in Computer Science — and to my surprise, I aced it. The questions were analytical, logical, almost puzzle-like, and for the first time studying felt like play. That was the moment I found my path: not handed to me, but stumbled upon and then chosen. It taught me the lesson that has carried me across three continents since — when you are lost, learning is the way forward.

After graduating, I began my professional life as a Java teacher at university — and quickly realised: technical skill matters, but connecting with human struggles matters more. Students understood me not because I was an expert, but because I remembered how difficult it felt to be a beginner. In 2008, I transitioned fully into software development, joining i2c Inc., where mission-critical payment systems taught me real ownership — not of tasks, but of outcomes.

Growing up in Pakistan in the 1980s and 90s also meant living through one of the most extraordinary technological revolutions in human history — from the ground up. I rewound cassette tapes with a pencil. I heard my first dial-up modem connect to the internet and knew, instinctively, that everything had changed. I held the early mobile phones that seemed like science fiction. Every transition — analog to digital, physical to connected, local to global — I felt personally. That generational experience of living through the transformation, not just reading about it, gave me a reference point no younger engineer will ever have. We are not digital natives. We are digital immigrants who became digital architects.

At i2c Inc., I worked on high-throughput OLTP systems supporting Visa, Mastercard, Discover, and American Express across four continents. I began thinking about systems in layers: throughput, load, latency, failure modes, operational risks, and user impact. This is where the craftsman was forged.

Pakistan also gave me something less technical but equally powerful — the spirit of community. The hospitality, the brotherhood, the willingness to improvise and keep moving with limited resources. People here solve problems that would stop others entirely. That resilience is cultural DNA, and I carry it everywhere I go.

Japan changed everything.

I often say: if you want to learn technology, read books. If you want to learn discipline, go to Japan. There is something about this country — the precision of trains arriving to the second, the harmony of architecture, the fireworks that take decades to perfect, the tea ceremony mastered over a lifetime — that reshapes what you think excellence means.

I arrived in Tokyo in 2016 with nearly a decade of software development experience and what I thought was a mature engineering mindset. Japan politely, respectfully, and thoroughly dismantled that assumption. Not through criticism — through example. When the people around you operate at a level of craft and care that makes your own standard look like a rough draft, you either adapt or you leave. I chose to adapt.

At Rakuten Travel, I led the team redesigning the next-generation search engine — supporting multilingual queries, contextual tagging, morphological analysis, and massive scale. Our performance goal: 100 milliseconds per query. We achieved it. But what stayed with me was not the metric. It was the discipline, the teamwork, and the culture that made it possible. We practiced Test-Driven Development rigorously, achieving 99% code coverage and reducing defects to near-zero.

At Fast Retailing (Uniqlo), I led teams across Japan, China, and India to build Cart & Checkout systems serving millions of users globally. APIs capable of handling 1,000 orders per minute. Infrastructure as Code using Terraform. Production-ready solutions rolled out effortlessly across regions. And through all of it — the Japanese philosophy of Monozukuri (attention to craft and detail) became not just a cultural observation but a personal standard.

Japan also gave me Ikigai — the intersection of what you love, what the world needs, what you are good at, and what you can be paid for. Finding that intersection is a lifelong pursuit. Tokyo accelerated mine considerably. And it gave me one principle I have never abandoned since: If there is no possibility — create one. If there is no paradigm — invent one. If there is no tool — build it.

Germany brought refinement.

After the fire of Pakistan and the precision of Japan, Munich offered something I had not expected to find: structure as a form of freedom. A society where rules exist not to constrain but to create the conditions for everyone to flourish. Work-life balance not as a perk but as a right. Psychological safety not as a workshop topic but as a way of operating.

The reason I moved to Germany was Wirecard — one of the most exciting FinTech companies in Europe at the time. I joined as a Senior Software Architect in January 2020, working on modernising their merchant onboarding platform. Six months later, Wirecard filed for insolvency — the largest corporate fraud scandal in post-war German history. It was a defining chapter: I learned that even fine companies can fail, that your craft and values must outlast any organisation you join, and that resilience is not optional. It was also the moment Munich revealed itself to me as a city I wanted to stay in.

What followed was a chapter I had been preparing for across an entire career. At Wemolo, I designed cloud-native smart parking systems using AWS, IoT, serverless technologies, and Terraform. At Mindshine, I reduced cloud costs by 70%. Then, across the Sopra Steria Group — first at Sopra Banking Software (SBS), then Sopra Financial Technology, and now Sopra Steria itself — I grew as a Senior Cloud Architect, designing domain-driven, secure, containerized, scalable, and resilient cloud architectures for FinTech and FinOps domains.

Germany is also where I became most fully myself as a husband and father. Three sons. A home in Munich. A family that is my anchor, my mirror, and my purpose. The engineering problems I solve at Sopra by day are shaped by the patience I learn from parenting by night. Both roles make me more grounded, more purposeful, and genuinely grateful for the life I have been given.

Germany has also sharpened my thinking about AI — not as a threat to craft, but as the next frontier of it. In our team's work on AIOps (the merger of DevOps, CloudOps, and AI), I see the next decade of cloud architecture being written right now. Human strength in this era will not be raw knowledge — it will be depth, judgment, and values. The things that no model can train on experience alone.

I am still becoming. Munich continues to make me. This chapter is not finished — it is the longest one yet, and perhaps the most important.