Vetted QA Automation Engineers

“QA professional focused on CRM workflow and case management releases, owning end-to-end validation from staging through release readiness. Demonstrated ability to catch critical UI-to-backend mapping defects early using API/DB validation and audit logs, then prevent recurrence by adding automated edge-case tests into CI.”

“QA automation engineer with hands-on ownership of Selenium (C#) and Cypress (JavaScript) suites, including CI integration in GitLab with PR smoke gating and nightly regressions with JUnit reports/screenshots. Drove a reported ~60% reduction in manual effort, improved suite maintainability through reuse/merging tests, and proactively shaped requirements/acceptance criteria in sprint planning to prevent defects (including claims calculation and server/log-related issues).”

“QA automation engineer who owned an end-to-end test suite for a financial payments application, building cross-layer E2E coverage (UI/API/DB) and integrating it into CI with smoke-on-commit and nightly regression. Caught high-impact issues including duplicate payments caused by missing idempotency in backend retry logic and an RBAC authorization gap, and has hands-on experience stabilizing flaky Cypress tests via network-call synchronization.”

Joon Im

Screened

Mid-level QA Automation Engineer (SDET) specializing in API and test automation

Los Alamitos, CA4y exp

“QA automation engineer who owns and modernizes end-to-end test automation across Selenium (Java) and Cypress (JavaScript), integrating suites into GitLab CI/CD with PR gating, nightly runs, and Sauce Labs reporting/recordings. Demonstrated impact by catching a session-timeout workflow issue in CI that manual testing missed and by reducing flakiness through stack upgrades, coding standards, and API-synchronized assertions.”

“Game-studio QA tester with full lifecycle experience (feature kickoff through release/live updates), strong in structured test planning, edge-case discovery, and disciplined defect tracking. Partners closely with engineers via Jira/standups, providing detailed repro steps, logs, and evidence, and builds regression coverage to prevent recurring UI/data-loss issues.”