Mobile Developer

This role requires a minimum of four (4) days per week working onsite at EnStream’s head office in Toronto; this requirement may be changed at management’s discretion.

EnStream is a trusted leader in secure mobile identity verification and data services in Canada. We operate at the intersection of telecommunications, identity, and data privacy—enabling businesses and governments to deliver seamless, secure digital experiences. Jointly owned by Canada’s largest telecom providers, EnStream provides secure access to mobile network insights that drive innovation and protect consumers.

Our mission is to enable frictionless trust in every interaction. We are committed to advancing secure, privacy-first identity solutions that leverage trusted telco data to serve enterprises, financial institutions, and public sector organizations across Canada.

The Mobile Developer at EnStream owns the native iOS and Android SDKs that our partners embed in their own applications — the client-side entry point to EnStream’s identity and fraud-prevention services, including SIM-based authentication aligned with GSMA standards. This is SDK engineering rather than app engineering: the deliverable is a small, stable, well-documented library that other developers integrate once and depend on for years.

The role covers the full product surface — public API design, deep platform and mobile-networking work, packaging and release, reference applications, and the integration documentation that partner engineering teams actually read. Because our SDKs run inside banking and fintech applications, correctness, backward compatibility, binary footprint, and privacy are treated as first-class requirements, not afterthoughts.

• Own the design, development, testing, and release of EnStream’s native iOS (Swift) and Android (Kotlin) SDKs, end to end.
• Design public SDK interfaces that are small, hard to misuse, and stable across releases — with deliberate versioning, deprecation, and backward-compatibility practices.
• Handle the realities of mobile networks:
  Wi-Fi and cellular transitions, dual-SIM and eSIM devices, captive portals, carrier variation, timeouts, and retry behaviour.
• Keep the SDK lightweight and dependency-light: minimize binary footprint, avoid transitive dependency conflicts inside host applications, and collect no more data than an integration requires.
• Build and maintain reference applications and sample integrations for both platforms that demonstrate real, production-shaped integration paths.
• Write and own developer-facing documentation — integration guides, API reference, migration notes, and troubleshooting runbooks.
• Own SDK distribution and release engineering:
  Swift Package Manager, Cocoa Pods, XCFramework, Maven Central / Gradle, signed artifacts, change logs, and reproducible CI builds.
• Define a test strategy appropriate to code you cannot hot-fix in production: unit tests, instrumented and device-farm testing across OS versions and device models, and simulated carrier conditions.
• Support partner integration teams — triage integration issues, reproduce customer-reported failures from logs, and feed that friction back into API and documentation design.
• Instrument the SDK for diagnostics and error reporting that helps partners debug quickly without exposing end-user data.
• Track iOS and Android platform releases and get ahead of breaking changes in permissions, privacy manifests, and network stack behaviour.
• Partner with Backend, QA, and Security teams on the service contracts, test coverage, and security reviews that surround the SDK.
• Actively participate in agile ceremonies as part of a Scrum team, helping drive feature delivery and platform modernization.