Senior Mobile Developer Onsite

Role Overview

We are currently looking for a Mobile Developer who will be responsible for the correspondence system mobile application— the iOS and Android companion to the Administrative Correspondence System used by client staff. This person will maintain the existing app, deliver prioritized improvements regularly, and implement electronic signature integration with the Client's mobile platform. The mobile app serves Arabic‑speaking government users, so RTL layout, accessibility, and usability for non‑technical staff are as important as technical correctness.

• Maintain the existing mobile application on both Android and iOS, keeping it stable, performant, and aligned with SLA requirements.
• Deliver new mobile features prioritized in release backlogs, improving the correspondence workflow, notifications, dashboards, and user experience.
• Implement the electronic signature integration with the Client's mobile platform as per contractual requirements.
• Ensure the mobile app stays functionally aligned with the correspondence system web portal (feature parity where required by client stakeholders).
• Keep all mobile frameworks, libraries, and dependencies on LTS‑supported versions throughout the contract – this is a contractual obligation.
• Perform mobile‑specific testing: device and OS compatibility across the range of devices end users operate, performance under low connectivity, security validation.
• Coordinate closely with the .NET Core backend developers to agree on API contracts before developing new features.
• Produce Arabic mobile release notes, update logs, and user‑facing documentation for each release.

• Fluent Arabic speaker is a must.
• Bachelor's degree in Computer Science, Software Engineering, or equivalent.
• 5+ years of professional mobile development experience with iOS and Android deployment.
• Production‑level experience with React Native or Flutter in enterprise or government applications.
• Experience integrating mobile apps with REST APIs in secure enterprise environments.
• Experience with government or enterprise apps;
  Arabic RTL interface experience strongly preferred.

• React Native or Flutter cross‑platform mobile development; production‑level competence in at least one; knowledge of both is preferred.
• iOS and Android native fundamentals: ability to investigate and resolve native‑level issues (crash reports, device‑specific rendering, permissions) even within a cross‑platform framework.
• REST API consumption and integration with .NET Core back‑end APIs; JWT authentication, error handling, retry logic, offline caching patterns.
• Electronic signature integration: familiarity with e‑signature standards (PKCS, PDF signing), mobile SDK integration for digital signing workflows; experience with government e‑signature platforms beneficial.
• Push notifications:
  Firebase Cloud Messaging (Android) and Apple Push Notification Service (iOS); notification payload design, delivery reliability.
• Mobile security: certificate pinning, secure local storage (Keychain / Android Keystore), biometric authentication (Face , fingerprint), OWASP Mobile Top 10 awareness.
• Arabic RTL layout: implementing and testing right‑to‑left user interfaces; handling bidirectional text; this is not cosmetic but essential for usability.
• Deep linking and navigation: complex navigation patterns, push notification deep links, in‑app routing.
• App distribution:
  App Store and Google Play publishing process; or enterprise MDM distribution if the client uses internal distribution.
• Mobile performance optimization: memory management, battery efficiency, network request optimization, list virtualization for large correspondence datasets.
• Git version control: branching aligned with the project’s overall release management process.

• Self‑directed mobile development: manage own delivery, quality, and timeline without close supervision.
• Close collaboration with backend developers: API contracts between the mobile app and .NET Core back‑end must be agreed in writing before development begins; ambiguity causes rework.
• User empathy and UX thinking: the app is used daily by government staff, not technical users; improving usability for Arabic‑speaking non‑technical users is as important as feature delivery.
• Proactive device compatibility awareness: end users may have a wide variety of device types, OS versions, and connectivity conditions; the developer should flag compatibility risks early, not after release.
• Documentation discipline: mobile release notes and update logs in Arabic must be produced for each release, as they feed into contractual project reports.