Back to Jobs

QA Testing Engineer

Not Disclosed

Job Description & Details

The gig is a contract QA Automation role focused on building Playwright test suites for a New York‑based team. You’ll be writing end‑to‑end tests, wiring them into Azure DevOps or Jenkins pipelines, and keeping the test codebase clean enough for the devs to actually rely on it.

What You'll Actually Be Doing

You’ll spend most of your day authoring Playwright scripts that cover UI, API, and integration scenarios, then hooking those scripts into the CI pipeline so they run on every PR. Expect a lot of back‑and‑forth with developers to nail down acceptance criteria, plus hunting down flaky tests and fixing them before they break the build. You’ll also be logging bugs in JIRA or Azure DevOps and helping the team interpret test results to drive quality decisions.

The Core Tech Stack

The non‑negotiables are Playwright for both UI and API testing, plus a solid grasp of CI/CD tools like Azure DevOps, GitHub Actions, or Jenkins. You’ll also need to be comfortable with API testing utilities (Postman, REST Assured) and have a working knowledge of mainframe DB2/CICS environments, since the stack mentions IT IS_AMS_Mainframe administration. The idea is you can spin up a cross‑browser test suite, push it through the pipeline, and have it report cleanly to the team.

Interview Expectations

  1. How would you troubleshoot a flaky Playwright test that only fails on Chrome in CI? The interviewer wants to see your debugging workflow—checking network conditions, adding retries, using test hooks, and possibly isolating the test to identify environment‑specific issues.
  2. Describe how you’d integrate Playwright tests into an Azure DevOps pipeline and ensure test results are visible to the team. They’re looking for concrete steps: adding a pipeline task, publishing test results as JUnit XML, gating PR merges on test pass/fail, and possibly using environment variables for secrets.

Application Advice

Tailor your resume to highlight every Playwright project you’ve shipped—mention the frameworks you built, the browsers you covered, and how you wired them into Azure DevOps or Jenkins pipelines. Sprinkle in keywords like “CI/CD integration,” “JIRA bug tracking,” “API testing with Postman/REST Assured,” and “cross‑browser automation.” If you have any exposure to DB2 or CICS, surface that too; it matches the niche mainframe admin skill set they listed. A concise bullet that reads Designed Playwright‑based end‑to‑end test framework, integrated with Azure DevOps, reduced regression cycle by 30% will get past most ATS filters.