Muhammad U.

Full Stack Engineer with 8+ years building HIPAA compliant healthcare, FIntech, SaaS and AI systems. I took a clinical platform from zero to production and acquisition inside its first year, and I've shipped software serving 800,000+ real users. If you're building in a regulated space (Healthcare/HIPAA, fintech, compliance-heavy), I build systems that stay secure and reliable when the load doubles and the auditors show up. I design for the constraint that actually matters in regulated products: audit-readiness and data security from the first commit, not bolted on later. Eight years across platforms with hundreds of thousands of users taught me that what separates software that holds up from software that doesn't is almost never the framework, it's the architecture decisions made early and the discipline held throughout. WHAT I BUILD Full-stack web applications: Next.js (App Router, SSR/SSG/ISR) with TypeScript and Tailwind on the front end; Node.js and Python (Express, Django, FastAPI) on the back end; PostgreSQL, Prisma, Supabase, and MongoDB for data. Multi-tenant from day one, secure authentication, and clean AWS deployments with Docker, Nginx, and GitHub Actions built to scale without a rewrite six months later. HIPAA & regulated products: PHI handling, encryption at rest and in transit, role-based access control (RBAC), audit logging, and BAA-aware architecture. Experience with EHR/EMR integration, FHIR and HL7 data exchange, and custom Stripe billing with automated invoicing. AI-native features & LLM integration: RAG pipelines over private documents with controlled hallucination, LLM-powered workflows, and multi-agent systems where accuracy is a requirement. OpenAI, Claude, Gemini, and Mistral, with LangChain, LlamaIndex, and LangGraph, plus Pinecone, Weaviate, FAISS, and Chroma for vector storage. AI voice agents with Twilio, LiveKit, and Retell when a project needs conversational AI. HOW I WORK I start from what the product needs to achieve; architecture, security, scale, and AI decisions follow from that. If I'm joining an existing system, I understand the codebase before I change it, and I'll push back when something technically correct would make the product worse. No cowboy commits. No "it worked on my machine." No Friday deploys that leave you fixing production over the weekend. If you're building software that has to perform in production not just demo well send me a message and tell me what you're building. I'll explain exactly how I'd approach it.