- Are you open to research collaboration with professors or universities?
- Yes. I am most useful when a research question also needs serious software: an experiment platform, a data pipeline, a reproducible prototype, or a path from a paper idea to something people can test.
- Are you looking only for full-time roles?
- No. I consider full-time roles, consulting, focused contracts, and founder or research collaborations. The common requirement is clear ownership and a problem substantial enough to justify doing the work properly.
- Do you mentor or speak?
- Yes. I am open to mentorship, tech talks, workshops, speaking opportunities, and conversations that create value for engineering communities or academic circles.
- Which kinds of teams benefit most from working with you?
- Teams that need someone who can move between architecture, implementation, debugging, AI integration, and platform thinking without losing delivery momentum.
- How do you usually start an engagement?
- By finding the real constraint, which is often not the one in the brief. A short read of the system, the data and the failure history, then a written view of what is actually expensive and what I would change first. That is useful on its own even if the work stops there.
- What does a realistic AI project look like with you?
- One workflow, one owner, one number it has to move. Grounded retrieval over sources you already trust, visible uncertainty, and a clear boundary on what the system decides alone. Demos are easy; the gap between a demo and something a team can operate is most of the job.
- Do you work with existing codebases or only greenfield?
- Mostly existing ones. The interesting problems are in systems that already work and have outgrown their first design — a Lambda path that got expensive, a monorepo nobody wants to touch, a query that quietly became the bottleneck.
- How do you handle handover?
- As part of the work, not as a final phase. Documentation, the reasoning behind the trade-offs, and enough tests that the next engineer can change things without being afraid. A system the team cannot operate without me is not finished, it is borrowed.
- What are your rates, and how do you scope?
- It depends on shape rather than hours: a review is a fixed scope, an implementation is a milestone, an ongoing advisory is a retainer. Tell me the constraint and the deadline and I will tell you what is realistic — including when the honest answer is that I am not the right person.
- Where are you based, and how do you work with time zones?
- Pakistan, working with teams across Europe and North America. I keep a real overlap window rather than promising full coverage, and I write things down so progress does not depend on catching me live.