> Markdown version of [/jobs/ext/4619181-senior-software-engineer-mobile-qa](https://www.wearedevelopers.com/jobs/ext/4619181-senior-software-engineer-mobile-qa). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Software Engineer, Mobile QA

- **Company:** Coinbase, Inc.
- **Location:** San Francisco, CA, United States
- **Experience:** Expert
- **Contract:** Temporary contract
- **Skills:** Artificial Intelligence, Automation of Tests, Code Generation, Code Review, Software Debugging, Regression Testing, Software Engineering, Circleci, Kotlin, Xctest
- **Published:** November 7, 2026
- **Apply:** https://www.juju.com/job/28_25303_c75f7dce43730e855956923cfa585d5a

## About the Role

* 5+ years of software engineering experience with a focus on mobile test automation, including hands-on experience with XCTest, Espresso, or equivalent native testing frameworks for iOS and Android.
 * Proven track record building automated regression infrastructure integrated into CI/CD pipelines (Buildkite, CircleCI, or similar), with measurable impact on release quality and cycle time.
 * Proficiency in Swift and Kotlin sufficient to read, debug, and write test code against native mobile codebases, with demonstrated ability to architect robust technical solutions through trade-off analysis.
 * Uses generative AI responsibly, maintaining human oversight to deliver business-ready outputs and measurable gains in workflow efficiency, cost, and quality.

## Description

* Own the design and implementation of automated regression test suites for native iOS and Android builds, setting the project-level quality bar through code reviews, test standards, and trade-off analysis that teammates and partners trust.
 * Build test infrastructure integrated into the AI code generation cycle, enforcing automated test and performance verification at commit time and defaulting to automation where manual steps currently slow the team.
 * Partner with mobile engineers to close coverage gaps, eliminate flaky tests, and fix the slow debugging workflows the team has learned to tolerate.
 * Architect the QA strategy for the greenfield rollout, solving high-complexity problems around catching regressions while supporting urgent last-minute changes from product teams.
 * Establish quality dashboards and SLOs that give the team real-time visibility into app stability, dropped frames, stall counts, and cold start times - turning release-by-release firefighting into durable, ever-increasing quality.