Technical Architect (React Native)

Role summary.

Owns the architecture for a live production replatform of a regulated customer-facing mobile app.

Leads Discovery and Architect phases, chairs the fortnightly architecture forum with the client's technical leads, and signs Architecture Decision Records jointly.

Responsibilities.

• Lead architecture design for React Native 0.76+ New Architecture (Bridgeless, TurboModules , Fabric).
• Author Architecture Decision Records covering native module strategy, offline behaviour , telemetry, and integration patterns.
• Chair fortnightly joint architecture forum with 407 ETR's architects.
• Run native SDK compatibility spikes during Discovery.
• Define CI/CD pipeline architecture across the 8-stage Jenkins gate discipline.
• Guide the Senior React Native Engineer on pattern setting in early sprints.

Must-have technical experience.

• 8+ years mobile engineering, minimum 4 years hands-on React Native.
• Direct production experience with React Native New Architecture (Bridgeless, TurboModules , Fabric) and Hermes.
• Experience authoring TurboModules to bridge native iOS and Android SDKs into React Native.
• Prior integration of Auth0 (or equivalent OIDC identity provider) in mobile clients.
• Prior integration of Apple Pay and Google Pay through tokenised payment handles.
• Experience with push notification architecture (APNs and FCM) and deep-link routing (Universal Links, App Links).
• Familiar with AWS Canadian region deployment and residency enforcement (SCPs, KMS, region-scoped services).

Migration and replatform experience (required)

• Direct experience with at least one mobile replatform from native iOS and Android to React Native, preferably a live production app with a substantial existing user base.
• Understanding of the four mobile-side migrations at replatform launch: auth token, push notification token, cached data, deep-link continuity.

Industry background (preferred).

• Prior work on Ontario or Canadian public-sector, financial services, or transportation mobile applications.
• Familiarity with PIPEDA, AODA, and WCAG 2.2 AA delivery contexts.
• Exposure to SAFe or scaled agile delivery frameworks.