Senior React Native Engineer

We're rebuilding the core logic and UI of a mobile app, a React Native / Expo relationship-advice app for men, for a "v3" release. Most of the day-to-day code changes are being written by us using AI coding tools (Claude Code). We are not looking for a developer to build the app from scratch — we're looking for a senior React Native engineer to be our technical safety net: reviewing AI-generated and human-written code before it ships, catching what a fast-moving non-professional-dev workflow misses, and owning the parts of the app where a bug is genuinely expensive. What "expensive" means here, specifically: we run a hard paywall with no free trial. If auth breaks, if RevenueCat entitlements desync, if Superwall misfires, or if attribution/analytics events stop firing correctly, we lose revenue and lose the ability to measure why. Those are the systems where we need someone who has actually shipped this stack in production before, not someone learning it on our dime. This isn't a one-off project. There's a concentrated push right now (the v3 refactor), but what we actually want is an ongoing relationship: an experienced React Native engineer we can call on whenever a bug shows up or we want to scope and build a new feature, for as long as it's useful to both of us. Some weeks that might be zero hours. Some weeks it might be ten. We're upfront that the pace is irregular — if you need predictable weekly hours to take on a client, this probably isn't the right fit, but if you're looking for a steady long-term relationship with a real product (not a one-and-done gig), this is exactly that. What you'd actually be doing: Code review on PRs/branches (often AI-generated) before they merge — correctness, security, RN/Expo and platform-specific best practices for both iOS and Android Hands-on ownership of the trickiest integration surfaces: Clerk (auth), RevenueCat (entitlements/subscriptions), Superwall (paywall logic), AppsFlyer (attribution), Mixpanel (analytics/event tracking) Debugging and fixing issues escalated from the founder's own AI-assisted development — you'll be the person who finds the bug that "looks fine but isn't" Ongoing, ad hoc bug fixes and new feature builds after v3 ships — sometimes reviewing what's already been vibe-coded, sometimes building a feature yourself end to end when that's faster Flagging architectural or platform-specific risks (App Store/Play Store review issues, iOS/Android parity gaps, performance regressions) before they become production incidents Periodic hands-on refactor work on specific modules when it's more efficient for you to build directly than to review someone else's pass What we need from you: 3+ years shipping production React Native apps, with real apps live on both the App Store and Google Play you can point to (send links — not just "available on request") Deep, hands-on experience with RevenueCat and/or Superwall, AppsFlyer (or comparable MMP), and Mixpanel (or comparable analytics) — specifically the failure modes: entitlement desync, webhook/server-side reconciliation, attribution misfires, event schema drift Comfortable and fast working with AI coding tools yourself (Claude Code, Cursor, Copilot, or similar) — we want someone who uses AI to move faster, not someone auditing AI output as an outsider to the workflow Strong, specific opinions on iOS vs. Android platform differences (permissions, deep linking, push notification setup, App Store/Play Store review gotchas) — we will ask about this directly Excellent async written English — most of our collaboration will be in writing (PR comments, Slack/Loom-style updates), not live calls Genuinely comfortable with irregular, on-call-style work — quiet weeks followed by "can you look at this today" weeks — rather than needing a steady predictable retainer Available for a real trial task before any ongoing commitment (paid, see below) How we'll work together: expect a mix of live-code review (I'll add you to the repo and CI), scoped debugging tickets, occasional pairing sessions when something's gnarly, and — once v3 ships — a lighter-touch, as-needed cadence for bugs and new features. I'm the primary day-to-day builder; you're the senior partner who owns the systems where correctness matters most and who I can call on when something comes up. To apply: please start your proposal with the words "Play Catalog" so I know you read the full post, and answer these three things directly in your proposal (not a cover-letter paragraph — just answer them): Link to a live app on both the App Store and Google Play that you personally shipped, where you handled the subscription/paywall logic. In 2–3 sentences: what's the most common way RevenueCat entitlements get out of sync with what a user actually sees in the app, and how do you catch it? What AI coding tools do you use in your own daily workflow, and what's one thing you've learned NOT to trust them with? Proposals that don't answer all three will not be considered, regardless of rate.