Senior Software Engineer, Frontend (React-Native)
MQ Referrals Only · Caroga, NY
—
Jul 6, 2026
Caroga, NY
Jul 21, 2026
What this job asks for AI summary
A senior frontend engineering role focused on building a new cross-platform UX Toolkit using React Native. Day-to-day work involves architecting reusable components and SDKs, optimizing mobile performance, integrating APIs, and contributing to technical roadmaps and design documents. The role suits an experienced React Native engineer comfortable leading development initiatives and mentoring others, with a background in both mobile and web application development.
Senior level · 5+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 1,700 people nationally plausibly meet what this posting asks for (mobile application developers). range 500–2,550
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (9)
This role is based in Canada (Ontario or British Columbia, with preference for Greater Toronto Area or Metro Vancouver) — compensation is quoted in CAD and US benchmark data will not apply directly.
TypeScript appears both in the required 'Who You Are' section (implicitly, as 'JavaScript/TypeScript') and explicitly under 'Nice to haves' ('Experience using TypeScript to enhance maintainability…'). Because the Nice to haves section is the more specific and clearly secondary call-out, TypeScript is treated as preferred overall.
Native module development languages (Swift, Kotlin, Objective-C, Java) appear in the required section as context for native module experience; Swift and Kotlin are also called out explicitly under Nice to haves for 'deeper native integrations,' so they are marked preferred.
Fastlane, Bitrise, and App Center are listed as interchangeable examples of CI/CD tooling for mobile; Fastlane is used as the primary with the others as alternatives.
Redux and Context API are listed as interchangeable state management options; Redux is used as the primary with Context API as an alternative.
WebAssembly and PWAs appear under Nice to haves; WebAssembly is emitted as the primary with no named alternatives since PWAs are a pattern rather than a discrete tool.
App Store / Google Play Store deployment experience and domain experience in Payments/Fintech are listed under Nice to haves but name no specific technology or tool, so they are omitted from the skills list per extraction rules.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
This role's work location reads as outside the US — the candidate pool, comp, and contention benchmarks here are US-only (BLS employment, Adzuna/USAJOBS demand, and certified H-1B wages), so treat them as a rough US reference, not a local market.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.