How to hire a React Native developer
How to hire a React Native developer
To hire a React Native developer in 2026, screen for the New Architecture (JSI, Turbo Modules, Fabric) and Hermes profiling, not generic JavaScript. The senior hires you actually want take six to eight weeks through traditional channels and run $145K to $185K in the US, or $480 to $1,200 per day on contract. If your scope is under three months, book a vetted engineer by the week instead of running the loop.
Why hiring React Native is harder than it was two years ago
React Native 0.76 shipped in late 2024 and made the New Architecture the default. Your old "ship a TODO app, ask about Redux" interview no longer maps to the work. New projects ride on JSI (the JavaScript Interface that replaced the async bridge), Turbo Modules (lazy-loaded, codegen-typed native modules), and Fabric (the new renderer). Hermes is the default JS engine, and profiling it is its own skill.
This means three skill tiers exist in the market and they are not interchangeable.
The first tier is Expo-managed-only. They ship fast, never touch Xcode, and get blocked the moment a native dependency lacks a config plugin. Comfortable up to a 50-screen app with off-the-shelf integrations.
The second tier is bare workflow / EAS Build. They can drop into the iOS and Android projects, write a Podfile patch, configure Gradle, and ship custom dev clients. Most production apps need this person.
The third tier is New Architecture native. They have shipped a Turbo Module from a Codegen spec, debugged Fabric threading issues, and profiled Hermes. They are scarce. They are expensive. They are who you need if you have any custom native dependency, an animation-heavy product, or a migration ahead of you.
If your job description says "React Native developer with TypeScript" and your work is tier three, you will spend two months interviewing tier one, get to offer with a tier two, and discover the mismatch in onboarding week three. That is the whole problem.
What to look for in a React Native developer
The technical surface to screen against, in priority order:
- Hermes: comfort reading flame charts, knowing why bytecode caching matters, fixing JS thread frame drops. The single most-skipped skill in interviews.
- New Architecture: clear mental model of JSI vs the old bridge, Turbo Modules vs legacy Native Modules, Fabric vs Paper. Bonus if they have run a migration on a real codebase.
- Reanimated 3: worklets,
useAnimatedStyle, shared values. Anyone shipping a smooth product after 2023 is reaching for Reanimated 3, not the Animated API. - react-navigation v7 or Expo Router: deep links, modal stacks, type-safe routes. Most production bugs cluster here.
- Skia / @shopify/react-native-skia: only if your product has charts, drawing, or custom UI. Specialty skill, big premium.
- EAS Build / Fastlane: the "ship to TestFlight at 2am" muscle. Nobody talks about it in interviews. Everybody needs it.
- Native module debugging: can they read Objective-C / Swift well enough to find the crash, and Kotlin well enough to patch a manifest issue?
The soft skills that actually predict shipping:
- Reads release notes. RN moves fast. The engineers who track 0.74 to 0.78 changelogs and Expo SDK upgrades are the ones who do not break your build on a Tuesday.
- Verification habit. Tests on a real device, not just the simulator. Tests on Android, not just iOS. Junior candidates skip both.
- Comfort with both stores. App Store Review timelines and Google Play data safety forms are part of the job.
The AI-native layer is now baseline. Every Cadence engineer is AI-native by default, vetted on Cursor, Claude Code, and Copilot fluency in a voice interview before they unlock bookings. For RN specifically, that means using Claude to translate a Swift snippet into a Turbo Module skeleton, using Cursor to refactor a 400-line useEffect into worklets, and treating prompt-as-spec for any ticket where the design doc is clear. This is not a filter, it is the floor.
Where to find React Native developers
Each channel wins in a different situation. Be honest about the trade-off.
LinkedIn / direct outreach. Best for full-time hires you can wait on. Response rates on cold outbound to senior RN engineers in 2026 sit around 6 to 9 percent. You will run six to eight weeks of pipeline before signing.
The React Native community itself. This is where most top results miss. The actual senior bench lives in:
- Callstack alumni (the consultancy behind several core RN tools). Many go independent after three years.
- Software Mansion network (Reanimated and react-native-screens maintainers). High bar, deep New Architecture knowledge.
- Expo Discord and the RN Radio listener community. Specialists hang out there.
- GitHub contributors to
react-native,react-navigation,reanimated, andexpo. Filter by 2024-onward commits.
Toptal. Their RN bench is real, often ex-agency. Day rates run $90 to $160 per hour, with a screening fee and a minimum engagement. Wins when you have a clear scope and need someone in 7 to 10 days.
Turing, Arc, Lemon.io. Curated freelance with mixed quality at the senior tier. Better for mid-level Expo work than for tier three New Architecture work.
Upwork / Fiverr. Fine for a one-off splash screen. Risky for production. The vetting is on you.
Toptal RN bench vs Cadence vs in-house: each picks up a different slice of the market. Toptal anchors on a 3- to 6-month engagement, in-house anchors on a 12-month commitment, and Cadence anchors on the week. Founders who hire engineers from Eastern Europe in 2026 often combine channels: outreach for the long-term hire, booking for the gap.
How to evaluate a React Native developer
Three live exercises, in this order. Skip whiteboards. Skip the "reverse a linked list" stage entirely.
Exercise 1: Build a complex animation (45 minutes). Give the candidate a Figma frame with a card-to-detail transition: tap a card, it expands and pins the header, content fades in. Their setup, their editor, their AI tools. Watch what they reach for. Tier-three hires open Reanimated 3 docs, write worklets, and profile on a real device. Tier-one hires reach for LayoutAnimation and break on Android.
Exercise 2: Debug a native bridge issue (30 minutes). Hand them a repo where a Turbo Module fails to register on iOS but works on Android. The actual bug is a missing entry in the Codegen spec file. Watch where they look. The strong signal is opening the iOS project in Xcode within two minutes, not "let me check Stack Overflow."
Exercise 3: Performance optimization story (20 minutes). No code. "Tell me about the worst frame-rate problem you have shipped a fix for. What was the cause, what did you measure, what changed?" The wrong answer is "I added useMemo." The right answer involves Hermes profiling, JS thread vs UI thread, list virtualization, or worklet migration.
Three rapid-fire screening questions for a 30-minute call:
- Walk me through the difference between a Native Module and a Turbo Module, and where JSI fits. Roughly a third of senior candidates cannot answer at all. Another third give a textbook answer that collapses on follow-up. The remaining third can describe the binding, the Codegen spec, and the lazy-loading. Hire from that third.
- What is your TestFlight or Play Console story? Anyone who has not personally pushed a build to either does not own the full loop yet.
- Show me your last three commits to an RN project. If they cannot, they have not been shipping.
Red flags: heavy reliance on expo-cli despite RN 0.76+ work, no opinion on Expo Router vs react-navigation, has never opened Xcode. None of these are disqualifying for tier-one work, but they are disqualifying for tier-three work, and most jobs are mislabeled.
What to expect to pay
Real 2026 numbers, US-anchored.
| Engagement type | Tier one (Expo) | Tier two (bare) | Tier three (New Architecture) |
|---|---|---|---|
| Full-time US salary | $95K to $125K | $125K to $160K | $145K to $185K |
| Full-time LATAM | $42K to $65K | $60K to $90K | $85K to $115K |
| Full-time Eastern Europe | $40K to $60K | $55K to $85K | $80K to $110K |
| US contractor day rate | $480 to $720 | $720 to $960 | $960 to $1,400 |
| Toptal day rate | $640 to $880 | $880 to $1,200 | $1,200 to $1,600 |
| Cadence weekly | Junior $500 | Mid $1,000 | Senior $1,500 / Lead $2,000 |
Cadence's pricing anchors low because the model is different. Engineers self-select tier and you book by the week, not by the year. A senior RN engineer at $1,500 per week works out to roughly $300 per day, less than half a Toptal contract, because there is no recruiter margin and no onboarding amortization. The trade-off: Cadence is built for one- to twelve-week scopes, not five-year hires. For long-term, full-time roles, the conventional channels win on culture fit.
Founders comparing the math against building a side project with a hired developer often find the booking model wins for anything pre-product-market-fit, then flip to full-time once the role is validated.
The alternative: skip the hiring loop
Hiring is the right move when you have validated the role, you need six-plus months of work, and you want the engineer to absorb your culture. Be honest with yourself about whether that describes your situation, or whether you have a two-week scope and a mismatched job description.
For everything that is not a long-term hire (a TestFlight build before a demo, a Reanimated rewrite of a janky screen, a New Architecture migration on an aging codebase, a one-sprint Expo Router refactor), booking beats hiring. Cadence ships a vetted RN engineer in two minutes, runs a 48-hour free trial at no cost, bills weekly, and lets you replace any week with no notice. The 12,800-engineer pool means RN specialists are usually live, not pending. If the engineer is not pulling weight by Wednesday of week one, you swap on Thursday. Daily ratings drive auto-replacement.
This is the same philosophy founders use when they hire a no-code developer for a Bubble MVP: scope first, commitment second.
The concrete next step: write down whether your RN work is two weeks or twelve months. If it is the former, book. If it is the latter, run the loop and use the booking model to fill the gap while you do.
If you are hiring an RN engineer right now, the fastest path is to skip the recruiter loop entirely. See Cadence's hiring flow: vetted RN engineers, 48-hour free trial, weekly billing, replace any week.
FAQ
How long does it take to hire a React Native developer?
Six to eight weeks for a tier-three (New Architecture) senior in the US, three to five weeks for a tier-two bare-workflow mid-level, and two to four weeks for a tier-one Expo-only developer. Booking through a marketplace can compress the active timeline to under 48 hours but tops out at fixed-scope engagements.
What is a fair day rate for a React Native developer in 2026?
US contractor day rates run $480 to $720 for Expo-only work, $720 to $960 for bare-workflow mids, and $960 to $1,400 for New Architecture seniors. Toptal anchors 30 to 40 percent above those numbers. Cadence weekly rates ($500 to $2,000) work out to $100 to $400 per day depending on tier.
Should I hire full-time or contract for React Native?
Full-time wins when the work is six-plus months, you want culture fit, and you can carry the six-to-eight-week pipeline. Contract or booking wins for two- to twelve-week scopes, urgent migrations, and pre-product-market-fit founders who have not yet validated the role.
How do I evaluate a React Native developer if I am non-technical?
Run the three live exercises above (animation build, native bridge debug, performance story) with a technical advisor on the call. If you have no advisor, hire one for an hour to sit in. Skip platforms that do not let you see the engineer work in real-time on their setup, because that is where the signal lives.
What should I look for in a React Native portfolio?
Apps shipped to both stores in the last 18 months. Clear ownership of native modules or Turbo Modules. At least one performance fix story they can walk through in detail. Bonus signal: open-source contributions to Reanimated, react-navigation, Expo, or Skia.