Apply Edge Start your job search

Mobile Lead – AI-Native Care Delivery Applications

Azodha · Pune Division, Maharashtra, India

Apply & track with Apply Edge

Role: Mobile Lead – AI-Native Care Delivery Applications

Location: Pune / Remote (with overlap) Mode: Full-timeAbout AzodhaHealthcare is no longer confined to hospitals—it’s happening in homes, in transit, and in real time.

The systems supporting this shift haven’t kept up.Azodha is addressing that gap.We coordinate workflows, logistics, and care delivery across fragmented systems into a single, real-time layer. Mobile is where a lot of this actually comes to life—especially for clinicians in the field and patients outside traditional care settings.What this role is really aboutYou’ll be shaping mobile systems that people rely on while delivering or receiving care—not in ideal conditions, but in the real world.That means:Unreliable networks.Time-sensitive workflows.Interfaces that need to work quickly and clearly, every time.This isn’t about building consumer apps or pixel-perfect screens.It’s about making sure:A clinician can do their job without friction.A patient can engage with care without confusion.The system holds up when it actually matters.You’ll also define how mobile engineering is done here—architecture, quality, and how the team approaches problems.What you’ll work onMobile systems that work in the real world.Build and evolve applications using Flutter (Dart).Work across iOS and Android fundamentals where needed.Design mobile architecture that scales and remains maintainable over time.Performance and reliability where it mattersOptimize for responsiveness across devices, OS versions, and network conditionsEnsure stability in environments where failure isn’t acceptableHandle edge cases that don’t show up in ideal testing conditionsAI as part of the mobile experienceIntegrate AI-driven capabilities into mobile workflowsEnable context-aware interactions and decision support at the point of careThink through how intelligence shows up on small screens—clearly and usefullyConnected systems, not isolated appsIntegrate deeply with backend APIs and distributed systemsEnsure reliable data flow between mobile, backend, and web platformsHandle sync, offline scenarios, and real-time updates thoughtfullyQuality that survives productionImplement testing strategies across unit, widget, and integration layersWork with CI/CD pipelines for reliable builds and releasesMaintain consistency and reliability across environments=Leadership & OwnershipSet direction for mobile architecture and engineering practicesDefine standards for performance, reliability, and maintainabilityMentor engineers and help them grow in both technical depth and ownershipDrive clarity in ambiguous problem spacesCollaborate closely with backend, frontend, product, and design teamsTake ownership of outcomes—not just deliveryWhat you’ll influenceHow clinicians interact with systems in the fieldHow patients experience care outside hospital environmentsMobile architecture and engineering standardsHow AI shows up in real-world, mobile-first workflowsWhat we’re looking forStrong hands-on experience with Flutter (Dart) and cross-platform developmentExperience building and scaling production-grade mobile applicationsSolid understanding of mobile architecture, performance, and system integrationComfort working with APIs, distributed systems, and real-time dataExperience dealing with edge cases like offline mode, sync, and unreliable networksExposure to AI-driven applications is a plusExperience mentoring engineers or leading mobile effortsAbility to operate in fast-moving, ambiguous environmentsWhy this is worth your timeYou’ll work on mobile systems used in real-world care delivery—not demosThe constraints are real, and solving them well mattersYou’ll have ownership over how the system behaves in the fieldYou’ll work at the intersection of mobile, AI, and healthcare operationsYou’ll shape both the product experience and the mobile engineering cultureIf you’re looking for:Consumer-style apps with predictable usage → this isn’t itPerfect conditions and clean abstractions → also not it