React Native Engineer

Responsibilities:

• Own the app. Design, build, release, OTA hotfix, and production support. 2 to 3 builds a week; every one of them is yours.
• Own quality. No QA team to hand off to. Jest and React Native Testing Library cover logic and screens. Maestro flows cover the money paths (login, address, prescription upload, cart, payment, tracking) on real low-end Android phones. Tests gate every PR and every EAS build. We rehearse every OTA update on a staging channel before a customer sees it.
• Move the numbers. Install-to-first-order conversion, repeat rate, checkout drop-off, crash-free sessions, cold start. That is your scoreboard, and you check it daily.
• Make the core journey excellent. Search, substitutes, prescription upload, address, cart, payment, live tracking. Fewer taps, clearer states, and no dead ends on an API error.
• Build for everyone who needs medicine. A grandparent on a 5-year-old phone. A parent ordering at 2 am for a sick child. Someone on their first smartphone. Big touch targets, readable type, plain language, regional-language ready, accessibility that actually works with a screen reader.
• Make it fast for everyone. Performance tiers, not one build. Detect device class and network, then adapt: lighter images, fewer animations, smaller payloads on low-end phones and 2G/3G, and the full experience on flagships. Profile on the cheapest phone we support, not your own.
• Get the location right. Addresses and pins must land on the correct door every time. Every delivery promise rests on it. Shape the platform. Backend-for-frontend (BFF) and server-driven UI (SDUI) with the backend team, so screens and offers change without waiting for a release.
• Instrument, then optimize. Session replay, funnels, and crash reporting tell you what actually happens. Act on it the same week. Use AI as a multiplier. Claude Code, Cursor, Copilot, or similar every day, while holding the line on code quality and tests.
• Push back. With product and design, a flow won't convert or will confuse a stressed user. Then help on the store and rider apps when an order's path needs it, and leave every codebase simpler than you found it.

Requirements:

• 3 to 6 years shipping React Native apps that are live on the Play Store or App Store.
• A consumer app you helped grow past 100K active users, where crashes, slow screens, and checkout drop-off had a measurable cost, and you were the one who brought them down.
• Strong TypeScript and a deep grip on React Native: the new architecture, native modules, Reanimated and gestures, navigation, and profiling on real devices. You can explain why a screen is slow and fix it.
• A BFF (backend-for-frontend) layer and server-driven UI you have built or consumed in production. This is a big one: it is how we change screens and offers without a release.
• Observability and event SDKs wired properly: product analytics and session replay (PostHog or similar), crash reporting (Crashlytics or Sentry), and marketing and attribution SDKs such as MoEngage and the Meta SDK, with a clean event taxonomy that growth and ops can trust.
• Expo and EAS, or an equivalent build, release, and OTA pipeline.
• Automated testing as part of the feature, not after it: Jest, React Native Testing Library, and Maestro or Detox on real devices.
• Strong UI/UX sense and real empathy. You can design a flow when there is no mock, and you understand that someone ordering medicine is often anxious, in a hurry, or not fluent with phones. Confusion here is not a bug; it is a missed dose.
• Inclusive design: you can show apps built for elderly, low-literacy, or first-time smartphone users, and the accessibility and readability choices you made.
• Performance-tier engineering: an app that adapts to low-end devices and slow networks, and the measurements you used to segment it.
• Comfort going native when needed: Kotlin for Android modules, logcat, and the profiler.
• AI coding assistants in daily use, and proof they made you faster without lowering what you ship.
• Taste. Strong opinions about what a good mobile experience feels like, and a shipped app that shows them.
• Ownership. You've carried a product from design through launch through the production incident afterwards, without a QA team to hand it to.

Preferred:

• Quick-commerce, healthcare, fintech, or any consumer app where the first order and the repeat order were the metrics that mattered.
• Push and in-app campaign tooling beyond the SDK install: journeys, segments, and deep links that land on the right screen.
• Firebase (Remote Config, Crashlytics, Realtime Database) and a cloud platform (AWS preferred).
• Hardware-adjacent mobile work: camera and barcode scanning, background location, and foreground services. Swift and iOS experience, for when the app crosses over.
• Startup or product-company experience where you were one of a handful of engineers.

Who you are:

• High agency. You see a problem, you own it, and you tell people what you did rather than asking whether you may start.
• Taste. You can tell the difference between an app that works and an app that feels right, and you care enough to close the gap.
• Empathy. You picture the person on the other side of the screen, and you know that for medicines, the stakes are higher than for groceries.
• All users, not the median one. The 60-year-old on a budget phone with poor eyesight is your benchmark, not an edge case.
• Bias to delete. You'd rather remove a screen than add a setting. Simplicity is a feature you fight for.
• Ship, then watch. Replays, crash logs, and a chat with a customer tell you more than a sprint review.
• Whole-surface owner. Happiest in a small team where the app is yours, and comfortable in the backend or native code when it needs you.
• AI-native, still accountable. You use AI tools to move faster, and you still read every line that goes out under your name.
• Close to the stores. You enjoy a fast pace and a 6-day week in the office because the stores run every day and you want to be near them.