NOTE:

This is a 01 role, with the responsibility that implies: there is no mobile team today and no playbook - you make the architecture calls, you ship, and you own what happens in production. If you've been waiting for scope you didn't have to ask permission for, this is that role.

What we're looking for
- 3+ years building mobile apps, including at least two you shipped to both the App Store and Google Play and kept alive through updates and re-reviews.
- Solid React Native and TypeScript. Enough Swift and Kotlin to write a native module, debug a platform crash, and read Apple/Google docs without fear.
- You've been through App Store review you know the common rejections (wrapper minimum-functionality, permission prompts, payment rules) and design around them before submitting.
- You own outcomes, not tickets:



you'd rather ship a smaller thing to production than a bigger thing to staging.
- Clear written communication much of our coordination is async.

Nice to have
- Capacitor or Trusted Web Activity experience our current Android app is a TWA, and you'll be the one to retire it.
- Care for detail on the small things users feel: loading states, offline behaviour, keyboard handling, accessibility.
- Expo EAS (build / update / submit) in production.
- Firebase phone auth and FCM; Razorpay or other payment SDKs.
- Next.js familiarity the web app is where the product lives today.
- Healthcare or another regulated domain.
- Bonus: Expo EAS, Firebase, Razorpay, or a healthcare / consumer-services background.

📌 Founding Mobile Engineer (Pune)
🏢 Curoclan
📍 Pune