Remote
Senior QA Engineer
About this role
ABOUT APHEX We’re the construction planning platform replacing outdated spreadsheets with multiplayer tools that delivery teams love. Major contractors like BAM, Balfour Beatty, SKANSKA, Kier, MACE, and Murphy use Aphex to deliver projects ranging from £50 million to multi-billion-pound megaprojects. We’re tackling an industry that drives 10% of global GDP yet has seen productivity decline for 20 years. It’s time for change.
ABOUT THE ROLE Aphex is building out its internal QA function with dedicated, embedded product-team QA — a single owner of quality for a product area. You'll be embedded directly in the product team as its dedicated QA, owning quality for your area, Planner or Diary, end-to-end across the SDLC, from ideation through to post-release. You're the quality voice from the moment a feature is scoped, and you own the E2E automation suite (Playwright/TypeScript) that guards it in CI across multiple environments and regions.
WHAT YOU'LL DO - Own quality end-to-end for your product area. Engage from ideation and refinement — shaping clear, testable acceptance criteria and surfacing risk before code is written — through development and release sign-off, to post-release verification in production. - Own and extend the E2E automation suite — Playwright/TypeScript, Page Object Model, per-worker isolation, seeded test data. - Drive test reliability.
Diagnose and eliminate flakiness at the root — readiness/synchronization over fixed waits, race conditions, shared-state leaks — using traces, videos, and network/console logs to isolate the real mechanism. - Read the application source to understand why something fails before touching the test — no guess-and-rerun. - Review automation PRs for correctness and maintainability; set and uphold standards across the suite.
- Blend automation with exploratory/manual testing — exercise judgment on what's worth automating and what isn't. - Partner day-to-day with engineers and PMs in an Agile flow — raise well-evidenced defects, and reliably tell a real product bug from a test artifact. - Close the loop post-release — verify in production, watch for regressions, and feed findings back into the team. - Maintain the pipeline — CI (GitHub Actions), test reporting (Qase), and test-data/seeding infrastructure.