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

• 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
• Test at every layer: UI behavior, API contracts and response shapes, and the resulting database state
• Write SQL queries to verify that what the UI shows matches what the system actually stored
• Own bug reporting end-to-end: reproduce reliably, isolate the trigger, document exact steps, and verify the fix
• Test numeric and reporting output for correctness — totals, boundaries, rounding, aggregation, and date ranges
• Validate role-based access control: what each user role should and shouldn't be able to see or do
• Test date/time and timezone behavior, pagination, filtering, sorting, and data export (Excel/CSV/PDF) parity
• Pick up unfamiliar applications and assess where their real risk sits, rather than testing only what's easy to reach
• Participate in requirement reviews and call out ambiguity, missing acceptance criteria, and untestable specs before development starts
• Help define our QA process — test strategy, automation coverage targets, regression scope, release criteria, and definition of done

Required Qualifications

• 3+ years professional QA / software testing experience
• Hands-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
• Ability to debug and stabilize flaky automation — locator strategy, waiting and race conditions, parallelism and test isolation
• Working 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
• Understanding of the testing pyramid, with the judgment to place a given test at the right level
• Solid manual testing fundamentals — test case design, boundary and negative testing, exploratory testing, regression planning
• API testing experience — Postman, REST clients, or code-based API tests; comfortable reading JSON payloads
• Working SQL skills — able to write SELECTs with joins and filters to verify application data independently
• Comfortable in TypeScript or JavaScript to the level Playwright authoring demands (async/await, promises, modules)
• Experience testing web applications, including browser dev tools for network and console inspection
• Adaptable across products and domains — you've tested more than one kind of application and can context-switch without losing rigor
• Clear, reproducible bug reports with precise steps, expected vs. actual, and supporting evidence
• Familiarity with Agile/Scrum, sprint-based delivery, and a bug-tracking tool (Azure DevOps, Jira, or similar)
• Attention to detail with the judgment to know what actually matters

Preferred Qualifications

• Advanced Playwright — API request context, network interception/mocking, trace viewer and debugging workflows, visual comparison, custom fixtures, sharding for parallel CI runs
• Vitest and React Testing Library specifically — querying by role/label, user-event interactions, and mocking modules and API layers
• xUnit with Moq specifically — fact/theory-based tests, fixtures, and mocking service and repository dependencies
• Experience testing systems where output must be numerically exact and reconcile against a source of truth
• High-volume event-processing or data-intensive application experience
• Experience testing asynchronous / queue-based systems and eventual consistency
• Familiarity with C# — enough to read backend code, follow an xUnit test, and understand what an API is doing
• Azure DevOps Pipelines or other CI/CD experience running automated tests in a pipeline
• Performance or load testing exposure (JMeter, k6, or similar)
• Accessibility testing (WCAG) and cross-browser testing experience
• Experience selecting or standing up test management tooling (TestRail, Azure Test Plans, Xray, or similar)
• Experience being the first or only QA on a team and building an automation practice from scratch
• Experience supporting multiple products or teams at once and prioritizing across them

What We Value

• Clear, direct communication — say what you mean, flag problems early, ask questions when something is unclear
• Curiosity about how things break, not just whether the happy path works
• Verifying the actual behavior — check the API response, check the database row; "the UI looked right" is not a passing test
• Automation that earns trust: a failing test means something is actually broken, and a green suite means something
• Testing at the cheapest layer that can catch the defect, rather than pushing everything up to E2E
• Challenging risky or incorrect decisions instead of silently going along, including pushing back on "it works on my machine"
• QA as a partner in building quality, not a gate at the end of the sprint
• Adaptability — willingness to learn a new product or domain rather than staying in one comfortable corner
• Pragmatism over over-engineering — automate what earns its keep and test what actually carries risk

In order to apply, please submit your CV in English