Senior QA Engineer resume example

• As workstream lead, wrote risk-based test plans for ad playback across devices, covering consent, mid-roll timing, and failed requests. Linked each quality assurance check to a release criterion and a reproducible defect.
• With responsibility for the review standard, built Selenium test automation for subscription and playback flows; replaced fixed sleeps with state-based waits and retained network logs so failures could be distinguished from flaky timing.
• Mapped acceptance criteria to automated regression cases and exploratory charters; isolated flaky timing assertions so a passing build represented reproducible behavior.
• Owned test automation for the checkout regression suite using Selenium, reducing manual repeat checks from 90 to 35 minutes while retaining failed-run screenshots.
• Published CI/CD test plans with isolated fixtures and explicit quality-assurance gates, resolving false failures caused by shared state before making the checks blocking.

• Built reusable test data for 9 account and entitlement states; aligned review standards and decision owners across the participating teams. Working with partner teams, kept turnaround time within the agreed operating window.
• Reviewed a proposed change against the existing interface contract, reproduced a reviewer’s edge case, and added the missing test or example before merging the change.
• Investigated a failure reported by a downstream team using the exact version and input they supplied. Reduced it to a reproducible test, delivered the fix with compatibility notes, and confirmed the original case passed before closing the report.

• Introduced defect escape reviews by source, detection gap, and prevention action; aligned review standards and decision owners across the participating teams
• Built an isolated fixture with normal, malformed and interrupted inputs; recorded the expected response before running the implementation so failures were distinguishable from a changed assumption.
• Packaged the reproduction steps, configuration and regression tests with the project; checked the instructions from a clean environment and documented the unsupported cases instead of claiming production readiness.
• Owned the independent regression fixture using isolated inputs, resolved a failing edge case and released a reproducible test package with expected outputs.

Relevant coursework: Algorithms, operating systems, databases, computer networks

Test strategy · Playwright · API testing · Risk analysis · CI pipelines · Defect triage

• Published an independent technical note using the project’s before-and-after traces, explaining the failed assumption, regression coverage and cases the implementation does not support.