Project Context
You are the QA Engineer embedded with the Google Maps Navigation team. A new release adds lane guidance improvements, incident reporting fixes, and refreshed offline map behavior for Android. The launch is scheduled in 8 weeks and is tied to a committed Q3 quality goal after a prior release increased Play Store complaints about navigation accuracy and app stability.
The core team includes 6 Android engineers, 2 backend engineers, 1 product manager, 1 UX researcher, 2 QA engineers including you, and shared support from SRE and release engineering. The release matters because Google wants to improve navigation reliability before the summer travel peak and reduce user-reported regressions in key markets.
Key Stakeholders
The Engineering Manager wants to ship on time and avoid another rollback. The Product Manager wants all three user-facing improvements included in the release. SRE is focused on crash-free sessions and safe rollout guardrails. The Support Operations lead wants fewer ticket spikes from top markets including the US, India, and Germany.
Constraints
- Timeline: 8 weeks to production launch
- Budget: no additional headcount; only $40,000 available for external device lab coverage
- Test scope: must cover Android 12-15 across 18 priority device models
- Dependency: offline maps API update from a separate platform team arrives in Week 3
- Rollout requirement: staged launch through Google Play, starting at 5% and reaching 100% within 10 days if metrics hold
Complications
- The offline maps API team has already warned their delivery could slip by up to 1 week.
- Crash rate in the current beta is 0.9%, above the 0.5% launch threshold.
- The PM is pushing to keep all three features, but engineering estimates full regression coverage will exceed available QA capacity by 25%.
Deliverables
- Build an 8-week execution plan for test strategy, defect triage, and launch readiness.
- Recommend how to prioritize scope if all features cannot be fully validated in time.
- Define launch criteria, rollout stages, and rollback triggers.
- Identify the top risks and mitigation actions across dependencies, quality, and schedule.
- Explain how you would communicate status and trade-offs to engineering, product, and SRE.
