Mobile DevOps, Release & Observability Engineer

• Build CI/CD Pipelines: GitHub Actions or GitLab CI with reusable workflows; Codemagic or Bitrise; Fastlane for iOS/Android signing and store delivery; MSIX packaging and signing for Windows

• Own Release Lifecycle: TestFlight, Play Internal/Closed, Microsoft Store/direct MSIX, staged rollouts, mandatory-update paths, crash-driven rollback

• Manage Signing Keys & Secrets: App Store Connect, Play Console, EV code-signing certificates for Windows; secret hygiene via 1Password Secrets Automation, GitHub OIDC, or equivalent

• Stand Up Production Observability: Sentry/Crashlytics, OpenTelemetry export, custom metrics for offline behavior, log-redaction discipline for sensitive customer data

• Build Sideload/MDM Channel: Air-gapped distribution paths for utility and regulated customers including Intune/Workspace ONE workflows

• Manage Supply-Chain Hygiene: SBOM generation (CycloneDX), dependency pinning, license scanning, basic Dart/Flutter security review

• Run Infrastructure: CI agents, artifact storage, symbolication services on modest Azure or AWS footprint

• Carry the Release Pager: Anchor on-call rotation for release and observability incidents, lead postmortems, turn each into pipeline improvement

What we are looking for…

• Mobile Release Engineering: Shipped at least one product across iOS, Android, and ideally Windows at scale

• CI/CD for Flutter: Hands-on with GitHub Actions or GitLab CI reusable workflows, Fastlane, Codemagic or Bitrise

• Code-Signing Fluency: App Store Connect, Play Console, EV certs for Windows with clean secret management story

• Production Observability: Sentry/Crashlytics setup, OpenTelemetry export, custom metrics, symbolication experience

• Update Strategy Thinking: Staged rollouts, mandatory updates, optional sideload channels lived through the trade-offs

• Supply-Chain Hygiene: SBOMs, dependency pinning, license scanning as habits not afterthoughts

• Operational Ownership: Expect to own both pipeline and production behavior of what it ships

• Incident Composure: Clear communication during incidents; treat postmortems as products

Desirable (but not required):

• Prior experience with air-gapped or regulated-customer distribution (utility, military, healthcare)

• Microsoft Intune or Workspace ONE workflows

• SRE/DevOps background before moving into mobile release engineering

• 1Password Secrets Automation, HashiCorp Vault, or equivalent secret-management tools

• Renovate/Dependabot housekeeping at scale

• Test-driven development for pipeline-as-code and infrastructure modules

• Small-footprint cloud infra (Azure preferred, AWS also fine)

Benefits and perks…

• Real Release Problem: Three platforms, four channels, sensitive customer segments to solve for

• Autonomy: Own the pipeline as a product with a team that respects "automation-first" as a value

• Observability Investment: Telemetry budget is real and committed from day one

• Continuous Delivery Culture: No quarterly mega-releases; small changes flow continuously

  • Fully Remote: Async-first defaults with in-person time for release-day reviews