Senior Mobile Engineer - Flutter

About the role

Flutter is technology. Rural India is the user base. The intersection of those two facts means this role requires both technical depth (performance engineering, offline-first architecture, low-end device optimisation) and the empathy to build software for users who may be accessing the internet for the first time on a low-end smartphone in a village with intermittent connectivity.

Key Responsibilities

Customer App - Technical Ownership

• Own the Customer App architecture - Flutter project structure, state management approach, navigation patterns, API integration layer, and the architectural decisions that will govern the app for the next three years

• Conduct a full technical audit in the first 30 days - document the current state, identify performance bottlenecks, security gaps, offline capability limitations, and technical debt that needs remediation

• Own the app performance budget - define acceptable load times, memory consumption, battery usage, and APK size targets for a rural user on a low-end Android device, and build to those constraints

• Implement offline-first architecture - local data caching, sync strategies, conflict resolution, and the graceful degradation patterns that keep the app functional during connectivity drops

• Own the app release process - Play Store release management, versioning strategy, staged rollouts, and the A/B testing infrastructure for feature experiments

WhatsApp Integration & Lending Flows

• Own the mobile-side WhatsApp integration architecture - how the Customer App and WhatsApp channel share state, handoff flows, and deep link handling for the agentic lending workflows being designed

• Implement the loan application journey in Flutter - the full origination flow from lead capture through KYC, document upload, and application submission; designed for rural users with variable literacy and connectivity

• Build the repayment and EMI management UIs - payment flow, BBPS integration, eNACH mandate management, and the notifications that drive on-time repayment behaviour

• Implement the field officer mobile tools - the screens that field officers use for customer onboarding, visit documentation, and collections activity capture in the field

Rural UX & Performance Engineering

• Build for low-end Android devices that SarvaGram's borrowers use require deliberate performance engineering; this is not a nice-to-have, it is the primary performance constraint

• Design for low-literacy users - icon-first navigation, voice input support, regional language readiness (Marathi, Hindi), and the interaction patterns that work for first-time smartphone users

• Implement progressive loading and skeleton UIs - perceived performance patterns that make the app feel fast even on 2G connections by loading critical content first

• Own crash reporting and real-user monitoring - Firebase Crashlytics, performance monitoring, and the analytics that tell you how real users in rural Maharashtra and Karnataka are experiencing the app

AI-Native Mobile Development & Standards

• Use Cursor / Claude as primary development tools - AI-assisted Flutter development is the engineering standard; widget generation, state management boilerplate, and test writing are AI-augmented

• Design the AI feature integration on mobile - how the WhatsApp AI agent, agentic underwriting flows, and AI-generated personalisation surface in the Customer App UI

• Define Flutter engineering standards for Nexus - code organisation, widget composition patterns, state management approach, testing strategy, and the review criteria that govern all Flutter code

• Mentor the Mobile Engineers - structured development toward ownership of feature domains and eventual independence on production deployments

Professional Experience

• 6 to 8 years in mobile engineering with 3+ years in Flutter - has shipped production Flutter apps with real users and managed the full lifecycle from architecture to Play Store release

• Has engineered for constrained devices and connectivity - has worked on an app where device capability and network quality were genuine engineering constraints, not edge cases

• Has owned mobile architecture decisions in a production app - not just implementing features but making the architectural choices (state management, offline strategy, navigation) that the team lives with

• Active AI tool user - uses Cursor and Claude for Flutter development today; AI-augmented development is standard practice

• Fintech mobile experience is a meaningful plus - payment SDK integration, KYC flows, and bureau API mobile surfaces are common territory

Mindset & Soft Skills

• Rural empathy: Rural user empathy: the app's users are not developers or urban smartphone power users - designs for the actual user, not the imagined user

• Performance obsession: Performance obsession: a feature that works beautifully on a Pixel 8 but is unusable on a Redmi A2 has not shipped for SarvaGram - performance on low-end devices is the acceptance test

• Technical ownership: Technical ownership: 'I inherited this codebase' is not an excuse - audits, fixes, and refactors are the Senior ME's responsibility from week one

• AI-native: AI-native developer: reaches for Claude before writing Flutter boilerplate or writing documentation - AI-augmented mobile engineering is standard, not occasional

Technical Skills

Progressive loading / skeleton UI & Regional language / i18n

Prompt engineering for Flutter code