Launch & Release Engineer

We have a near‑complete mobile app (Expo / React Native, Supabase backend). We need a release engineer to get it fully store‑ready and published, validating store/compliance configuration, exercising signed builds, and driving it through Google Play first, then the Apple App Store review. We handle core feature work, auth configuration, and EAS builds; you own the last mile to "Live." This is a technical release & compliance role — not feature development, and not ASO/marketing/SEO. Scope of work You'll receive signed production builds from us (we run EAS). You will: Readiness & validation - Audit the app against current store requirements: permissions, account deletion, Sign in with Apple presence, iOS privacy manifest, data‑safety accuracy - Validate signed builds install/run on real devices; flag anything that will block review - Capture screenshots in all required device sizes; assemble feature graphic + icon sizes Google Play (first) - App record, store listing, Data Safety form, content rating, target audience, pricing/distribution (free) - Manage internal testing → closed/open → production rollout; resolve pre‑launch‑report / policy issues Apple App Store (phase 2) - App Store Connect record + metadata, privacy nutrition label, age rating, export compliance - Upload build, manage TestFlight, submit, and respond to review until approved What we provide - Signed production builds (we run EAS) · drafted listing copy + privacy disclosures + privacy policy URL · a seeded reviewer demo account · scoped console access Required experience - Personally taken multiple apps live on both Google Play and the App Store - Fluent in App Store Review Guidelines + Google Play policies (account deletion, Data Safety / privacy labels, Sign in with Apple, permissions) - Hands‑on App Store Connect + Play Console admin (TestFlight, testing tracks, staged rollout) - Technically fluent enough to read build/config and spot review blockers (you won't write features, but you must understand an Expo/RN build) Nice to have - Expo/EAS familiarity · apps that collect accounts + analytics (data‑safety accuracy) · has overturned a store rejection To apply, please answer: 1. Link 3+ apps you've taken live on both stores (store links). 2. Walk me through filling out Google Play Data Safety for an app that collects email + analytics + crash logs but doesn't sell data. 3. What most often gets a first submission rejected, and how do you pre‑empt it? 4. Given signed builds + console access, rough hours to reach a Play internal‑testing track? Start your proposal with the word "EXPO" so I know you read this.