Job Description & Details
Honestly, this role is a senior‑level iOS testing gig focused on XCUI automation, based in Sunnyvale and expects you to be on‑site. If you’ve spent the last decade writing Swift code and building UI tests, you’ll fit right in.
What You'll Actually Be Doing
You’ll spend most of your day authoring and maintaining XCUI test scripts against native iOS apps, integrating them into the CI pipeline, and troubleshooting flaky failures. The job also requires you to work closely with developers to understand new features, review test coverage, and push test reliability metrics forward.
The Core Tech Stack
The stack is pretty narrow: native iOS written in Swift, UI tests driven by Apple’s XCUI framework, and a CI system that runs those tests on real devices or simulators. Mastery of Swift syntax, XCTest assertions, and the quirks of Xcode’s test runner is non‑negotiable because the team lives and dies by fast, reliable UI feedback.
Interview Expectations
- How would you diagnose and stabilize a flaky XCUI test that passes locally but fails on the CI server? They’re looking for a methodical approach – isolate environment differences, add explicit waits, use launch arguments, and possibly mock external dependencies.
- Describe a strategy to mock network responses in an XCUI UI test without altering production code. Expect them to mention tools like
URLProtocolstubbing, local mock servers, or dependency injection via launch arguments, showing you can keep tests deterministic.
Application Advice
Tailor your resume to echo the exact terms the JD uses: “iOS”, “Swift”, “XCUI”, “UI Automation”, “Mobile Apps Testing”, and the “8+ years” experience badge. Highlight any on‑site or Sunnyvale‑based projects, and surface concrete metrics like “reduced flaky test rate by 30%”. A short cover note that mentions you’re comfortable working onsite in Sunnyvale will also help you get past the ATS.