The systemsbusinessesrun on.
Multi-tenant SaaS, payment platforms, and AI features — architected to ship, built to last. Six years leading delivery across nine production products.
Get the highlights.
Six years, in numbers
Not a portfolio of demos. A portfolio of production.
ARCHITECTED.
SHIPPED. OWNED.
Every system below is live, in production, carrying real customers — not a Dribbble shot.
How I actually build it
Not a stack of buzzwords. A system that holds together.
Scroll — this is Paylio's real request path, drawn live.
Client requests a page
RadiologyJobs — Challenge
Radiology hiring runs on keyword job boards that don't understand what anyone is actually looking for.
Constraints
Candidates need to search in plain English. Employers need to hire at volume, not one listing at a time.
Architecture
An AI recruiter layer sits in front of the listings, not just a search box on top of them.
It continuously scans new postings and matches them against saved candidate searches, emailing matches directly.
The decision
A passive listings board means candidates do the searching, over and over. Matching runs the other way here — postings are scanned as they arrive and pushed to the candidates already looking for them, with an employer dashboard built for bulk hiring: XML/CSV import and team workspaces, not one form per role.
Result
A marketplace that finds the match, instead of making people search for it.
View radiologyjobs.com ↗How I actually work
Six principles, held the same way on every product.
Silence is a bug.
Systems fail silently unless you design them to speak. Observability, structured logging, and measurement protocols ship with the feature - not after the incident.
Scale on day one.
Multi-tenant resolution, domain-based routing, no hardcoded country logic. The architecture assumes growth before the first customer arrives.
Security is not optional.
Secrets out of git history, CORS hardened, JWT and cookies locked down. Remediation runs as a program, not a checkbox.
Automation beats repetition.
CI/CD pipelines, content-hash caching, exchange-rate cron sync. If it happens twice, it gets automated the third time.
AI augments, never replaces.
Agentic tooling accelerates diagnostics, review, and delivery - judgment and architecture stay human.
Business value or it doesn't ship.
Every feature answers one question: what measurable problem does this solve?
Selected work
Live systems, real stakes.
Questions, answered.
Senior full-stack (MERN) engineering and technical leadership — multi-tenant SaaS architecture, production payment systems, and AI-assisted delivery, primarily in React, Next.js, Node.js, NestJS, and PostgreSQL.
Yes — open to select senior software engineering and technical-lead roles, remote-first from Lahore, Pakistan. The fastest way to reach him is WhatsApp or email, both linked in the contact section.
Frontend: React, Next.js, TypeScript, Tailwind. Backend: Node.js, NestJS, PostgreSQL, Redis, BullMQ. Cloud & DevOps: AWS, OVHcloud, Docker, GitHub Actions CI/CD. Plus Stripe, GA4/Measurement Protocol, and agentic AI tooling.
Production SaaS with real stakes: multi-tenant WPS-compliant payroll (Paylio), a payment-analytics dashboard over live PSP webhooks, multi-currency European commerce, and an automated print-on-demand render pipeline.
As a technical lead: he scopes the smallest valuable slice, owns the architecture and code review, leads a five-person team across a nine-product portfolio, and measures engineering in business outcomes — not just features shipped.
Let's build something
that lasts.
Hiring your first senior engineer, scaling a platform, or shipping an AI product — one message is enough.