Distributed Systems
Designing services that coordinate at scale — across process boundaries, network partitions, and eventual consistency constraints. CAP tradeoffs are engineering decisions, not theory.
Building enterprise-grade backend systems and distributed architectures that perform under real-world load — across healthcare platforms, media streaming, and high-availability infrastructure.
Over the course of my career, I have worked at the intersection of scale and reliability — building backend systems that process millions of events, serve global audiences, and recover gracefully under pressure. My experience spans healthcare and media: two domains where data integrity and uptime aren't aspirational — they're contractual.
At OSN, I contribute to platform infrastructure serving streaming audiences across MENA — onboarding enterprise telco clients, optimising content delivery pipelines, and reducing infrastructure overhead without sacrificing availability. At CureMD, I built enterprise healthcare software where correctness and compliance were non-negotiable constraints, leading teams and shipping across a complex multi-tenant platform serving clinical operations globally.
I am drawn to problems that live at the boundary of performance and correctness: distributed coordination, event-driven data flows, service boundaries that hold under pressure. I work well in senior engineering teams — contributing architecture decisions, reviewing design tradeoffs, and mentoring engineers who are growing into that same systems-level thinking.
Designing services that coordinate at scale — across process boundaries, network partitions, and eventual consistency constraints. CAP tradeoffs are engineering decisions, not theory.
Production Java, Kotlin, and .NET services built for longevity. Clean APIs, disciplined dependency management, testable architectures — code meant to outlast the sprint.
Asynchronous pipelines, Azure Service Bus, RabbitMQ, and event sourcing patterns for systems that need to decouple without losing consistency guarantees.
Azure-native deployments with Docker and Kubernetes orchestration. Infrastructure as a product — observable, reproducible, and cost-aware by design. Terraform for provisioning.
Profiling hot paths, eliminating N+1 patterns, restructuring query plans, CDN caching strategies. Achieved up to 99.93% API response time improvement in production environments.
PostgreSQL, SQL Server, Cosmos DB, and Redis — indexing strategies, query optimisation, and read/write architecture patterns that serve the system, not just the feature.
Real numbers from production systems. Specific clients and internal system names remain confidential.
Problem: Core APIs serving downstream media delivery consumers had accumulated severe latency — response times of 8–10 seconds under load, causing cascading timeouts across dependent services.
Approach: Leveraged microservices and an event bus to pre-process and serve data from Cosmos DB. Introduced CDN caching with indefinite TTL, purged only on data change. Eliminated N+1 query patterns in the Kotlin Exposed DAO layer and combined queries with joins for 50% query round-trip reduction.
Outcome: API response times dropped from 8–10 seconds to under 3–10ms via CDN, and under 300ms for dynamic endpoints — a 99.93% end-to-end improvement. Cascading timeout incidents eliminated.
Problem: Monolithic workloads on Kubernetes were generating excessive resource consumption — memory spiking to 80%, frequent autoscaling events, and unpredictable pod health causing unplanned downtime.
Approach: Refactored monolithic workloads into microservices following single responsibility patterns. Migrated scheduled cron jobs to on-demand notification-based systems via event bus. Segregated background processing from request-serving workloads.
Outcome: Nodes reduced from 10 to 5 (50%), pods from 25 to 11 (56%), system load down 60%, memory from 80% to 20%. Zero autoscaling events observed post-implementation. Infrastructure costs reduced by 30%.
Problem: A growing multi-tenant CMS needed to support major B2B telco clients across STB, ATV, CTV, and mobile — with complex user onboarding flows, purchase integrations, and strict response time SLAs.
Approach: Built read-only serving systems backed by Cosmos DB for read-heavy workloads and PostgreSQL for write-heavy relational data. Designed a zero-downtime deployment strategy. Integrated third-party providers including Comcast, Amazon Prime, and Tabii.
Outcome: Onboarded 2 major telco clients end-to-end, including purchase flows and user lifecycle management. Sustained response times under 30ms. Customer satisfaction improved 30%, infrastructure costs reduced 30%.
Problem: A large multi-tenant healthcare codebase had accumulated significant technical debt — reducing delivery velocity, increasing regression risk, and making architectural improvements unsafe to execute.
Approach: Led service refactoring and architectural decisions across the organisation. Introduced Scrum, structured code review processes, and a formal release pipeline enabling a team of 20 to ship to production without impacting critical business timelines.
Outcome: Technical debt reduced 40% organisation-wide; 20% reduction in refactored services. Delivered 3 major projects including Angular v9→v15 upgrade. Successfully onboarded and developed a team of 6 into independent contributors.
Contributing to the backend platform powering OSN's streaming product — one of MENA's leading entertainment networks. Responsible for content delivery infrastructure, multi-tenant CMS architecture, and the User Gateway managing all transactions across systems. Onboarded major telco clients end-to-end across STB, ATV, CTV, and mobile platforms.
Developed and maintained backend systems for CureMD's enterprise healthcare platform — a complex multi-tenant environment serving clinical operations, telemedicine, billing workflows, and patient data management. Led a team of 6, drove architecture decisions, and introduced engineering practices that improved delivery reliability across a team of 20.
Studied at one of Pakistan's most prestigious technical universities, with a curriculum grounded in algorithms, systems design, software engineering principles, and applied computing. UET Lahore consistently ranks among the top engineering institutions in Pakistan and the broader South Asian region.
Reliability over cleverness.
Latency is user experience.
Simple systems scale better.
Observability is not optional.
Failure is a first-class concern.
Code is read more than written.
I'm open to senior engineering roles, distributed systems challenges, and engineering leadership conversations. Based in Dubai. Available for both FTE & FTC engagements — remote and on-site roles globally.