All jobs
RemoteListed Jul 19, 2026

Mobile Lead Engineer (React Native) - US-based

Curotec

  • IOS-Android-Development
  • Lead-Mobile-Developer
  • Lead-Mobile-Engineer
  • Mobile-Engineering
  • Mobile-Engineering-Lead
  • Mobile-Engineering-Team-Lead
  • Mobile-Software-Engineer-Lead
  • React-Native-Development
  • React-Native-Technical-Lead
  • Senior-React-Native-Mobile-Developer
  • Software-Engineering

Assessed from original listing evidence

The role

Job description

Our client is looking for a Mobile Lead Engineer for a project focused on a cross-platform React Native app (iOS and Android) that discovers, pairs with, and controls BLE hardware.

  • Native module integration: wiring a vendor-supplied Bluetooth SDK into React Native and handling the bridge cleanly
  • Cross-platform BLE identifier handling, where iOS exposes a per-pairing UUID and Android exposes the MAC address directly
  • Lock and unlock flows with hard timing constraints (sub-second response, short connection and validation windows)
  • Over-the-air firmware updates to connected devices
  • Offline-first behavior: a pending-action queue that syncs when the device reconnects
  • Secure credential storage (iOS Keychain, Android Keystore), biometric auth, NFC, and QR-based device registration
  • Real-time device status: battery, firmware version, connectivity state

Requirements

Must-haves:

  • Strong production React Native experience, with apps you've shipped to the App Store and Google Play
  • Comfort writing or integrating native modules (Swift/Kotlin) when the JavaScript layer isn't enough
  • Solid grasp of mobile state management, async flows, and the realities of debugging on physical devices rather than simulators
  • The instinct to handle edge cases and failure states up front, not after QA finds them
  • Fluent English and availability during US Eastern business hours

Big pluses:

These aren't required, but they move a candidate to the top of the list:

  • Bluetooth Low Energy (BLE) experience. Direct, hands-on work with BLE in a mobile app. If you've fought with connection timeouts, GATT services, pairing quirks, or platform identifier differences, say so.
  • IoT apps in your portfolio. Apps that control or communicate with physical hardware. Tell us what the device was and what your app did with it.
  • B2B / enterprise app experience over consumer apps. We'd rather see a multi-tenant admin tool, a field-operations app, or a hardware companion app than a high-polish consumer social app. The user base here is organizations and operators, not the mass market.

Originally posted on Himalayas

Keep exploring