Backend · APIs · Distributed systems

Your traffic
doubled.
Your backend
shouldn’t notice.

I’m Saqib. I design APIs, microservices and multi-tenant platforms that stay fast and boring under load. Python, Node.js, PostgreSQL, Redis.

Studio portrait of Saqib Ejaz in a charcoal blazer
Scroll to exploreAPIs · Microservices · Multi-tenant
01 / Where I come in

Growth is good.
Timeouts aren’t.

Most scaling problems are a few bad queries and one decision nobody wrote down.

01 / LATENCY+

“The API gets slower every month.”

Find the hot paths. Fix queries, cache with Redis, measure again.

02 / TENANCY+

“One big customer slows everyone.”

Multi-tenant design with sane limits and real isolation.

03 / ARCHITECTURE+

“The monolith is the bottleneck.”

Split what needs splitting into services. Leave the rest alone.

04 / DEPENDENCIES+

“Nobody knows what talks to what.”

Map the dependencies, document the APIs, make it legible.

05 / RELEASES+

“Deploys are scary.”

Repeatable CI/CD with Docker and Terraform. Boring is the goal.

02 / Work behind the words

High traffic,
low drama.

40+

major platform features delivered at TestGorilla

5,000+

moves supported by the WeMove platform

8+

years shipping production software, end to end

TestGorillaNetherlands · remote
Senior engineer

Scaled backend services and REST APIs for a high-traffic platform. Delivered 40+ major features with Node.js and React, shipped through CI/CD, Docker and Terraform.

Current role2025 – now
Lead / GenAI engineer

Distributed systems and high-performance APIs for large-scale code analysis and dependency mapping. LLM + retrieval automation pipelines. AWS and Azure with Docker and Terraform.

WeMoveUS · remote
Team lead

AI-powered scheduling and logistics microservices in NestJS and PostgreSQL. LLM automation that lifted operational efficiency 25% on a platform supporting 5,000+ moves.

AlayaCareCanada
Tech lead · secure messaging

Led secure messaging: OAuth 2.0 / JWT and the serious version of “who can see what”.

Selected outcomes from previous roles.
03 / Stack

Built for load.

Picked for the problem, not the conference talk.

PythonFastAPIDjangoFlaskNode.jsNestJSExpressREST APIsMicroservicesPostgreSQLRedisAWSAzureDockerKubernetesTerraform
04 / How I work

No theatre.
Just shipping.

Same rules whether it’s a two-person startup or a platform with serious traffic.

01

Problem first, stack second.

I’ll ask annoying questions before I write clever code.

02

Ship small, ship often.

You see working software in days, not a deck in weeks.

03

Built to be run.

Deploys, CI/CD and infra are part of the job, not someone else’s ticket.

04

Talk like a human.

Clear updates, no jargon fog. Disagreements said out loud, early.

05 / Pick your flavour

Same engineer.
Your problem.

Choose the one that sounds like yours. Each page is the short version for that job.

06 / Let’s talk

Where does it hurt?

Send me the symptom: slow endpoint, angry customer, scary deploy. We’ll find the cause.