Head of Software QA

The Head of QA leads LedgerRun's QA function for ClinRun: the QA team, quality strategy, release readiness and UI test automation. As QA moves to automation-first UI testing in Playwright, this role is accountable for a fast, trusted quality signal on every change and every release.

What you’d own

People and team

• Regular 1:1s with every direct report
• A QA career ladder with clear expectations and promotion criteria at each level
• A development plan for each team member, with automation capability addressed directly
• Performance reviews on the company cycle, and underperformance addressed early with a clear plan
• QA hiring: role definitions, interview loop and onboarding

Quality strategy and release readiness

• A coverage map by functional area - automated, manual, untested - kept current and visible to engineering
• Test plans for major initiatives, produced during quarterly planning process
• A go/no-go recommendation, backed by test results and open risk, for every release and hotfix
• Test evidence captured through the pipeline and retained audit-ready for SOC and SOX
• Best practices for QA processes within agile development

Test automation

• Ownership of the Playwright framework after handover: coding standards, code review and documentation
• A path - training, hiring or both - to every QA engineer writing and maintaining automated tests
• Migration plan for all current manual regression testing to be automated
• Flaky tests tracked on a visible list, each with an owner, and fixed or quarantined quickly
• A point of view on AI-assisted testing and how we accelerate adoption in the team

Metrics

• The weekly QA metrics review: defect escape rate, suite stability, coverage and migration progress
• A monthly quality report to engineering leadership
• Root-cause analysis for clusters of production defects, with follow-up actions tracked to closure

What we’re looking for

• 10+ years' experience in software QA required
• Bachelor's Degree required
• People leadership: hiring, coaching and performance management, and leading a team through change rather than only running steady state
• QA strategy: risk-based testing, coverage planning, and release decisions you can defend - including what you chose not to test
• Automation depth: test architecture, CI pipelines and flakiness; able to read and review Playwright/TypeScript and set technical direction, without writing tests daily
• Data-driven: defines quality metrics that change behavior, and uses them in decisions
• Agile delivery: experience leading QA in agile delivery cycles, ideally in a regulated or audited environment