Mobile Engineer, React Native

Our mobile work runs from consumer travel products to field apps for logistics clients: offline maps, drivers tapping a screen in the rain, and performance problems that only appear on the cheapest phone in the fleet.

You'd own the mobile codebase on an engagement, with a designer and a backend engineer beside you, and take the app through review, release and the first months of real ratings.

React Native with Expo by default, native modules when the bridge isn't enough and someone has to go in.

Agents handle the scaffolding, the platform boilerplate and the third rewrite of a config file for store review. Your attention goes on the parts where the app either feels right or doesn't.

• Own the codebase. Architecture, navigation, state, and all the small decisions that add up to how the app feels.
• Get it through review. Both stores, including the rejection nobody warned you about, twice.
• Build the release machinery. EAS builds, over-the-air updates, crash reporting, staged rollouts you can stop halfway.
• Chase the feel. Work with the designer on motion and gesture detail, the difference between an app and a website in a shell.
• Handle reality. Offline state, background sync, permissions, battery, and the device with 200MB free.

• Four Years Mobile, Two in React Native: shipped to both stores, with the version history to prove it.
• React Native and Expo: managed and bare workflows, and the reasons you'd leave one for the other.
• TypeScript on Mobile: typed navigation, typed API clients, and nothing loose at the boundary.
• Release Machinery: EAS or Fastlane, code signing, TestFlight and staged rollouts you have run yourself.
• Offline and Sync: local storage, optimistic updates, and conflicts resolved without losing someone's work.
• Push and Deep Links: notifications, permission prompts, and links that open the right screen from a cold start.
• Crash Loop Closed: Sentry or Crashlytics wired up, and the habit of reading it on Monday morning.
• Store Review Veteran: you know the common rejections and how to avoid collecting them.
• Native When Needed: comfortable dropping into Swift or Kotlin for a module or a platform bug.
• Performance on Real Devices: startup time, list rendering, memory, and why the animation stutters on exactly one phone.
• Tests on Hardware: the simulator is a rehearsal, not the performance.
• Client Calm: you can explain an app store delay to a client without either panic or jargon.
• Fluent English, Written and Spoken: most of our work happens in a written thread or on a call, and both have to be clear. Arabic is a genuine advantage across the region.
• AI in the Loop: agents handle your boilerplate while you keep hold of the parts that decide how the app feels.

• Detail-obsessed: a 60ms jank annoys you personally.
• Patient: store review timelines can't be argued with, only planned around.
• Self-sufficient: you're often the only mobile person on the engagement, and that suits you.

• Maps: Mapbox, MapLibre, offline tiles that behave in a tunnel.
• Consumer apps with public ratings you're happy to point at.
• App analytics, and knowing what to do with what they say.

• Remote across MENA. Work from wherever you are in the region, with hours built around your team's overlap rather than someone's attendance spreadsheet.
• Work that ships. Products go live in weeks, not quarters. When someone asks what you have been building, you can open it on your phone and show them.
• Small teams, no ticket queue. Four to eight people carry a product from the first client call to handover. Nobody hands you a spec and disappears.
• Kit and tools you choose. A budget for your setup, and for the editor, licenses and services that make you fast. No three-week procurement saga.
• A learning budget with time attached. Money for the course or the conference, plus room in the week to use it. The second half is the part most places skip.
• Client contact from day one. You sit in the room where the decisions get made. Plenty of engineers wait a decade for that seat.
• Time off people take, and no timesheets. We measure engagements, not humans in fifteen-minute increments. Book the holiday, go, come back.