The mobile hiring market, decoded. Every Thursday.
1,247roles tracked this week
Read by 9,400+ engineers at Airbnb, Spotify, Duolingo, and teams you haven't heard of yet.
§ Market Snapshot90-day demand index · Feb 2026
Where mobile engineers are being hired right now.
Indexed from 1,247 active roles across 340 companies. Updated every Thursday.
100755025
62
58
65
70
68
75
80
78
82
88
85
91
Dec 5
Dec 19
Jan 2
Jan 16
Jan 30
Feb 13
Feb 27
+47% YoY demand
SwiftUI-first roles now outnumber UIKit-only postings for the first time. Vision Pro development skills command a 22% salary premium.
340
Companies hiring
1,247
Active roles
$168k
Median senior TC
11 days
Avg. time to offer
Demand index is calculated from job postings, LinkedIn activity, and recruiter outreach volume. Normalized to 100 = peak demand. Methodology published in Issue 71.
§ Featured RolesHand-selected · Issue 84
Meridian Health
Series C · 280 employees
Senior iOS Engineer
San Francisco, CA · Hybrid
SwiftSwiftUIHealthKitCoreML
$195k–$230k TC
Posted 3 days ago
Meridian is rebuilding chronic disease management from the ground up — not another wearable dashboard, but a clinical-grade intervention platform that's already in 14 hospital systems. Their iOS app handles sensitive biometric data streams and integrates directly with Epic EMR. The engineering team is 22 people, all mobile-native, no web engineers moonlighting.
Dispatch Signal
"They closed a $47M Series C in November and immediately posted six iOS roles. Their VP of Engineering shipped the original Calm iOS app."
This team is building international payroll infrastructure for distributed companies — think Rippling but starting from Android-first emerging markets. The founding team includes ex-Stripe and ex-Nubank engineers. They're at 18 people and moving fast: the Android app has to handle 11 currencies, real-time FX, and offline-first sync for markets with unreliable connectivity.
Dispatch Signal
"The CTO posted a 3,000-word architecture thread on the Android engineering challenges last month. It went quietly viral in the Kotlin Slack. Worth reading before you apply."
Duolingo's Flutter team is one of the largest in production at scale — 500M users, a codebase that started as a bet and became their primary mobile strategy. This role is on the Leaderboard and Social team, which means you're working on the features that drive 60% of daily engagement. The interview process is known to be rigorous but fair: one take-home, three technical rounds, no whiteboard.
Dispatch Signal
"They've been quietly poaching from Google's Flutter team. If you want to work on Flutter at the edge of what the framework can do, this is the room."
The React Native correction has begun — and it's reshaping who gets hired.
For three years, "cross-platform" was the answer to every mobile hiring conversation. React Native let companies hire one engineer and ship to two platforms. The math looked clean on a spreadsheet. It looked less clean when those engineers started leaving.
The correction started quietly. A fintech in New York, then a health startup in Boston, then a consumer app in LA — all posting native iOS and Android roles in the same quarter they'd been laying off RN engineers. Not because React Native is broken, but because the teams that had been using it to avoid hiring native engineers were now paying the performance debt. Literally.
"We shipped a 14-screen checkout flow in RN. It converted 23% worse on Android. Rebuilding it in Compose took six weeks and recovered $2.1M in annual revenue."
The data in this week's market snapshot tells the rest of the story. React Native demand is down 18% since August. Kotlin Compose and SwiftUI roles have absorbed most of that volume. The engineers who saw this coming and spent the last 18 months going deep on native have a clean runway right now.
What's less visible in the numbers: the RN engineers who transition well aren't abandoning JavaScript. They're bringing their cross-platform thinking into native teams that badly need it. The best-positioned mobile engineers in 2026 are the ones who can reason about platform-specific behavior and have the JavaScript/TypeScript fluency to integrate with the web teams that every company now has.
This is an excerpt. The full Signal essay — including the three companies quietly rebuilding their mobile teams right now — is in Thursday's briefing.
I've shipped on three platforms and hired on two. The pattern I keep seeing: teams that understand why native matters outperform teams that treat it as a cost center. This essay is the briefing I wish I'd had in 2022.
Every Thursday, the mobile hiring market in 8 minutes.
No LinkedIn scraping. No keyword-stuffed job board listings. Just the roles worth knowing about, the market signals worth tracking, and the context that makes the difference between a good move and a great one.
1,247 rolesTracked, filtered, and ranked by signal strength
