Three roles that frame the rest. Each one ships a system, not a feature — and each one ran longer than the original brief because the work mattered.
iMumz · Software Engineer II
Lead mobile engineer across iMumz's HealthTech suite — the pregnancy app used by 100K+ mothers and a fertility product built 0→production in 3 months for 2,500+ couples. Launched a 15-doctor consultation platform and re-architected imumz.com on Next.js for 38K+ monthly organic visits.
iBind Systems · Software Engineer I
Designed a config-driven KYC routing engine on a unified JSON schema spanning 6+ countries, and built native Android modules bridging Flutter to biometric and document-capture SDKs. 85% unit and 60% widget coverage; 97% first-attempt verification success.
Bijak · Software Engineer I
Built the Agent and Broker apps from 0→1 — real-time area analytics, comparable-sales filtering, and bulk commodity trading with automated brokerage-fee calculation. Shipped 15+ features across three marketplace apps and migrated the flagship from BLoC to GetX.
The engineering habits I bring to a team — ownership past the first release, quality that holds at scale, and a bias for shipping over process.
I take a feature from ambiguous spec to instrumented release and stay with it past launch — measuring, fixing, and iterating rather than handing off at merge.
Flutter shipped to 100K+ users across 20+ products. State management, performance budgets, crash-free rates, and release discipline are muscle memory, not afterthoughts.
Mobile is the core — Flutter and React Native for cross-platform, native Android in Kotlin where the platform demands it. Next.js, TypeScript, and Node cover the surfaces around it. I can own the app and still be useful across the stack.
Fewer meetings, sharper reviews, releases that go out on a Friday afternoon. I optimize the work, not the process around it.