Senior QA Engineer

Job description

## 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. - Build scalable systems and deterministic quality gates. Our principle is systemic, not silver-bullet — you solve problems at the source and build gates that make quality repeatable and head off whole classes of issues, rather than patching each symptom as it surfaces. - Take an idea from concept to implementation, independently — you can ideate, stress-test, and build a solution end-to-end, and you enjoy experimenting with new approaches from a solid engineering foundation. ### **Hard requirements** - 5+ years in software QA, with substantial hands-on E2E UI automation. - Strong with a modern E2E framework — Playwright preferred (Cypress/Selenium transferable) — and JavaScript/TypeScript. - Page Object Model / test-architecture experience — you structure automation for maintainability and reuse (POM, shared fixtures, clear separation of concerns), not brittle one-off scripts. - Demonstrable flaky-test remediation — you've made an unreliable suite deterministic, not just written new tests. - Comfortable reading application code (front-end, and enough back-end to trace a failure to its source). - CI/CD + Git PR workflow (GitHub Actions or equivalent); confident debugging from CI artifacts. - Clear, evidence-based written communication — bug reports and PR reviews someone unfamiliar can act on. - Embedded-QA mindset — comfortable owning quality across the whole lifecycle, not just executing or automating tests handed to you. ### **Nice to have** - Playwright specifically; test-management tooling (Qase/TestRail); multi-environment/region test configuration. - Test architecture at scale — parallelism, isolation, seeded/cloned fixtures. - Complex, stateful SPA UIs — scheduling/Gantt boards — and auth flows (e.g. WorkOS). - Experience standing up or maturing a QA function - Construction-tech or complex B2B SaaS domain exposure. ### **How you work** - **Root-cause mindset**; you dig for the mechanism instead of reaching for the masking fix - **Pragmatic judgment**; you test behaviour, not incidental state, and you know when *not* to file a ticket. - **Ownership and thoroughness**; you leave the suite more reliable than you found it. - **Proactive collaborator**; clear with engineers, PMs, and non-technical stakeholders alike. **What We Offer** - A high-performing team: Be part of and contribute to a genuinely collaborative and motivated team - Genuine development: Ongoing training, learning, and coaching to get better every day - A focus on culture: At Aphex, we are focused on making real impact, together, and strive to walk the talk on that every day - Growth opportunities: As Aphex scales across new markets, your career can scale with it - Annual global offsite: In 2025 our team met for a week in Da Nang, Vietnam - you’ll need to join us to see where we have planned in 2026! - One annual all-expenses-paid international team offsite (we've been to Vietnam and Thailand — where to next?) - Annual training allowance - MindFi EAP access - Employee Referral Program ### Equal Employment Opportunity (EEO) Statement *Our company does not discriminate in employment on the basis of race, color, religion, gender identity or expression, national origin, age, disability, or other non-merit factors. At Aphex, we believe our team should reflect the variety of perspectives in the world we build for. We've noticed that qualified candidates from underrepresented groups sometimes hesitate to apply unless they meet 100% of the listed requirements, while others might apply when meeting just 60%. If you're excited about Aphex and believe you have the core skills to succeed in this role, we encourage you to apply - even if you don't check every box in the description. Your unique perspective might be exactly what we need. If you need any accommodations during the interview process, please let us know.*