Three engagements 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.
Most projects fail in the gap between “what we're shipping” and “why we're shipping it.” This is how I close that gap.
Listen first. Map the user, the constraints, the unfair advantage. Define what 'great' looks like before writing a single line.
Architect for the second release, not the first. Draft systems, name primitives, and decide what to leave out — that's where the elegance lives.
Ship in surgical increments. Tests, instrumentation, and reviews baked in — never bolted on. Velocity comes from confidence, not corner-cutting.
Measure, profile, refine. Every release should be faster, leaner, and quieter than the last. Performance is a feature.