Flutter Developer

Job highlights

• 4+ years Flutter mobile frontend experience with released apps on Google Play and App Store, ownership of Flutter codebase, production Python shipped, expertise in Flutter architecture, Riverpod/Bloc state management, go_router routing, dio networking with 401 refresh mutex, native Kotlin/Swift integration, on-device security including flutter_secure_storage, offline-first encrypted local stores, codegen tooling, performance profiling, and golden testing

• Design and maintain Flutter apps including architecture decisions, state management, routing, networking, native platform integration, app lifecycle handling, security and storage, performance optimization, and comprehensive testing

• 4+ years building production mobile frontends, the majority of it in Flutter.

• At least one Flutter app has been released on both Google Play and the App Store.

• Nameable and linkable, with your specific contribution stated.

• Enterprise/internal distribution counts only if you own signing, release builds and rollouts.

• You have owned a Flutter codebase over time, not just built screens in one.

• Architecture decisions, dependency upgrades, Flutter/Dart SDK migrations, tech-debt paydown.

• Production Python you have shipped and maintained.

Flutter / Dart the core of this role

• Architecture

• Feature-first layering with an enforced boundary between presentation and data.

• Reasoned opinion on why a domain layer is or is not worth its mapping cost.

• Shared internal packages consumed by more than one app, with per-app flavors, build config and entrypoints.

• State management and DI

• Riverpod (AsyncNotifier / AsyncValue, per-screen controllers) — or Bloc/Provider plus a coherent argument for the difference.

• Must cover dependency injection, not just state.

• Correct loading / data / error modelling without boolean flag soup.

• Routing

• go_router — declarative routes, redirect and guard chains evaluated in order, deep-link and URL parsing.

• Must be able to reason about a guard failing mid-chain, with the original destination held and replayed after the block clears.

• Networking

• dio interceptor chains — header attach, error mapping, jittered retry/backoff, 401 refresh-and-replay.

• Must be able to explain why concurrent 401s require a single-flight refresh mutex, and exactly what breaks without one.

• Multiple client profiles in one app, where some requests must never trigger a token refresh.

• Push notification plumbing — FCM/APNs, token rotation on reinstall and OS restore, data-only vs notification payloads.

• Native integration — Kotlin and Swift you personally wrote

• Plugin consumption alone is not sufficient.

• FLAG_SECURE and the iOS screen-capture listener, App Attest, Play Integrity, keystore delegation, certificate pinning.

• Comfortable debugging inside Android Studio and Xcode when the Dart side is not where the bug is.

• App lifecycle and process death

• inactive vs paused vs detached, what each means on Android vs iOS, and what survives each.

• Restoring a multi-step journey after the OS kills the process, and knowing what must not be restored.

• On-device security and storage

• flutter_secure_storage Keychain/Secure Enclave and Android Keystore (StrongBox/TEE); local_auth biometrics.

• Must know what isHardwareBacked == false implies and why it is a hard block rather than a warning.

• Discipline about what may never touch SharedPreferences/NSUserDefaults, disk, or a log sink.

• Offline-first mobile — encrypted local stores, TTL enforcement by key destruction, sync reconciliation.

• Codegen and tooling

• build_runner, json_serializable, freezed; keeping generated output non-drifting in CI.

• flutter analyze on a strict lint set, and treat analyzer warnings as build failures.

• Performance

• Profiling with DevTools; jank diagnosis; memory behaviour when rendering large documents page by page.

• Long list performance with hundreds of cached items.

• Testing

• Widget tests, golden tests, integration_test.

• Deliberately testing process-death and resume paths, not just happy paths.