Senior Flutter Engineer

Senior Flutter EngineerMangaluru, Karnataka | Onsite | Full-timeAbout the roleDelivery at Synterra is organised into small, senior pods who own a client outcome end to end: scope, architecture, delivery, quality, and production. AI coding agents are an integral part of the delivery workflow, and much of the implementation is agent-generated. The value of this role lies in the work that surrounds generation: decomposing ambiguous business problems into buildable specifications, making architectural decisions, directing agents against those decisions, and ensuring that everything shipped to both stores meets production standards.This position owns the mobile client of a multi-product consumer platform shipped across several regions: app architecture, state management conventions, performance budgets, offline behaviour, release engineering, and a security posture that withstands VAPT review. The role is problem-driven rather than ticket-driven. Most engagements are delivered on fixed-price, fixed-timeline terms, so scoping and estimation quality has a direct bearing on project outcomes. The emphasis throughout is on engineering judgment, with particular weight on mobile-specific constraints: a client that cannot force users to upgrade, and store review processes that sit between the team and every release.AI-augmented delivery: expectations•    AI coding agents are used daily as a core part of delivery. The critical skills are the specification that goes into generation and the review that follows it.•    Full ownership is expected for all code shipped under this role, regardless of how it was produced. Accountability for correctness, security, and maintainability rests with the engineer, not the tool.•    A key competency is identifying code that appears correct but is not: output that compiles, renders on the happy path, and yet conflicts with framework fundamentals, introduces security exposure, or degrades at scale. On mobile this includes generated layouts that fight Flutter’s constraint model, rebuild-heavy widget trees, and state handled in places it does not belong.•    All AI-assisted work is expected to be fully explainable and debuggable by the engineer who ships it.Key responsibilities•    Outcome ownership: scoping, architecture, agent-directed implementation, review, testing, store release, and post-release monitoring for mobile features, delivered end to end.•    App architecture and conventions: layering, state management, dependency injection, modularisation, and business logic kept out of the widget tree, so that generated code lands within a coherent system rather than accumulating as one-off structures.•    Performance budgets: startup time, frame rendering, memory, and app size defined, defended, and verified through profiling rather than assumption.•    Offline and sync behaviour: local persistence, conflict handling, background refresh, and behaviour that degrades sensibly on poor connections.•    Release engineering: signing, versioning, flavours, staged rollouts, crash and error monitoring, and predictable passage through store review.•    Security posture: built to withstand security review, with VAPT findings triaged and closed. Generated code is treated as an additional review surface for security.•    API boundary: shaping the contract with the back end, and flagging API designs that would be costly on a client that cannot force users to upgrade. Multi-region configuration and localisation handled without forking the app.•    Review, mentoring, and standards: pull requests and agent output reviewed with the same rigour; mentoring of junior engineers within the pod; conventions and reference patterns documented for wider team use; collaboration with design on handoff, design-system fidelity, and QA.•    Scoping and estimation: estimates prepared with care and stood behind, given the direct relationship between scope quality and commercial outcomes on fixed-price work.Required skills and experience•    Framework depth: deep production Flutter and Dart experience on apps shipped and maintained on both the App Store and Play Store, including signing, versioning, and store review.•    Understanding beneath the API surface: the constraint and layout model, the rendering pipeline, rebuild behaviour, and the widget, element, and render-object relationship. Review quality at this level is what distinguishes the role, since this is where generated code most often looks right and behaves wrongly.•    State management command: BLoC, Riverpod, Provider, or similar, with a clear view of when each is appropriate and where state belongs.•    Architecture at scale: business logic separated from UI, dependency injection, feature modularisation, and conventions that hold up as a team grows.•    Performance profiling: diagnosing jank, unnecessary rebuilds, excessive layout work, and memory leaks with Flutter DevTools.•    Offline engineering: local persistence and offline-capable apps, with a credible approach to sync and conflict resolution.•    Secure mobile development: the OWASP Mobile Top 10 in practice: secure storage of tokens and keys, certificate pinning, secrets kept out of the binary, and comfort triaging and fixing VAPT findings.•    Native reach: platform channels and native Android or iOS code where no plugin exists.•    Breadth of fundamentals: HTTP, state, data modelling, concurrency, and security fundamentals strong enough to review work at the API and data layer the client consumes. Pods are small, and review responsibility extends across adjacent layers. This includes versioned contracts, retries and backoff, caching, pagination, auth and token refresh, and real-time connections that survive backgrounding.•    Accessibility and internationalisation: semantics, contrast, dynamic type, screen reader support, and internationalised layouts that hold up across languages.•    Testing: unit and widget tests as part of normal delivery, with clear judgment on what is worth integration testing.•    Independent execution: the ability to take an ambiguous requirement, clarify what is actually needed, document it clearly enough for others (or agents) to execute, and deliver without close supervision.Good to have•    CI/CD for mobile: Codemagic, Fastlane, or GitHub Actions, including automated store deployment.•    Code obfuscation, root and jailbreak detection, and tamper protection.•    Data privacy in practice on mobile: consent and permission flows, minimal collection, accurate store privacy declarations (Play Data Safety and Apple App Privacy), auditing of third-party SDKs, and support for account deletion and data export; familiarity with GDPR and India’s DPDP Act.•    Push notifications, deep linking, crash reporting, analytics, and feature flags or remote config.•    In-app purchases, subscriptions, or payment SDK integration.•    Building or maintaining a design system and shared widget library across features.What the role offersCompetitive salary based on experience, direct ownership of technical decisions on the mobile client, fast delivery cycles supported by AI-augmented workflows, and a small senior team environment where engineering judgment is the primary contribution.How to applyPlease send a resume along with links to careers@synterrait.com shipped apps, store listings, GitHub, or both.