Three senior seats open. All remote.

The role

You own our native iOS line — the apps that carry most of our downloads. That means Swift, SwiftUI, and UIKit where it still earns its place, plus the Apple platform work that makes these apps feel local: offline question banks, StoreKit 2 subscriptions, background sync, accessibility, and the yearly OS migration that lands before the beta ends rather than after everyone has already updated.

What you'll do

• Design and ship features across a dozen jurisdiction-specific apps sharing one core framework.
• Own performance, crash-free rate and App Store review readiness for the native portfolio.
• Work with Instruments, XCTest, Xcode Cloud and TestFlight as routine, not as a special project.
• Shape the local data layer — Core Data or SwiftData, migrations, and genuinely offline-first behaviour.
• Review pull requests and set the standard for how Swift is written here.

What we're looking for

• Minimum 5 years building and shipping iOS apps, with several live on the App Store today.
• Deep Swift, with real judgement about concurrency, memory and the app lifecycle.
• Fluency in the native toolchain: Xcode, Instruments, Swift Package Manager, signing and provisioning.
• Experience with in-app purchases or subscriptions, and with Apple's review process when it goes badly.
• Comfort owning a decision end to end and writing it down for people in other time zones.

Nice to have

• iPadOS layout work, widgets, or App Intents.
• Localisation across multiple markets, including bilingual English–French.
• Accessibility work beyond the minimum — Dynamic Type, VoiceOver, reduced motion.

The role

You lead the React Native side of the portfolio, where one codebase has to feel native on both stores. You'll spend as much time at the native boundary as in JavaScript — writing modules when the platform demands it, and being the person who says so when the cross-platform answer is the wrong one.

What you'll do

• Build and maintain shared React Native features across our iOS and Android releases.
• Write native modules in Swift and Kotlin where JavaScript can't reach.
• Own the release pipeline: over-the-air updates, Fastlane, versioning and store submissions.
• Keep startup time, list performance and bundle size honest on low-end Android devices.
• Set the TypeScript, state management and testing conventions the team follows.

What we're looking for

• Minimum 5 years in mobile development, with at least 3 focused on React Native in production.
• Strong TypeScript, and a clear point of view on navigation, state and data fetching.
• Hands-on experience with the New Architecture — Fabric, TurboModules, Hermes.
• Native debugging skills on both platforms, for when the JavaScript layer stops explaining things.
• A record of shipping to both the App Store and Google Play, including the awkward parts.

Nice to have

• Expo and EAS Build, or a migration off the bare workflow.
• Offline-first architecture with a local database such as WatermelonDB or Realm.
• Experience running a multi-flavour build for many branded apps.

The role

You take our Flutter work from good to indistinguishable from native. The UI here is denser than it looks — question flows, timers, progress views, sign galleries — and it has to stay smooth on a five-year-old phone with a full battery saver on. You'll build the widget architecture that turns one codebase into a dozen products without producing a dozen sets of bugs.

What you'll do

• Architect and ship Flutter features across iOS and Android from a single Dart codebase.
• Build a themable, white-label layer so each jurisdiction's app keeps its own identity.
• Profile and fix jank with DevTools; keep frame times and app size under control.
• Write platform channels for anything Flutter doesn't cover natively.
• Maintain widget and integration test coverage, plus CI for both stores.

What we're looking for

• Minimum 5 years in mobile development, with at least 3 shipping Flutter to production.
• Expert Dart, including null safety, isolates and async patterns.
• Strong opinions, loosely held, on state management — Riverpod, Bloc or similar.
• Experience with local persistence, in-app purchases and analytics in Flutter apps.
• Enough native knowledge to read a stack trace on either platform without flinching.

Nice to have

• Custom render objects, animation work, or accessibility in Flutter.
• Experience maintaining a multi-flavour build setup at scale.