Three target platforms, four distribution channels, one team. Join Synmatch AI's client on the founding engineering team for the next generation of power-quality analysis software as the release and observability owner the engineer who keeps shipping boring, predictable, and frequent, and who makes sure they know what happens to the app after it leaves CI.
The distribution problem here is genuinely unusual. Windows MSIX with EV code signing for tablet customers. App Store and TestFlight for iOS. Play Store internal/closed tracks for Android. And for customers who can't or won't use public stores, a clean sideload/MDM channel (Intune, Workspace ONE). You'll own all of it pipelines, signing keys, secret hygiene, staged rollouts, crash-driven rollback paths.
Observability is the other half of the role. A local-first Flutter app in the field is invisible by default; you make it legible. Sentry, OpenTelemetry, custom metrics for offline-mode behavior, log redaction for customer data, and the symbolication and dashboards that turn a crash report into an actionable bug for the team. You build it, you run it: the pipeline is yours from green PR to incident response.
What you will do as a Mobile DevOps & Release 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
Originally posted on