From curiosity to engineering real-world systems
My journey into software engineering began in the second semester of university. What started as curiosity about how computers solve problems quickly turned into something much bigger. I spent my early days exploring programming fundamentals, data structures, algorithms, and the logic behind software. But I soon realized that understanding code wasn’t enough for me. I wanted to build things that actually mattered.
By my fourth semester, while most of my journey was still supposed to be about lectures and assignments, I had already stepped into the professional world as a developer. I immersed myself in web development, learning how to turn ideas into functional applications and how real software is designed, built, and maintained.
The real turning point came in my sixth semester when I joined Expertflow, a Cisco technology partner. This was where my perspective on engineering fundamentally changed. I was no longer just writing code to make something work. I was building customer-facing applications, working with data-intensive systems, real-time communication, complex backend architectures, and databases where performance, security, and reliability mattered.
I began to understand the difference between building an application and engineering a system that could survive in production.
After gaining nearly two years of professional experience, my journey took me beyond Pakistan to Fitter Health, a Spain-based health-tech startup. There, I transformed backend infrastructure, redesigned data models, developed APIs, and built cloud-based systems that supported real healthcare workflows. It was an opportunity to take greater ownership of engineering decisions and understand how technology directly impacts a growing business.
Along the way, my curiosity expanded beyond traditional software development into data engineering, distributed systems, artificial intelligence, and machine learning. That curiosity also led me to pursue a Master’s in Data Science at the National University of Computer and Emerging Sciences, connecting my software engineering experience with a deeper understanding of data and intelligent systems.
Today, I see myself as an engineer who enjoys understanding difficult problems, designing systems around them, and turning complex ideas into reliable, real-world products.
And the most exciting part? I’m still learning, still building, and still pushing toward problems I haven’t solved yet.
Starting with why, not what
Before choosing a framework, I want to understand the problem. Membership credits, coach booking, or a question over a document each needs a clear workflow and a useful outcome before it needs more code.
think first, build later.Designing for real constraints
Working across APIs, cloud services, and data pipelines means balancing performance, reliability, and delivery. At Expertflow, profiling, Redis caching, and database indexes brought an admin response from 130 ms to 30 ms.
measure, then improve.Collaboration over heroics
I’ve worked across frontend, backend, and SDK teams, and delivered a complete platform as the sole engineer. In both settings, clear API contracts, communication, and documentation help the next person move with confidence.
we, not just me.Making the invisible visible
Reliable software depends on details people rarely see: retries, queue alarms, database constraints, and tests. At Fitter Health, I addressed silent notification loss and handed over documented services with 135 passing tests.
details build trust.
SaaimOpen to full-time roles, contract work, and conversations about things worth building.