QA Automation Engineer

We are hiring QA Engineers who can do both manual testing and test automation. You will own quality end-to-end for the features, design and execute test cases, do exploratory and regression testing, and then automate the high-value flows in Playwright with TypeScript so they are protected forever. This is not a "manual now, automation later" role; both happen in the same sprint, by the same person.
The core responsibilities for the job include the following:
Manual Testing and Quality Ownership:
Own quality for features from requirements review through release sign-off.
Design, document, and execute test cases covering functional, regression, integration, system, and exploratory testing across our web app, responsive mobile web, and Chrome extension.
Participate in sprint planning, refinement, and stand-ups; review user stories and surface ambiguities before development starts.
Reproduce, isolate, and document defects with clear repro steps, expected vs. actual behavior, logs, and screenshots/recordings.
Maintain test case repositories in Confluence; keep documentation current as features evolve.
Test Automation:
Design, build, and maintain UI and API automation in Playwright with TypeScript using the Page Object Model, fixtures, and data-driven patterns.
Write automation alongside the feature, not after release. Automate critical paths within the same sprint as the manual test pass.
Build and maintain API test coverage using Playwright's request fixture; supplement with Postman for exploratory and contract checks where appropriate.
Tag, organize, and parallelize tests so the suite stays fast.
Investigate and fix flaky tests with the same rigor as production bugs; flakiness erodes trust in the suite.
Maintain CI/CD integration via Bitbucket Pipelines: PR validation, nightly cross-browser regression, post-deploy production smoke, and scheduled health checks.
Collaboration and Process:
Log, track, and report defects in Jira; collaborate with cross-functional teams in an Agile / Scrum environment with weekly releases.
Partner with frontend engineers contributing their first Playwright tests: review their PRs and help establish conventions (data-testid usage, locator priorities, and naming).
Contribute to the weekly "escaped bug" review when a production bug slips through, help analyze why, and convert it into a permanent regression test.
Report on quality metrics: open defects, severity distribution, regression coverage, automation suite runtime, and flake rate.
Requirements:
Our stack is intentionally TypeScript end-to-end, so QA and engineering share one language. Frontend engineers also contribute Playwright tests, so you will collaborate closely with developers and help shape conventions, frameworks, and CI pipelines.
Experience: 2 to 5 years in software quality assurance, with hands-on exposure to both manual testing and UI automation.
2+ years of hands-on QA experience on web applications (SaaS / B2B preferred), with real exposure to BOTH manual testing and UI automation.
Strong manual test design skills: equivalence partitioning, boundary analysis, decision tables, and exploratory charters; the ability to write test cases that another QA could pick up and execute.
Hands-on experience with Playwright (preferred) or a similar modern framework. Solid TypeScript / JavaScript fundamentals: async / await, promises, modules, basic typing, and the ES standard library.
Working knowledge of test framework concepts: Page Object Model, fixtures, data-driven testing, and parallel execution.
Proficient at writing reliable selectors; prefers semantic locators (getByRole, getByLabel, getByTestId), but comfortable with XPath and handling dynamic elements when needed.
Hands-on API testing experience: REST, JSON, and auth flows. Comfortable with the postman and/or playwright's requested fixture.
Solid grasp of HTTP, browser developer tools (network tab, console, and application storage), and cross-browser/responsive testing.
Experience integrating automated tests into a CI/CD pipeline (Bitbucket Pipelines preferred; Jenkins / GitHub Actions experience translates).
Comfortable with Git workflows: feature branches, pull requests, and code reviews.
Experience with Jira for defect tracking and Confluence for documentation.
Strong analytical and debugging skills to isolate whether a failure is product, test, environmental, or data and act on it independently.
Excellent written and verbal communication: your bug reports and test plans should be unmistakable.
Nice to Have:
Experience testing Chrome extensions or other browser-integrated products.
Exposure to performance/load testing tools like K6 JMeter, Gatling, or Artillery.

Experience
2-5 yrs