I'm a full-stack JavaScript engineer from Lahore with a BS in Computer Science and three years of shipping production software for enterprise operations. I've built payment and point-of-sale systems with role-based access, gateway integrations and React Native apps running on dedicated card terminals; AI-driven hiring platforms that generate job descriptions, score candidates against weighted skills and run real-time voice interviews over WebSockets; OCR document capture feeding Apple and Google Wallet passes; and SharePoint-backed intranets with Azure AD single sign-on, approval workflows and LLM assistants grounded in company content. The common thread is owning the whole integration, from the interface to the API contract to the data model, not just the screens.

On the product side I build and run commerce platforms end to end: multi-variant catalogues, discount engines, guest-to-account cart merging, per-market pricing resolved at the edge, verified payment webhooks, server-side conversion tracking, and admin dashboards with audit logs, RBAC and exports, plus the companion mobile apps teams run the business from. Day to day that means TypeScript, React, Next.js and React Native on the front; Node, FastAPI, Prisma and PostgreSQL or MSSQL behind; Azure deployments, DevOps pipelines and Blob Storage, Cloudflare and Vercel underneath. And I stay on after launch, with monitoring, rate limiting, CSP hardening and rollbacks that are boring by design.

Underneath the frameworks, I like knowing what is actually on the wire. I've written an HTTP/HTTPS forward proxy on raw TCP sockets, with CONNECT tunnelling, a thread per client and structured request logging, and a reliable transport on top of UDP with sequencing, acknowledgements and retransmission. That grounding shows up in the day job: in how I debug a dropped WebSocket, size a payload or reason about what a cache will really do.