Mobile App Developer
Location: New Delhi (Work from Office)
Experience: 3–5 Years
Employment Type: Full-time
Who We Are:
PanScience Innovations is India's largest deep-tech and AI venture studio. Rather than investing in companies from the outside, we co-found them: we originate the idea, embed a team from day one, and build out the product, technology, go-to-market, operations, finance, and legal functions alongside each venture's core team. We've co-founded 24+ ventures across healthcare, finance, judiciary, media, and industrial AI, and our role is to take deep science that would otherwise stay in a lab and turn it into a company that can stand on its own.
Who you'll Work with:
You'll be looped into multiple portfolio ventures rather than sitting inside just one, working closely with each venture's product and engineering leads and PanScience's central studio functions. You won't be one mobile developer among many on a large team; you'll often own the mobile experience end to end for a venture, and you'll draw on the studio's shared design, backend, and QA resources when you need them.
What you'll Do:
- Design and build production-grade cross-platform apps in Flutter, taking a feature from a wireframe or a rough idea through to something real users rely on daily.
- Own the app end to end: architecture, state management, navigation, offline behaviour, and performance, not just the screens that are easiest to build.
- Integrate with REST/GraphQL APIs and backend services, and work directly with backend engineers to shape contracts rather than just consuming whatever is handed to you.
- Write code that another engineer can pick up without you in the room: clean architecture, sensible state management (Bloc, Riverpod, or Provider), and tests that actually catch regressions.
- Ship to the Play Store and App Store yourself, including release builds, versioning, crash monitoring, and the small platform-specific details that separate a working app from a polished one.
- Chase down performance issues and jank instead of accepting them as normal, whether that's a slow list, a memory leak, or a startup time that's crept up over releases.
- Push back on scope and native-plugin shortcuts that will cost the team later; protecting app stability and maintainability is part of the job, not a side effect of it.
What you should Bring:
- 3-5 years of mobile development experience, with at least 1-2 years building and shipping production Flutter apps that are live on the Play Store and/or App Store today.
- Minimum Qualification: Bachelor's degree in Computer Science, Engineering, or a related field (or equivalent practical experience).
- Strong command of Dart and Flutter fundamentals: widget lifecycle, state management, custom animations, and platform channels for native integrations.
- Working knowledge of native Android (Kotlin/Java) or iOS (Swift) development, enough to debug platform-specific issues Flutter can't fully abstract away.
- Comfort with the full app lifecycle: CI/CD for mobile, app store submissions, crash reporting (Firebase Crashlytics or similar), and analytics instrumentation.
- Solid grasp of REST/GraphQL integration, local storage (SQLite/Hive/Isar), and secure handling of auth tokens and sensitive user data.
- Comfort moving with limited structure, and a willingness to set up the tooling, conventions, and CI pipeline yourself rather than waiting for someone to hand it to you.
Good to Have:
- Experience integrating on-device ML (TensorFlow Lite, ML Kit) or real-time features (sockets, push notifications, background sync).
- Exposure to native module development in Kotlin/Swift, or prior experience with React Native, for comparison and migration decisions.
What Success Looks Like:
Within your first few months, you should have shipped at least one release to production that meaningfully improved a real metric — crash-free rate, load time, retention, or a feature adoption number — and be able to explain plainly what changed and why. Longer term, success means the venture's mobile app is something the team trusts you to own: fewer surprises in production, and a codebase the next engineer can actually build on.