Internship QA Engineer resume example

• Under supervision, mapped acceptance criteria to automated regression cases and exploratory charters; isolated flaky timing assertions so a passing build represented reproducible behavior.
• The team mapped payment-state risks into 68 API and browser scenarios; I supported research preparation, validation, and documentation under mentor review. The team removed a recurring quality failure from the reviewed workflow; confirmed with my mentor that my contribution was limited to the assigned support and validation work.
• The team stabilized the top 45 end-to-end tests by replacing time waits with state assertions; I supported research preparation, validation, and documentation under mentor review. The team reduced repeat defects in the next release or review cycle; confirmed with my mentor that my contribution was limited to the assigned support and validation work.
• Under supervision, owned test automation for the checkout regression suite using Selenium, reducing manual repeat checks from 90 to 35 minutes while retaining failed-run screenshots.
• Under supervision, 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.

• In a mentor-reviewed simulation, 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.
• As a second supervised exercise, 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.
• Under supervision, the team introduced defect escape reviews by source, detection gap, and prevention action; I supported research preparation, validation, and documentation under mentor review
• 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

• 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.