Hire
Hire an AI product engineer who ships.
Remote contract work, and senior mobile roles. Based in Pakistan, working with teams in the US, UK, Europe and Asia.
Open to senior mobile roles and contract work — remote
What I build
- Putting an AI feature into an app that already has users: support automation, LLM integration against OpenAI or Gemini, on-device inference where latency or privacy rules out a round trip, and the escalation path for everything the model should refuse.
- Building a new cross-platform iOS and Android app, from requirements through to App Store and Google Play release — App Review included, which is where AI features get stopped most often.
- Taking over an unstable Flutter codebase, with memory leaks, messy state, excessive API calls, navigation problems and performance bottlenecks, and making it reliable enough to build on.
Evidence
The parts you can open yourself.
Released to the App Store in 2026 — sole engineer
- AI Receipt Scanner & TrackerPhotographed receipts turned into export-ready Excel and PDF reports, by category, month, client, project or tax purpose.↗
- Voice Calorie Counter AILog a meal by speaking it rather than searching and tapping, with on-device reading of packaged nutrition panels.↗
- AI Humaniser — Detect & RewriteReads a draft for machine-written patterns and rewrites it, with a compare view before anything is copied.↗
- Cluster — Shared Tasks & ChoresHousehold chores and shopping, with recurring tasks that rotate between members and lists several people can patch at once in real time.↗
- Bloom — Voice Journal & DiarySpoken journalling with transcription, mood tracking and a weekly written-back story. Usable with no account and no sign-up.↗
Client engagements — the detail is on the work page
- Performance refactorCognitive BeamInherited a production app with memory leaks, excessive API calls and no state management.→
- AI support chatbotDafi LabsAn AI support chatbot that took most of the support load off a human queue.→
- Factor WalletFactor Wallet Inc.A non-custodial multi-chain crypto wallet covering Bitcoin, Ethereum, Solana and eight further chains, with in-app swaps and a DApp browser.→
Open source: browser-execution-runtime, TypeScript, MIT licensed — the rest is here. The engagement figures on the work page are my own measurements of private apps; proof separates those from what you can check.
Stack
- Role
- AI product engineer, mobile · Flutter team lead
- Shipped in 2026
- 5 iOS applications live on the App Store, 4 of them AI, sole engineer
- AI in production
- Support automation, OpenAI and Gemini integrations, agent tooling
- AI surfaces
- Voice capture, document scanning, generation and rewriting — all shipped
- Release
- App Review and Google Play releases, end to end
- Languages
- Flutter · Dart · Kotlin · TypeScript
- Architecture
- Clean Architecture · BLoC · state and lifecycle work
- Real-time
- WebSockets, chat and presence in shipped apps
- Experience
- 5 years building production mobile applications
- Open source
- browser-execution-runtime, TypeScript, MIT
Availability and rate
Available for full-time contract work, remote, and open to senior mobile engineering roles on the same terms. My rate depends on project duration, team size and technical complexity. If you have a budget already set, tell me what it is and I will tell you honestly whether I can work within it.
I do not compete on the lowest hourly rate. I compete on delivering production code that works, on schedule, without the rework that cheap bids tend to cost later.
Process
- 01Initial callThirty minutes on what you are building, the timeline, and whether my experience actually fits it.
- 02Scope and estimateA written breakdown of the work, the timeline and the cost. In writing before anything starts.
- 03ContractStandard services agreement — milestone-based or time-and-materials, depending on how certain the scope is.
- 04DeliveryPR-based workflow, your standups if your team runs them, and production releases when the work is done.
Not a fit if
- You need someone on-site. I work remotely, from PKT (UTC+5).
- You are optimising for the lowest hourly rate. Mine reflects senior experience, and I would rather you spend it with someone else than have that argument mid-project.
- You need a team rather than one engineer. I work as a senior individual contributor or a tech lead; I do not run an agency.
Before you get in touch
The questions that usually arrive first.
Answered here so the call can start further along. If the question behind them is what a build will cost, I have written that out in full.
- What do you actually mean by AI work?
- Shipping AI features inside products people use, not model research. In practice that is: LLM integration against OpenAI or Gemini, support automation, speech and document capture, on-device inference where a round trip is too slow or too private to make, and the plumbing around all of it — streaming responses, failure states, cost per call, and what the feature does when the model is wrong or unavailable. Four of the five apps I released in 2026 are AI products, and browser-execution-runtime, which I maintain, is agent tooling. I do not train models. I make them work in something that ships.
- Everyone says they do AI now. Why you?
- Because the hard part is not the API call, and the market prices it as though it were. Anyone can get a model responding in a prototype. What decides whether the feature survives is the part underneath: what the assistant refuses, how a user escalates without repeating themselves, what happens on a bad connection, what it costs per thousand users, and whether App Review accepts it — AI features are rejected for reasons most teams only discover on submission. I have shipped that whole path four times this year alone, and separately fixed the apps that had an AI feature bolted onto an unstable codebase. If you want a demo, many people can build one. If you want it in the store and still working in six months, that is a different skill and it is the one I sell.
- Are you available for contract work right now?
- Yes — full-time contract work, remote. I am also open to senior mobile engineering roles. The fastest way to find out whether a project fits is to send the problem rather than the job spec.
- What are your hours, and can you overlap with US or European teams?
- My timezone is PKT (UTC+5). That gives a full working overlap with Europe and a partial one with US East Coast mornings. I work asynchronously by default and keep decisions written down, so overlap matters less than it would with a purely synchronous team. If your team needs someone on-site, I am not the right hire.
- How do you charge?
- My rate depends on project duration and scope, so it is quoted per engagement rather than published as a single hourly figure. I do not compete on the lowest hourly rate — I compete on delivering production code that works on schedule, without the rework that cheap bids tend to cost later.
- Can you take over an existing Flutter codebase?
- That is one of the three kinds of work I do most. Inheriting a live app with memory leaks, unmanaged state, excessive API calls, navigation problems and performance bottlenecks, and making it reliable. On one such engagement that meant refactoring to Clean Architecture with BLoC rather than patching symptoms: unnecessary API calls fell by about 40% in four weeks, state moved out of the widget tree entirely, and the app stopped degrading over the course of a session.
- Can you build an app from scratch and get it released?
- Yes, including the release itself — cross-platform iOS and Android from requirements through to App Store and Google Play, App Review included. App Review is a particular interest of mine, specifically the reasons apps actually get rejected, which is usually cheaper to know before submission than after.
- Do you do real-time or AI features?
- Both, in apps that already have users rather than as greenfield demos. Real-time means WebSockets, chat and presence in shipped apps. AI means support automation with OpenAI and Gemini integrations — on one engagement, support response time went from 10 minutes to 30 seconds with 70% of queries handled without a human.
- Can you lead a team, or do you only write code?
- Both. I have worked as a Flutter team lead, leading four engineers and setting the delivery and code standards they worked to. I am comfortable as a senior individual contributor or as the person responsible for how a mobile team ships.
- What is your stack?
- Flutter and Dart primarily, with Kotlin, and Clean Architecture with BLoC for state. Five years building production mobile applications. Outside client work I maintain browser-execution-runtime, an MIT-licensed TypeScript project, which is public if you would rather read code than a CV.
- Can I see something you have actually shipped?
- Yes — five iOS applications released in 2026, all live on the App Store now, each one built and taken through App Review by me as the only engineer: a receipt scanner and expense tracker, a voice-driven calorie counter, an AI text humaniser, a shared household task app and a voice journal. The proof page links every listing, along with the public repositories behind the real-time and agent-tooling work. Four client apps are public too — Factor Wallet, CrowdGen AI, Encounter Walking and Infinity Club — though those are published by the clients, so they show the product rather than who wrote it. Start with the things you can open yourself.
- How does hiring one engineer pay off against an agency?
- The saving is not the rate, it is the rework. Most of what I get called in for is an app that was built cheaply, shipped, and then cost more to stabilise than it did to write — memory leaks, unmanaged state, an API called four times where once would do. One engineer who owns the architecture and the release does not hand you that bill later. It is also faster in practice, because there is no layer between the person deciding and the person typing. Where an agency genuinely wins is scale: several engineers, a project manager, a design team. If that is the shape of the work, hire the agency.
- Is your recent work current, or is this a CV of old projects?
- Current. The five App Store releases are from 2026, and browser-execution-runtime — an MIT-licensed TypeScript runtime for driving browsers from AI agents — is something I am maintaining now, not a finished portfolio piece. Mobile work has changed considerably in the last two years, particularly around on-device inference, streaming APIs and what App Review will accept from an AI feature. I would rather be judged on that than on a five-year total.
- When are you not the right hire?
- If you need someone on-site, if you are optimising for the lowest possible hourly rate, or if you need agency scale — several engineers, a project manager, a design team. I work as a senior individual contributor or a tech lead, and I do not run an agency. Saying so early saves us both a call.
Contact — AI Product Engineer — Mobile
Build it for the phone people actually have.
Open to senior mobile roles and contract work — remote
If you are putting an AI feature in front of real users, building a new app, or dealing with one that is not stable, message me.
System / stable

