Frequently
asked questions.
What hiring teams ask first — the roles I'm after, how I work, and how deep the stack goes. If yours isn't here, send it through and I'll answer in person.
Roles & availability
What kind of roles are you open to?
Full-time Senior Mobile Engineer roles focused on Android, Kotlin, Flutter and product ownership. Most recently, I was Software Engineer II at iMumz in Bengaluru, from June 2024 to September 2026. I'm available immediately. I want to own product surfaces end to end and help a mobile team ship reliably. Send a note with the job description and your hiring timeline.
Do you work remotely, and what hours do you overlap?
Yes — I'm based in Bangalore, India, on IST (UTC+5:30). Let's agree on working hours and the overlap your team needs. I use written decisions and clear handoffs to keep work moving across timezones.
Are you open to relocation?
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.
When could you start?
I'm available immediately. My most recent role at iMumz ended in September 2026. Reach out with the role and your hiring timeline so we can discuss the details.
Tech depth
What's your primary stack?
Flutter and Dart are my deepest production stack: BLoC, Riverpod, GetX, Clean Architecture, Firebase, Crashlytics and release pipelines. My native Android work includes 3+ Kotlin modules using MVVM, Coroutines and Jetpack, bridging document-capture and biometric SDKs to Flutter through MethodChannels and EventChannels. Next.js, React, TypeScript and Python support the web and backend sides of my products. See the iBind architecture decisions and full toolkit.
How deep does the Flutter experience actually go?
5 years of production mobile engineering, with Flutter as my deepest tool. 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. 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.
What I've shipped
What have you built?
5 years of production engineering. At iMumz, I worked on a pregnancy and parenting platform with 1M+ Android downloads, 60K+ monthly active users and 15K+ daily active users. Before that: Bijak Mandi, with 500K+ Android downloads and 100K+ verified traders, and iBind Systems, building KYC workflows for clients including Emirates and HDFC. Independently, I built PulseSync, a Flutter/Riverpod health-tracking product for 250+ users with Android Health Connect and Apple Health integrations. Full case studies here.
How I work
How do you work inside a team?
At iMumz, I led technical planning and architecture reviews for four mobile engineers, conducted 250+ PR reviews and mentored two engineers toward independent feature ownership. I use observability to prioritize reliability work and explicit feature boundaries to make changes reviewable. The iMumz case study shows those decisions in context.
What's the best way to reach you?
The contact page — email, or book a call directly. If you're screening for a specific role, email the job description, team context and hiring timeline. You can also use the optional email starter or schedule a call.