Saaim Abdullah

I’m Saaim Abdullah, a software engineer based in Lahore, working European and US-East hours. I build distributed backends: services that hold up under traffic, pipelines that can be replayed, and data models that do not have to be apologised for a year later.

Two years of that so far. At Expertflow, a Cisco UCCE solution partner, I owned backend services for 1,000 to 3,000 daily users, deployed them across pods on AWS EKS with autoscaling driven by request throughput, and built event-driven ETL on Lambda, MWAA, PySpark and EMR. At Fitter Health I was the entire engineering function: a preventive health platform for a Spain-based team, taken from an empty repo to live production, with the Next.js frontend, the Django and DRF backend, a 106-table PostgreSQL schema, the AWS estate and the Odoo integration all mine, then documented and handed over.

Those two jobs taught opposite lessons and I needed both. In a team you learn that the contract between services is the real product. On your own you learn that nobody catches your bad data model, nobody notices the queue quietly dropping messages, and nobody documents the system if you don’t.

So I start from the failure modes, because the interesting part of a design is what it does when something is already broken. A queue that drops messages silently is worse than one that refuses them loudly, so the durable buffer and the dead-letter path come before the feature. A constraint in the database beats a check in the serializer, because the serializer is not on the path a management command takes. And I would rather argue about a schema for a day than migrate one for a week.

I’m now looking for a full-time role where I own a system rather than a ticket queue. I write up how I build things on Medium, the code is on GitHub, and my data structures and algorithms work is public in DSA-Python: graphs, dynamic programming, tries and the rest, written out with complexity analysis rather than pasted from a solutions page.