Taking Your Work as a Craft

There are two ways to approach professional life. You can treat your work as a job — something that fills your days, pays your bills, and gives you a sense of stability. Or you can treat it as a craft — an ongoing pursuit of mastery, meaning, and contribution. A craft is not performed; it is lived.

For me, work — whether architecture, engineering, leadership, teaching, or writing — is not an obligation. It is a craft. This understanding did not arrive suddenly. It matured through years of moving across countries, industries, projects, and cultures: from Pakistan to Japan, and from Japan to Germany.

Craftsmanship is not something you learn; it is something you live.

Pakistan: Foundations of Grit and Ownership

Growing up in Pakistan, my love for books shaped the earliest version of who I am. Stories became my teachers, and learning became a lifelong habit. As a proud alumni of UMT (Batch 8, MCS 2000–2002), I received an internship offer at a Job Fair even before finishing my degree.

After my internship, I began teaching Java at a university. I quickly realised that technical skill matters, but connecting with human struggles matters even more. Students understood me not because I was an expert, but because I remembered how difficult it felt to be a beginner. That awareness — the memory of struggle — would later shape my leadership philosophy across three continents.

Early in my career at i2c Inc., I worked on mission-critical payment systems where even a small oversight could affect thousands of users. This environment taught me real ownership: responsible for outcomes, not just tasks. I learned to think about systems in layers — load, throughput, latency, failure modes, operational risks, and user impact.

Japan: Where Excellence Becomes a Lifestyle

Japan changed everything. I often say: if you want to learn technology, read books. If you want to learn discipline, go to Japan. Whether it's the precision of trains, the harmony in architecture, the consistency of service, or the fireworks that take decades to perfect — Japan embodies the philosophy of craft.

At Rakuten Travel, I led the team that redesigned the next-generation search engine — supporting multilingual queries, contextual tagging, morphological analysis, and massive scale. Our performance goal was 100 milliseconds per query. We achieved it. But what stayed with me was not the metric; it was the discipline, teamwork, and culture that made it possible.

We practised Test-Driven Development rigorously, achieving 99% code coverage and reducing defects to near-zero. I learned a powerful truth: mastery requires consistency, and consistency requires humility. You cannot become a craftsman if ego blocks improvement.

Later, at Fast Retailing (Uniqlo), I led teams across Japan, China, and India to build Cart & Checkout systems serving millions of users globally. What Japan taught me — more than technology — was a philosophy:

If there is no possibility, create one. If there is no paradigm, invent one. If there is no tool, build one.

Germany: Structure, Architecture & Solving Problems at Scale

Germany brought refinement. Here, I learned to merge innovation with structure — balancing creativity with governance, engineering freedom with regulatory compliance, and speed with sustainability.

At Wemolo, I designed cloud-native smart parking systems. At Mindshine, I reduced cloud costs by 70%, built a serverless data analytics platform, and helped shape a culture rooted in psychological safety. At Sopra Steria, I architect cloud-native, DORA- and GDPR-compliant solutions for the Payments and FinTech domain — working with AWS, large-scale microservices, multi-region clusters, and complex regulatory requirements.

I developed my signature approach: evaluating every problem through non-functional pillars — Throughput (TPS, QPS, RPS), Load, Scale, and Capacity. This ensures solutions are not only elegant but also resilient, battle-tested, and future-proof.

Philosophy of Craft: My Guiding Principles

The Journey Continues

After 23 years across three countries, I still consider myself a student. Not because I know less, but because mastery never ends. Craft is a journey with no final chapter.

Every new challenge is a chance to refine, rethink, rebuild, and reimagine. Every day is a chance to improve something — code, architecture, culture, processes, or myself.