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
Owned the Flutter platform end-to-end for India's leading pregnancy app. Refactored to BLoC, added Crashlytics, and shipped an A/B testing pipeline that lifted engagement.
iBind Systems
Architected two enterprise KYC apps with Clean Architecture and BLoC. Multi-step verification, OCR pipelines, and 85% test coverage to clear financial audit standards.
Bijak · Mobile Engineer
Shipped 15+ features across three marketplace apps connecting farmers, traders and brokers. Migrated state to GetX and built a reusable component library that doubled delivery speed.
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.