Voice agents that survive real callers
Telephony, speech, turn-taking and tool calling, with the booking and record-writing logic kept firmly out of the model's hands.
AI engineer · Karachi
I build production AI where the consequential logic stays deterministic and auditable, and the language model is scoped to the one thing it is actually good at. Voice agents, agentic pipelines, and integrations across systems that were never meant to talk to each other.
Four shapes of engagement. Most work is some combination of them.
Telephony, speech, turn-taking and tool calling, with the booking and record-writing logic kept firmly out of the model's hands.
Multi-stage systems that keep running when a third-party API fails halfway through. Retries, timeouts, checkpoints, human approval gates.
Reconciling records across systems that disagree, where names are partial, transliterated or simply wrong, and a false match is expensive.
Backend, frontend, mobile and the deployment underneath it. Usually the only engineer on the project.
Six projects with the most to explain. See all 15, by category

Profit analytics for direct-to-consumer Shopify brands. Revenue is not what lands in the bank, so the whole dashboard is built on contribution margin instead.
Turning free-form WhatsApp haggling into matched orders against a hand-kept catalogue with no clean keys, for an oil-blend vendor.
One endpoint that lets an assistant read and write Google Tasks and Calendar, hardened against a specific client's probing behaviour.

Consignment marketplace for collectible sports cards. The seller ships cards in and the operator handles everything through to payout.

Breast health screening and education, shipped as a mobile app with a risk questionnaire, a symptom journal and exam reminders.
An HTTP API that converts an ebook for a 2011 Kindle, sized to fit a machine far too small to do it comfortably.
A reusable demo application that reskins to a new client's brand by editing one file, with the colour system enforced by the build.
Grouped by the kind of problem rather than the client.
Voice agents, LLM pipelines and tool servers, built so the model never owns a decision it can get expensively wrong.
6 projectsClient web products that are live and that you can open right now.
5 projectsSmall services sized precisely to the constraints they run under.
6 projectsPipelines that reconcile systems with no clean keys, and survive the APIs they depend on.
3 projectsFlutter applications, offline-first where it matters.
2 projectsRoles and dates. What I built inside them stays with the companies that own it.
What I reach for. The first group is where most of the time goes.
Multi-agent pipelines, LLM orchestration, voice agents, human-in-the-loop design, deterministic scoping and model-risk design, n8n, Make.com.
OpenAI and GPT-4o APIs, NLP, PyTorch, TensorFlow, scikit-learn, model evaluation and regression testing.
ETL pipelines, cross-system reconciliation without clean keys, EHR integration, Stripe, QuickBooks and Xero APIs, SQL, AWS S3, Glue and RDS.
Docker, FastAPI, Cloudflare Workers, R2 and Pages, Contentful, observability and cost telemetry, HIPAA-compliant system design.
Python, SQL, JavaScript and TypeScript, C++, and Go at working knowledge.
Next.js, React, NestJS, Flutter, Node.js, PostgreSQL, MongoDB, Neon, Supabase.