Requirement to deployment. No handoffs, no gaps.
Pre-medical to software. Not the typical path, but the lesson stuck: results matter, not the route. Within two years of starting university, I had my first professional MERN Stack role at Level Up, Islamabad. What I learned there wasn't syntax. It was that the gap between working code and a working product is enormous, and most developers never cross it. I decided early that I would.
My final-year project, SMART GAZE, was a CCTV classroom monitoring system: face recognition, emotion analysis, and attention tracking, built on MERN with AI/ML models trained from scratch. Not academic. A production system with a live backend, real-time processing pipeline, and an interactive frontend. That project taught me what it actually costs to put machine learning into a product someone else runs.
At ApexBeat, backed by iSOFT UK, I contributed as a core full-stack developer: building the student platform, admin panel, support system, and CRM from the ground up. Separately, for MUNDIDA in Italy, I delivered all three portals end to end: prime clients, consultants, and admin. From requirement gathering through architecture, development, deployment, and handoff. Both engagements had one thing in common: no one else could own it, so I did.
Full-Stack Ownership
Most developers work in a layer. I build across all of them, from MongoDB schema design through Node.js API architecture to React interfaces. The result is systems with no translation cost between layers.
AI/ML Integration in Production
Training models isn't the hard part. Embedding face recognition, emotion analysis and real-time landmark detection into a live CCTV monitoring system is. I've done both, and I know where the real complexity lives.
End-to-End Delivery
Requirement gathering, architecture, development, testing, deployment, client handoff. I don't stop at the edge of my lane. When I take ownership of a product, I own the full loop from first commit to production.
What I don't do
- I don't start without understanding the problem. Requirements first, code second. Always.
- I don't treat the UI as decoration. Frontend architecture matters as much as the backend.
- I don't ship and disappear. Delivery means the client can run it without me in the room.
Used in production. Not just on a resume.
