QA Engineer (Santo Domingo)

We're hiring a mid-level QA Engineer to own quality across our product portfolio. You'll be the first dedicated QA voice on the team, which means you get to shape how we test rather than inherit someone else's process. We're not hiring for a single project. You'll move between products and problem domains as priorities shift, so we're looking for someone adaptable who can get oriented in an unfamiliar application quickly and figure out where its risk actually lives. This is a hands-on role across manual and automated testing, and **Playwright is central to it** — you'll be the person who builds and owns our E2E automation suite, not just runs it. You'll also work inside the unit and integration suites our developers maintain (Vitest on the frontend, xUnit and Moq on the backend), write and execute test cases, and dig into API responses and database rows to confirm what actually happened rather than what the screen claimed. Our applications handle data where a wrong number has real consequences, so we want someone genuinely curious about how systems break. Tech Stack E2E & API Automation: Playwright (E2E — our primary automation framework), Postman / REST clients for API testing Unit & Integration Testing : Vitest + React Testing Library (frontend), xUnit + Moq (.NET backend) — developer-owned suites you'll help extend and hold to account Test Management : Azure DevOps Boards (test plans, bug tracking) — tool selection beyond this is open, and yours to influence The Applications Under Test : React 18 + TypeScript frontends, ASP.NET Core (.NET 8) APIs, Azure SQL databases, Azure Functions and queue-based background processing Supporting Tools : Azure SQL / Azure Data Studio (SQL queries for verification), Azure DevOps Pipelines, Application Insights, browser dev tools, Figma (design reference) Responsibilities Design, build, and own our Playwright E2E automation suite — architecture, page objects/fixtures, test data strategy, and CI integration Write Playwright tests that are stable and trustworthy: proper auto-waiting and web-first assertions, no arbitrary sleeps, and no flake anyone has learned to ignore Run Playwright in CI/CD pipelines across browsers, triage failures, and keep the suite green and fast enough that people actually rely on it Write, maintain, and execute test cases for new features and regression cycles Work inside the developer-owned unit and integration suites — Vitest + React Testing Library on the frontend, xUnit + Moq on the .NET backend — adding regression tests for the bugs you find and pushing coverage down to the cheapest layer that can catch a given defect Review test coverage in pull requests: whether a fix shipped with a test that actually fails without it, and whether the assertion proves the behavior or just that nothing crashed Help decide what belongs in a unit test, an integration test, or an E2E test, so the Playwright suite doesn't become the dumping ground for everything …