QA Engineer

The Role We're hiring a QA Engineer (Automation) embedded in the engineering team, peer to our engineers. This is not a role where someone hands you a test plan and you execute it. You'll read PRDs alongside engineers, define testable acceptance criteria, write the tests, wire them into CI, and build the infrastructure that makes coverage visible across the team. You'll also own the test environments and the go-live gate that every new client onboarding must pass before it reaches them. The first phase will be an audit of what exists. Primary Scope PRD-to-test coverage: Read PRDs and produce integration + E2E test coverage before (or alongside) feature development not after the fact. Work with product to ensure acceptance criteria are testable before dev starts.Configuration matrix harness: Build and maintain parameterised tests that run critical flows (session open order payment close, online ordering, loyalty accrual, delivery routing) across the combinations of settings that vary client-to-client.Go-live readiness gate: Own a runnable suite that validates a new client's specific configuration before they go live. This replaces the current pattern of "onboard client discover surprise bug firefight." The gate should be reproducible, fast enough to run per onboarding, and expandable as new config options ship.Test environment ownership: Design and maintain seeded test tenants with known, stable configurations (e.g. multi-tax + loyalty + online ordering; dine-in only; delivery with sectors; takeout with printer routing). Tests that depend on predictable environments stay predictable.CI pipeline integration: Wire tests into GitHub Actions as quality gates. Coverage and pass/fail status visible to the whole team on every PR. Regressions in covered flows block merges.Stability visibility: Track coverage by feature area and pass rate trends. Build toward a dashboard start with the numbers, make them accessible to engineering and product.Tertiary Scope Load and performance testing: Foodops POS has predictable peak load patterns lunch rush, dinner rush, end-of-day session close. Introduce load testing (k6, Locust, or equivalent) to validate behaviour under concurrent use before it becomes a client issue.Multi-product expansion: As Foodops stabilises, extend the quality function to other Hubits products.What Success Looks Like E2E and integration coverage across the critical flows. The CI pipeline blocks any merge that regresses a covered flow. A new client onboarding no longer produces a surprise bug we haven't seen before because the go-live gate caught it first. A live stability dashboard. Onboarding issues-per-client is a tracked, visible metric that is trending down. Coverage gaps are surfaced proactively, not discovered by accident. What You'll Bring 4+ years of QA engineering experience, with a substantial portion in test automation not manual testing that grew into scripting.Demonstrable experience building or substantially improving an E2E test suite from an existing baseline not just adding tests to an existing framework someone else built.Strong with Playwright or clear evidence you've moved between E2E tools before and can move to Playwright quickly (we use it across the organisation).Comfortable testing .NET (C#) APIs: HTTP-level integration tests, database seeding, test environment setup.Hands-on experience wiring tests into GitHub Actions as blocking quality gates, not just running them locally.Able to read a PRD and independently produce a test plan with edge cases and combination coverage without being told exactly what to test.Clear communicator: can explain a coverage gap or a test architecture decision to engineers and non-engineers alike.Nice to Have Domain experience in food & beverage, retail, or hospitality SaaS you'll immediately understand why the configuration space is complex.Familiarity with load/performance testing tools.Experience designing and maintaining test data environments at scale.Compensation: 35,000.00 - 45,000.00 per month Benefits: Flexible scheduleWork Location: In person .