Frequently
asked questions.

Full-time software engineering roles where mobile is the centre of gravity — cross-platform teams on Flutter or React Native, native Android teams, and full-stack roles where a mobile surface is part of the product. I'm currently Software Engineer II at iMumz in Bangalore. Titles matter less than the work: I want to own product surfaces end to end, not just tickets. Send a note with the role and I'll reply within 24 hours.

Yes — I'm based in Bangalore, India, on IST (UTC+5:30). That gives a natural overlap with European mornings and with the US West Coast at the start of my day. I've worked with distributed teams across Slack, Zoom, and Jira, and I'm used to writing things down so decisions survive the timezone gap.

Open to discussing it for the right team and role. I'd rather talk through the specifics — location, timing, and what the team needs — than rule anything in or out on a webpage. Start the conversation and we can get concrete.

I'm currently employed, so a start date is something I'll confirm directly rather than post here. Reach out with your timeline and I'll be straight with you about mine.

Mobile first — Flutter and React Native for cross-platform, native Android in Kotlin where the platform demands it. Flutter and Dart are the deepest tool in that kit: day to day that means BLoC, Riverpod, and GetX for state, Clean Architecture, Firebase, Crashlytics, and CI/CD that makes releases boring. React Native when a team is already invested there, and Kotlin (MVVM, Coroutines, Jetpack) where a platform channel is the honest answer — I've shipped Kotlin modules bridging Flutter to biometric and document-capture SDKs. Next.js, React, TypeScript, and Node.js are the supporting half — enough to build and ship the web side of a product, including this site. See the full background.

4+ years of production Flutter, not tutorials. Architecture decisions that had to survive a second and third release, state-management migrations on live codebases, performance profiling on real devices, platform-channel work, and release pipelines to both stores. It's the deepest tool I have, not the whole of it — React Native covers cross-platform work where a team is already invested there, and native Android in Kotlin is where I drop when the platform demands it. I also write about it — see the engineering blog for how I think about the trade-offs.

20+ shipped products across 4+ years, reaching 100K+ users. At iMumz I work on a pregnancy and parenting app at real consumer scale. Before that: Bijak, an agricultural supply-chain platform, and iBind Systems. Earlier work at Queppelin and Samsung. Full case studies here.

I ask about the user and the constraints before I write code, architect for the release after the one in front of me, and ship in increments small enough to review honestly. I review pull requests properly, instrument what I build, and write the doc nobody asked for when a decision is going to outlive the sprint. I'm comfortable inheriting a legacy codebase — a lot of my best work has been on someone else's.

The contact page — email, or book a call directly. I read everything that comes in and reply within 24 hours. If you're screening for a specific role, send the description; it makes the first conversation far more useful for both of us.