React Native Developer

Responsibilities

• Build features in React Native and TypeScript for iOS and Android. Keep components small enough to review.
• Set up stacks, tabs, and deep links in React Navigation, and add a fallback when one platform behaves differently.
• Call REST and GraphQL APIs. Handle a slow or dropped connection. Keep server data separate from UI state.
• Add a native module in Swift or Kotlin when JavaScript cannot reach the device API.
• Make the app faster on a mid-range phone: bundle size, long lists, gestures, and startup.
• Test the paths that block a release, review other people's code, and write down a decision later releases will depend on.
• Help with Play Store and App Store releases: signing, the build, and the checklist before submit.
• Work with product, design, and backend until a rough requirement is something you can ship.

What helps you succeed

• 0–2 years with React Native and TypeScript, on a shipped app or a project you can open and walk through.
• You know hooks, state, and effects, and you have already hit the limits of running React on a phone.
• You have called REST APIs and handled loading and errors without putting server data in every component.
• You have debugged on a real phone and on a simulator, for both iOS and Android.
• You check text size, contrast, and layout on both platforms before you call a screen done.
• You can write a short note that says what you changed and what you left out.

Useful, not mandatory

• You have shipped with Expo, EAS Build, or Fastlane.
• You have used Firebase or Supabase, including push notifications, or you have built offline sync.
• You have used Reanimated, FlashList, TanStack Query, Zustand, or Redux Toolkit.
• An app you worked on is on Google Play or the App Store, or you can point to your commits on a shipped React Native app.

Work eligibility

Candidates must have the legal right to work in India. Confirm eligibility in your application.

Confirmed benefits

• Fully remote, and you do not need to be online all day
• A budget for courses, books, and conferences on mobile engineering
• The work ships. It is not a prototype that gets thrown away
• You get feedback on the code, and you can take on more of a feature as you go