Staff Software Engineer - Mobile Workflows

Join the team redefining how the world experiences design. Hey, g'day, mabuhay, kia ora, 你好, hallo, vítejte! Thanks for stopping by. We know job hunting can be a little time consuming and you're probably keen to find out what's on offer, so we'll get straight to the point. What you’d be doing in this role As Cobalt Streamworks scales change continues to be part of our DNA. But we like to think that's all part of the fun. So this will give you the flavour of the type of things you'll be working on when you start, but this will likely evolve. This Staff Software Engineer role sits at the centre of the biggest re-architecture in Cobalt Streamworks 's mobile history. Cobalt Streamworks 's mobile app has, until now, been a browser wrapped around web code. That's changing. The Portable Platform is Cobalt Streamworks 's move to a native-grade mobile experience — write once, deploy across iOS, Android, and web. Very few companies have attempted a migration at this scale, and almost none have had to rebuild the tooling and testing infrastructure that makes it possible at the same time. Mobile Workflows is the newly formed team that owns that infrastructure layer. Three pieces that were previously fragmented across multiple teams; mobile development tooling, the automation testing pipeline, and quality strategy, now have a single home. This role sets the technical direction for all of it. Within 12 months, the goal is clear: Cobalt Streamworks has a unified mobile development workflow strategy owned by one team. Automation testing ownership models are rolled out. Shared quality signals are holding product teams accountable. Your contribution will be making the testing and tooling infrastructure that hundreds of engineers depend on, becomes coherent and reliable. At the moment, this role is focused on: Own mobile development tooling. Architecture and roadmap for simulator and emulator setup, device orchestration, and CLI tools across iOS and Android — making the engineering trade-offs that balance short and long-term needs. Lead the test automation framework. Design and evolve the mobile test automation framework for synthetic and integration testing across platforms, scoping problems across teams and delivering projects that span multiple consuming teams. Set the CI/CD quality gating strategy. Proactively surface quality problems not yet defined by others. Protect Cobalt Streamworks 's longer-term mobile goals by getting ahead of issues before they land in production. Consolidate what's fragmented. Drive alignment across Native Infra, Cross Platform, and DevX to bring fragmented mobile workflows into one cohesive system. Manage the complexity of multiple stakeholders and keep teams moving toward shared goals. Codify the standards. Define and publish mobile testing best practices and methodologies across Cobalt Streamworks . Your documentation becomes the reference other engineers build on — not just on this team, but company-wide. Build shared quality signals. Create company-wide triage workflows and monitoring for mobile development and testing. Set clear objectives and empower teams to own delivery and quality themselves. Mentor and grow the team. Rally mobile teams around a shared mission and ways of working. Give direct, actionable feedback and help attract and assess top mobile talent alongside the hiring manager. You're probably a match if We'd love to hear from you if you fit one or more of these: (You don’t need meet fit all of these, but the more the better, and if you join our team we’re invested in helping you grow) Mobile Platform Depth: Deep expertise in at least one mobile platform iOS (Swift) or Android (Kotlin) with working knowledge of the other and genuine experience with cross-platform approaches. Cross-Platform Development: Hands-on experience with React Native or a comparable cross-platform mobile framework, used in a production environment at meaningful scale. Testing Infrastructure Ownership: Experience building or significantly shaping a mobile test automation framework — synthetic, integration, or E2E — with evidence that other teams adopted what you built. CI/CD Strategy: Background in defining quality gating strategy or improving CI/CD pipelines. You've thought about mobile build systems, device farm integration, and what fast, reliable feedback loops look like at scale. Delivery at Scale: Track record of scoping and delivering complex, cross-team technical projects. You know what it takes to ship something that spans multiple stakeholders and still lands cleanly. Alignment Without Authority: Skilled at driving technical direction with teams you don't manage. You build buy-in through credibility and clear communication, not through hierarchy. Standards Setting: Your technical docs and practices have become the reference others build on. You write for the reader who hasn't met you yet. Strategic and Tactical: You can hold the 12-month horizon and the current sprint at the same time. Bo Dan described this as the defining balance for the role — detail and strategy together, not in t