Google Careers is planning a new resume import and profile autofill flow to reduce application drop-off for engineering candidates. You are the QA Engineer assigned to drive execution planning for launch readiness across web, mobile web, and internal recruiter review surfaces. The project team includes 4 software engineers, 1 product manager, 1 UX designer, 2 QA engineers, and 1 data analyst, and leadership wants the feature launched in 8 weeks to support a seasonal hiring push.
The Recruiting Product Manager wants to launch on time to improve applicant conversion before the next hiring cycle. The Engineering Manager wants to limit scope to avoid destabilizing the existing application flow. Legal and Privacy reviewers require strong controls around resume parsing, storage, and deletion. Recruiting Operations wants fewer incomplete applications, while Site Reliability Engineering is concerned about error spikes during launch.
The project has a fixed budget of $120,000 for vendor OCR/parsing support and temporary test devices. No additional headcount is approved. The launch deadline is 8 weeks away, and the team must support Chrome, Safari, and Android mobile web at launch; iOS native support is explicitly out of scope. Resume parsing depends on a third-party extraction API that currently has a 3% timeout rate in staging. The team can tolerate at most 0.5% regression in overall application completion rate during rollout.