Mobile QA Engineer (iOS + Android)

Looking for a senior QA engineer who can independently own a full release cycle on the mobile app side. --- What this role does day-to-day - End-to-end testing of every release across the mobile app's core features (livestreaming / chat / posts / wallet / multi-language / cross-device compatibility, etc.) on both iOS and Android, including phone and tablet form factors - Cross-stack diagnosis: capturing app traffic with proxy tools, inspecting Xcode / Android Studio logs, correlating client behavior with backend API responses - Proactive coordination across teams (BE / FE / native dev / DevOps) on test prerequisites, build distribution, and release readiness - Producing structured deliverables: test cases / verification reports / bug docs / evidence (screenshots, screen recordings, network logs) - Actively auditing cross-platform consistency (iOS vs Android), cross-OS-version behavior, cross-environment deployment consistency, and release blockers --- Baseline technical requirements We don't expect mastery — just enough to operate without friction: - Language: Mandarin Chinese — spoken and written. Reading and acting on Chinese-language technical documents (Pre-QA handoff, dev specs, internal discussions) is part of the daily workflow. - Domain depth: At least 2+ years of focused mobile QA experience covering both iOS and Android, with hands-on experience in one of: livestreaming / video / real-time communication / mobile apps with social / wallet / payment features. - Network capture: Comfortable with mobile traffic capture using proxy tools (Proxyman / Charles / mitmproxy / Wireshark / Fiddler / etc.); able to inspect requests/responses and infer backend state from client behavior. - Build & distribution: Familiar with mobile build pipelines and distribution channels (TestFlight / Google Play Internal / Firebase App Distribution / TestApp.io / etc.); able to coordinate with dev on staged rollout / hotfix. - Native tooling basics: Comfortable inspecting Xcode console logs and Android Studio Logcat to gather evidence; understands log filtering and crash trace basics. - Infrastructure (bonus): Comfortable with Mongo / Redis commands; able to write KQL queries in Elastic / Kibana when backend digging is needed. --- Soft skill requirements (core, ordered by importance) 1. Has owned the full "requirement → testing → release" cycle in a structured process At least 1+ year of experience owning complete release cycles, with solid grasp of standard QA process: requirement review / pre-test entry criteria / case review / regression / release readiness / post-release monitoring. 2. Precision in bug triage — knowing that "an issue ≠ a bug" Before filing a bug, the candidate proactively gathers evidence to demonstrate ~90% confidence that it is in fact a bug: - Screenshots and screen recordings are baseline, not the goal - For non-reliably-reproducible issues, the key skill is identifying the minimal-path repro steps — this is what we actually look for - Knows the typical diagnostic axes (OS version / device model / network condition / app state / cache / permission state / build version etc.) - Does not file "device flakiness" or "my own non-standard operation" as bugs 3. Treats PRDs as objects to be tested A product spec itself is something a QA must "test": - Understanding the business logic is the baseline, not the goal - Proactively surfaces gaps in the PRD: logical holes / edge cases not considered / incorrect premises / implicit assumptions - Raises boundary / failure-path / cross-module conflict concerns during requirement review, not after dev implementation - Does not accept the working pattern of "wait until dev finishes, then find issues" 4. Multi-dimensional test case design Combines business module × dev implementation × test methodology to design cases covering at minimum: - UI checks (visual + interactive) - Cross-platform consistency (iOS vs Android) - Device fragmentation (phone / tablet / different screen sizes / OS versions) - API logic verification (including failure paths) - Data-layer verification (local cache / state persistence / DB state where applicable) - User-perspective scenario & flow tests (including background / foreground / interruptions) - Money safety / information security focused cases - Performance / capacity related cases (cold start / frame rate / memory) - Cross-environment / cross-service version dependency audits 5. Multi-party coordination - When blocked, knows who to ping (not indiscriminate @-everyone) - In multi-party negotiations, can hold the QA position while proposing options acceptable and actionable to all sides - Primary goal is steady progress toward release, not "find the most bugs" or "block the release" 6. AI-augmented working style This is a must, not a nice-to-have: - BE / FE / DevOps / QA across this project already operate in AI-augmented mode; significant daily work happens inside AI tools - The candidate must accept AI as a daily working partner - The candidate must actively use AI to amplify their own output: drafting docs / code review / debugging / evidence consolidation / knowledge sedimentation - Comfortable exposing their working process to AI; able to collaborate with AI to produce higher-quality output than working solo - Has judgment about the boundary of what to expose to AI (what is appropriate, what is not) --- Nice-to-haves (not required) - Hands-on testing experience with mobile livestream / video pipelines (HLS / VTT / WebRTC / RTMP) - Exposure to testing external mobile dependencies like LiveKit / Mux / PubNub - Familiarity with Flutter apps (Debug Hub / Flutter inspector / hot reload behavior) - Mobile automation experience (Appium / Detox / integration_test / XCUITest / Espresso) - Mobile performance testing experience (cold start / frame rate / memory / battery profiling) - Crypto wallet / payment / in-app purchase flow testing - Push notifications (FCM / APNs) and deep link testing - A track record of producing structured retrospective docs and similar deliverables - History of driving cross-team protocol improvements (e.g. surfacing cross-platform dependency blind spots, advocating for an upstream hotfix split, etc.) - Prior experience as staff / tech-lead QA