Flutter Mobile Developer

We are hiring a Flutter Mobile Developer to own the mobile side of our products. You will start on the travel booking apps that sit on top of our B2C and B2E platforms, then extend into Omni Channel and HR. Features are yours end to end: from the Figma handoff, through state management and integration with our .NET APIs, to the build that lands on the App Store and Google Play.

• Build and ship cross-platform features in Flutter, one codebase for iOS and Android.
• Integrate with our .NET REST APIs — auth, pagination, caching, and behaviour that survives a bad connection.
• Own the app's architecture and state management, keeping business logic testable and out of the widgets.
• Turn Figma designs into pixel-accurate, responsive layouts that hold from small phones to tablets.
• Ship full Arabic RTL support beside English: mirrored layouts, fonts, and number and date formatting.
• Keep the release pipeline healthy on Codemagic — signing, versioning, and store submissions.
• Instrument crash reporting and analytics, and act on what they show instead of waiting for bug reports.
• Review pull requests and hold the codebase to the team's conventions.

• 5+ years building production Flutter apps, with at least one live on both the App Store and Google Play.
• Strong Dart: null safety, async/await and streams, and isolates where they actually earn their keep.
• A state-management approach you can defend (Bloc, Riverpod or Provider) and clean separation between layers.
• Comfortable with REST APIs and real-world failure: timeouts, retries, token refresh, and conflicting writes.
• Native fluency where Flutter stops: platform channels, permissions, push notifications, and deep links.
• Local persistence and sensible caching (Hive, Drift or SQLite, and secure storage for anything sensitive).
• Git, code review, and release discipline — you can take a build from branch to store without hand-holding.
• Working English. Arabic is a strong plus given how much of the RTL work lands on mobile.

• Travel or booking domain experience — flights, hotels, GDS/NDC, or payment flows.
• Mobile CI you configured yourself, not only used: Codemagic, Fastlane or similar.
• Widget and integration tests, plus golden tests to catch UI regressions before review does.
• Firebase (Crashlytics, Remote Config, Cloud Messaging) or an equivalent stack.
• Published Flutter packages or contributions to open-source plugins.

Mobile is not a downstream team here. You sit with the backend and web engineers who own the same product, so the shape of an API and the needs of the app get settled together rather than handed over. Work runs in short cycles that end in a real release, code review is the norm rather than a formality, and whoever builds a feature is the one who watches it in production.