React / TypeScript · ASP.NET Core / .NET · PostgreSQL / Supabase · ERP · Logistics · Production Debugging
LinkedIn · Email · Production Case Studies
I build and harden production business software. My strongest work sits at the intersection of full-stack product engineering, messy operational data, internal tools, ERP integrations, logistics, and AI-assisted development.
I am especially useful when a project has moved beyond the prototype stage and now needs someone who can understand the existing system, find hidden failure modes, make targeted changes, test them properly, and ship without casually breaking business rules.
- Production app rescue & code audits — inherit React, Supabase, .NET, or AI-generated codebases; trace bugs; improve architecture; add tests; harden risky flows.
- ERP & internal tools — dashboards, inventory, purchasing, sales, finance, reporting, permissions, exports, reconciliation, and legacy-system integration.
- Backend & data engineering — ASP.NET Core APIs, PostgreSQL/Supabase, SQL Server integrations, data pipelines, migrations, background jobs, and auditability.
- Logistics & routing — route planning, dispatcher workflows, GPS/telematics analysis, geocoding, delivery evidence, and human-in-the-loop optimization.
- Applied AI/ML — computer vision, medical imaging, OCR, speech/NLP, and practical AI features that have to coexist with real software systems.
Open to freelance, contract, and product-engineering work where production reliability matters more than demo polish.
My largest current codebase is a private production ERP and logistics platform. The source, customer data, commercial rules, and operational datasets remain private, but the engineering work includes:
- React 19 + TypeScript frontend
- ASP.NET Core / .NET 10 backend
- PostgreSQL / Supabase
- SQL Server / legacy ERP integration
- sales, purchases, stock, collections, customers, suppliers, cash flow, P&L, reporting, and administration
- authentication / RBAC and module-level permissions
- route planning, delivery workflows, geocoding, and GPS/telematics analysis
- CI, automated tests, release verification, migrations, and production debugging
I keep a sanitized write-up of this work here:
→ Read the production engineering case studies
I use coding agents aggressively, but I do not treat generated code as verified code.
My normal workflow is:
requirements → repository/schema inspection → implementation → independent review → focused tests → regression checks → release verification
For difficult changes I use multiple agents/models adversarially: one can implement while another searches for broken assumptions, missing edge cases, unsafe migrations, or false success signals. I remain responsible for the requirements, technical judgment, acceptance criteria, and final verification.
This is particularly useful for AI-generated or “vibe-coded” applications that need to become maintainable production systems.
| Area | Technologies |
|---|---|
| Frontend | React, TypeScript, JavaScript, Vite, Tailwind |
| Backend | C#, ASP.NET Core / .NET, Node.js, REST APIs |
| Data | PostgreSQL, Supabase, SQL Server, MongoDB, SQL |
| AI / ML | Python, PyTorch, scikit-learn, computer vision, OCR, speech/NLP |
| Mobile | Kotlin, Jetpack Compose, React Native / Expo experience |
| Delivery | Git/GitHub, CI, Docker, Heroku, Render |
| Engineering focus | debugging, testing, data integrity, migrations, observability, production hardening |
Computer-vision and medical-imaging experimentation around segmentation workflows.
Machine-learning experimentation for structured healthcare data.
Public C# backend project demonstrating .NET/backend development.
Public full-stack JavaScript application work covering frontend/backend integration and application flows.
Alongside product engineering, I work on applied AI research in areas including:
- pediatric cardiac / medical-image segmentation
- healthcare machine learning
- OCR pipelines
- Arabic speech and NLP workflows
I am currently pursuing an MSc in Artificial Intelligence at Istinye University and hold a BSc in Computer Engineering.
That research background is useful in product work because I am comfortable moving between experiments, data analysis, software implementation, and evidence-based debugging instead of treating them as separate disciplines.
Good fit:
- “We built this quickly with AI and now need an engineer to make it reliable.”
- “Our internal system has years of business rules and nobody wants a rewrite.”
- “The dashboard says one number, the ERP says another, and we need to know why.”
- “We need a React/.NET/Postgres feature added without breaking production.”
- “Our route/delivery/GPS workflow works in theory but fails in real operations.”
- “We need a technical audit before investing in a larger rebuild.”
Production software, not just prototypes.
musabkhan2003@gmail.com