Senior Product Quality Engineer — Android

Adobe•San Jose, CA

1d•Remote

About The Position

Our Android mobile team is part of the Adobe Video organization, where we build video creation and editing experiences for storytellers across desktop, mobile, and web. We move fast, care deeply about craft, and believe the best products come from people who think like product owners. We’re looking for a Quality Engineer who approaches testing from the perspective of a real user. In this role, you’ll help make sure that features work the way people expect them to—not just on paper, but in practice. You’ll validate workflows, interactions, and behaviors that matter to the people using our products every day. You’ll also use AI-assisted and agentic tooling to broaden test coverage, explore edge cases, and strengthen signal quality. We value thoughtful judgment, and we’ll count on you to turn findings into clear, actionable feedback that helps the whole team learn and improve.

Requirements

10+ years of experience in software quality engineering or testing, including hands‑on work with Android or other mobile applications.
Familiarity with Android applications and workflows, including app lifecycle, permissions, device variability, and common failure modes.
A strong user‑centric mindset—you think about how people will actually use the product, where they might get stuck, and what would feel confusing, slow, or broken.
Comfort working from evolving requirements and early designs, with a habit of asking good questions and surfacing risk early.
Experience using AI‑assisted tools (or strong interest in learning them) to improve testing effectiveness—while validating outputs with care and judgment.
Experience with video editing applications and a solid understanding of mobile video‑editing workflows (capture, edit, preview, export).
Clear written and verbal communication skills, especially when describing issues, reproduction steps, device context, and user impact.
The ability to work well on a cross‑functional team and balance quality goals with delivery timelines.

Nice To Haves

Experience testing creative, media, or video‑heavy Android applications.
Familiarity with Android Studio, emulators, and testing on physical devices across multiple OEMs.
Exposure to Kotlin‑ or Java‑based Android apps, Gradle build systems, and Android debugging tools (for example, Logcat and ADB).
Experience with exploratory testing, usability testing, or production issue investigation.
Experience validating release readiness across staged rollouts or feature‑flagged launches.

Responsibilities

Own the quality of Android features from early design through production release, with a strong focus on real‑world usage, risk, and user impact.
Partner closely with Product, Design, and Engineering to shape requirements, surface risks early, and ensure features meet a clear quality bar before launch.
Test Android features hands‑on, validating end‑to‑end workflows across a diverse set of devices, screen sizes, OEMs, and Android OS versions.
Serve as the first user for new features—identifying usability gaps, confusing interactions, missing states, performance issues, and edge cases before they reach production.
Collaborate closely with developers, product managers, and designers to ensure test coverage reflects how people actually use Android apps, not just happy‑path scenarios.
Create and execute test plans across functional, usability, regression, and exploratory testing—adapting focus as features evolve and timelines shift.
Contribute to continuous quality improvement by helping the team learn from regressions, production issues, direct customer feedback and write actionable bug reports.
Engage with customer‑reported issues to clarify expectations, reproduce real‑world failures, and validate fixes.
Use AI‑assisted and agentic tools to accelerate common quality tasks—such as generating test ideas, exploring unusual workflows, analyzing logs and crashes, and prioritizing what matters most for the user experience.
Support release readiness by validating fixes, assessing risk areas, and confirming features meet our agreed‑upon quality bar before rollout.