{"id":1583435,"url":"https://alion.io/job/transperfect-games-testing-engineer-santo-domingo","title":"Testing Engineer (Santo Domingo)","company":{"id":2066542,"name":"TransPerfect Games","domain":"transperfectgames.com","url":"https://alion.io/company/transperfectgames","size_band":"1001-5000","is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Recruitee","truth_index":{"grade":"B","score":70,"open_postings":553,"ghost_share":0.505,"stale_share":0,"repost_share":0,"time_to_fill_p50_days":43,"computed_at":"2026-10-05T05:45:15Z"}},"role":"QA","role_family":"QA","seniority":"middle","employment_type":null,"work_mode":"on_site","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["Santo Domingo, Dominican Republic"],"countries":["DO"],"hiring_countries":[],"hiring_countries_total":0,"salary":null,"salary_estimate":null,"experience_years_min":3,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"Agile","optional":false},{"name":"ASP.NET Core","optional":false},{"name":"Azure","optional":false},{"name":"Azure DevOps","optional":false},{"name":"Azure SQL Database","optional":false},{"name":"CI/CD","optional":false},{"name":"Figma","optional":false},{"name":"JavaScript","optional":false},{"name":"Jest","optional":false},{"name":"Jira","optional":false},{"name":"Moq","optional":false},{"name":"Playwright","optional":false},{"name":"Postman","optional":false},{"name":"React.js","optional":false},{"name":"Rest API","optional":false},{"name":"Scrum","optional":false},{"name":"SQL","optional":false},{"name":"TypeScript","optional":false},{"name":"Vitest","optional":false},{"name":"xUnit","optional":false},{"name":"C#","optional":true},{"name":"JMeter","optional":true},{"name":"k6","optional":true},{"name":"TestRail","optional":true}],"status":"live","first_seen_at":"2026-09-25T19:39:57Z","employer_posted_date":"2026-09-25","last_verified_at":"2026-10-06T01:48:32Z","board_verified":true,"closed_at":null,"days_open":10,"trust":{"level":"ok","repost_count":0,"flags":["company_stale"],"days_open":9},"description":"We're hiring a mid-level Testing 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.\nWe'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.\nThis 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.\nTech Stack\nE2E & API Automation: Playwright (E2E - our primary automation framework), Postman / REST clients for API testing\n\nUnit & Integration Testing: Vitest + React Testing Library (frontend), xUnit + Moq (.NET backend) - developer-owned suites you'll help extend and hold to account\n\nTest Management: Azure DevOps Boards (test plans, bug tracking) - tool selection beyond this is open, and yours to influence\n\nThe Applications Under Test: React 18 + TypeScript frontends, ASP.NET Core (.NET 8) APIs, Azure SQL databases, Azure Functions and queue-based background processing\n\nSupporting Tools: Azure SQL / Azure Data Studio (SQL queries for verification), Azure DevOps Pipelines, Application Insights, browser dev tools, Figma (design reference)\n\nResponsibilities\nDesign, build, and own our Playwright E2E automation suite - architecture, page objects/fixtures, test data strategy, and CI integration\n\nWrite 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\n\nRun Playwright in CI/CD pipelines across browsers, triage failures, and keep the suite green and fast enough that people actually rely on it\n\nWrite, maintain, and execute test cases for new features and regression cycles\n\nWork 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\n\nReview 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\n\nHelp 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\n\nTest at every layer: UI behavior, API contracts and response shapes, and the resulting database state\n\nWrite SQL queries to verify that what the UI shows matches what the system actually stored\n\nOwn bug reporting end-to-end: reproduce reliably, isolate the trigger, document exact steps, and verify the fix\n\nTest numeric and reporting output for correctness - totals, boundaries, rounding, aggregation, and date ranges\n\nValidate role-based access control: what each user role should and shouldn't be able to see or do\n\nTest date/time and timezone behavior, pagination, filtering, sorting, and data export (Excel/CSV/PDF) parity\n\nPick up unfamiliar applications and assess where their real risk sits, rather than testing only what's easy to reach\n\nParticipate in requirement reviews and call out ambiguity, missing acceptance criteria, and untestable specs before development starts\n\nHelp define our QA process - test strategy, automation coverage targets, regression scope, release criteria, and definition of done\n\nRequired Qualifications\n3+ years professional QA / software testing experience\n\nHands-on Playwright experience - required, and specifically implementation experience.** You have built or substantially extended a Playwright suite yourself: written the tests, structured the project, handled auth/session state and test data, and wired it into CI. Experience limited to executing someone else's suite is not what we are looking for here\n\nAbility to debug and stabilize flaky automation - locator strategy, waiting and race conditions, parallelism and test isolation\n\nWorking familiarity with unit/integration testing frameworks and mocking - Vitest, Jest, xUnit, NUnit, Moq, or equivalent. You should be able to read a developer's test suite, judge whether it genuinely covers the behavior, and add a test to it yourself\n\nUnderstanding of the testing pyramid, with the judgment to place a given test at the right level\n\nSolid manual testing fundamentals - test case design, boundary and negative testing, exploratory testing, regression planning\n\nAPI testing experience - Postman, REST clients, or code-based API tests; comfortable reading JSON payloads\n\nWorking SQL skills - able to write SELECTs with joins and filters to verify application data independently\n\nComfortable in TypeScript or JavaScript to the level Playwright authoring demands (async/await, promises, modules)\n\nExperience testing web applications, including browser dev tools for network and console inspection\n\nAdaptable across products and domains - you've tested more than one kind of application and can context-switch without losing rigor\n\nClear, reproducible bug reports with precise steps, expected vs. actual, and supporting evidence\n\nFamiliarity with Agile/Scrum, sprint-based delivery, and a bug-tracking tool (Azure DevOps, Jira, or similar)\n\nAttention to detail with the judgment to know what actually matters\n\nPreferred Qualifications\nAdvanced Playwright - API request context, network interception/mocking, trace viewer and debugging workflows, visual comparison, custom fixtures, sharding for parallel CI runs\n\nVitest and React Testing Library specifically - querying by role/label, user-event interactions, and mocking modules and API layers\n\nxUnit with Moq specifically - fact/theory-based tests, fixtures, and mocking service and repository dependencies\n\nExperience testing systems where output must be numerically exact and reconcile against a source of truth\n\nHigh-volume event-processing or data-intensive application experience\n\nExperience testing asynchronous / queue-based systems and eventual consistency\n\nFamiliarity with C# - enough to read backend code, follow an xUnit test, and understand what an API is doing\n\nAzure DevOps Pipelines or other CI/CD experience running automated tests in a pipeline\n\nPerformance or load testing exposure (JMeter, k6, or similar)\n\nAccessibility testing (WCAG) and cross-browser testing experience\n\nExperience selecting or standing up test management tooling (TestRail, Azure Test Plans, Xray, or similar)\n\nExperience being the first or only QA on a team and building an automation practice from scratch\n\nExperience supporting multiple products or teams at once and prioritizing across them\n\nWhat We Value\nClear, direct communication - say what you mean, flag problems early, ask questions when something is unclear\n\nCuriosity about how things break, not just whether the happy path works\n\nVerifying the actual behavior - check the API response, check the database row; \"the UI looked right\" is not a passing test\n\nAutomation that earns trust: a failing test means something is actually broken, and a green suite means something\n\nTesting at the cheapest layer that can catch the defect, rather than pushing everything up to E2E\n\nChallenging risky or incorrect decisions instead of silently going along, including pushing back on \"it works on my machine\"\n\nQA as a partner in building quality, not a gate at the end of the sprint\n\nAdaptability - willingness to learn a new product or domain rather than staying in one comfortable corner\n\nPragmatism over over-engineering - automate what earns its keep and test what actually carries risk\n\nIn order to apply, please submit your CV in English","description_format":"text","description_chars":8200,"description_truncated":false,"requirements":{"experience_years_min":3,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[],"hiring_excludes":[],"relocation_offered":false,"industries":["Design & Creative","Sales & Marketing"],"lifecycle":[{"event":"open","at":"2026-10-01T13:48:31Z"}],"visa":[],"liveness":{"score":62,"band":"ok","label":"Likely open","p_open":1,"p_active":0.621,"p_room":1,"age_days":9,"expected_fill_days":43,"reasons":["conf:1","stale_co","velocity","win:early","comp:brand"],"computed_at":"2026-10-05T05:45:15Z"},"pay":null,"html_url":"https://alion.io/job/transperfect-games-testing-engineer-santo-domingo","json_url":"https://alion.io/job/transperfect-games-testing-engineer-santo-domingo.json","meta":{"generated_at":"2026-10-06T02:16:26Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","about":"Alion is a live layer of people, companies and AI agents: who they are, whether they are real and active right now, what they do and how to work with them, readable by people and by agents and paid per call.","catalog":"https://alion.io/catalog.json","usage":{"tier":"crawler","counted_by":"address","units_charged":1,"used_today":3303,"day_limit":5000,"remaining_today":1697,"minute_limit":60,"resets_at":"2026-10-07T00:00:00Z"}},"offers":[{"id":"company.slices","title":"One company in depth, by slice","status":"live","price":{"credits":0.02,"usd":0.002,"plus_per_slice":{"credits":0.05,"usd":0.005}},"unit":"per company, plus each slice with data","note":"the employer in depth","call":{"mcp_tool":"get_company","arguments":{"id":2066542},"rest":"https://alion.io/mcp/rest/get_company?id=2066542"},"human":"https://alion.io/catalog?offer=company.slices&for=job%2Ftransperfect-games-testing-engineer-santo-domingo"},{"id":"market.stats","title":"A market slice: pay, demand and time to fill","status":"live","price":{"credits":1,"usd":0.1},"unit":"per slice","note":"pay, demand and time to fill for this role and place","call":{"mcp_tool":"market_stats"},"human":"https://alion.io/catalog?offer=market.stats&for=job%2Ftransperfect-games-testing-engineer-santo-domingo"},{"id":"job.search","title":"Open jobs by role, technology, place, pay and visa","status":"live","price":{"credits":0.02,"usd":0.002},"unit":"per posting in a list","note":"similar open postings","call":{"mcp_tool":"search_jobs"},"human":"https://alion.io/catalog?offer=job.search&for=job%2Ftransperfect-games-testing-engineer-santo-domingo"},{"id":"company.verify","title":"Is this company real and active right now","status":"pilot","price":null,"unit":"per company","request":{"url":"https://alion.io/catalog/request","method":"POST","body":"{\"offer\": \"company.verify\", \"for\": \"job/transperfect-games-testing-engineer-santo-domingo\", \"note\": \"what you need it for\"}"},"human":"https://alion.io/catalog?offer=company.verify&for=job%2Ftransperfect-games-testing-engineer-santo-domingo"}]}