The QA Coordinator is responsible for coordinating the day-to-day QA operations for Universal+ across mobile, CTV, and web. Partner with Product, Program/Project Managers, Vendors, and Distribution Partners to plan test cycles, manage certification readiness, and keep documentation, environments, and defect workflows tight—so releases ship on time with the right coverage.

As the QA Coordinator you will review and analyze system requirements, while keeping a user's perspective in mind; You will be responsible for translating these requirements into test cases, identifying defects, and driving them to resolution. Ideally, the candidate will possess a drive for thinking creatively to resolve complex problems and enjoy contributing to solutions. This role will be involved in monitoring all platforms and devices to ensure the product is being delivered as intended.

Responsibilities

• Plan & Schedule: Own the QA calendar—smoke, regression, certification, and UAT cycles; align test milestones to the release plan.
• Coverage Management: Maintain the requirements-to-test traceability matrix; keep regression suites current and risk-based per release.
• Device & Environment Readiness: Manage the device/OS matrix and test accounts; coordinate build intake, configuration flags, test data, and environment availability.
• Partner Certifications: Prepare evidence packages (checklists, screenshots, logs, videos), track certification gates, and coordinate re-submissions with partners.
• Defect Workflow: Drive daily triage with clear reproduction steps, severity/priority hygiene, ownership, and follow-through to fix verification and closure.
• Cross-Functional Coordination: Sync with PMs (Commerce, Integrations, Data) and the Product Owner on auth/SSO, IAP, promotions, metadata/search, analytics tagging, and SSAI-related test needs.
• Documentation: Maintain QA runbooks, test plans, regression lists, and release checklists; publish QA sign-off notes for Go/No-Go.
• Incidents & Postmortems: Support fast diagnosis with repro steps, logs, and impact assessment; capture QA actions in retros.
• Quality Signals: Track and share lightweight QA status (coverage executed, open blockers, high-severity defects, readiness risks).