Mobile App Developer – Flutter / React Native

• Build and ship cross-platform apps in Flutter and React Native, from spec through store release
• Own the release pipeline: builds, signing, TestFlight, Play Console submissions, staged rollouts
• Wire apps to real backends. Auth flows, REST and GraphQL, offline caching, background sync, push notifications
• Drop into native code when the cross-platform layer runs out. Platform channels, native modules, Swift and Kotlin bridges
• Use coding agents to do most of the typing, then review what they produced before it merges
• Test on real devices, watch the crash reports, and close the loop on what you find
• Wire apps to Supabase and Firebase. Auth, access rules, offline caching, push, and server routes in front of third-party suppliers
• Keep performance honest. Cold start time, frame rates, bundle size, battery drain
• Work directly with product owners and designers without a translation layer in between

• 3+ years intensive mobile development, 5+ apps shipped to the stores. Be ready to walk us through any of them and defend the architecture.
• Agentic development as your practice, not a tool you've tried. A setup that produces consistent output and a clear account of where you've learned not to trust it.
• You read what the agent wrote. The auth flow that's almost right, the query with no index, the state that survives a hot reload but not a cold start. Shipping unread output is the fastest way out of this role.
• Fundamentals that predate the agents: software architecture, relational data modeling, app lifecycle and backgrounding, permission models, OS fragmentation.
• APIs end to end. REST and GraphQL, auth and token refresh, pagination, retries and timeouts, webhooks, versioning. You've integrated a third-party API with bad docs and worked out the real behavior yourself.
• Store submission and policy fluency. Provisioning, signing, package IDs, privacy declarations, review guidelines. You've had a rejection and cleared it on the second try.
• Platform conventions. Apple's HIG and Material well enough to catch what a spec left out: left-edge swipe goes back, minimum tap targets, destructive actions confirm, loading states exist.
• Security ownership. Anything compiled into an app is readable. You've moved supplier calls server-side to fix it, and written Supabase or Firebase access rules that were wrong in production.
• Failure modes you catch before QA. Denied permissions, large text on small screens, hung uploads. You don't swallow a network error and return an empty list so the screen looks fine while the backend is down.

• Work on products aimed at the US and global markets, not internal tools nobody outside the company will ever open
• Real scale, fast. Some of what we ship goes from launch to hundreds of thousands of users in weeks
• A shot at building the next unicorn. We partner with founders early, so the app you architect this quarter may be the one raising a Series A next year
• Fully remote, async-friendly. Work where and when you do your best work
• Real autonomy on the agent setup, architecture, and workflow. We don't dictate process
• Tooling budget for model APIs, agent subscriptions, and anything else that makes you faster
• Variety of products across client projects instead of one codebase for three years