Senior QA Engineer

Senior QA EngineerDili builds software that helps construction and clean-energy companies manage complex prevailing wage, apprenticeship, and labor compliance requirements.We started Dili because labor compliance is still handled through a mix of spreadsheets, PDFs, manual review, and institutional knowledge, despite determining whether some of the largest construction projects in the country are compliant.Today, we're a team of roughly 30, including a small engineering team working closely with our in-house Compliance team. We're building the infrastructure to turn complex regulatory requirements into software that can be evaluated consistently, explained clearly, and audited.About the RoleOur compliance engine evaluates payroll, timekeeping, worker classifications, prevailing wage rates, apprenticeship requirements, and documentation across frameworks including federal Davis-Bacon, IRA requirements, state prevailing wage laws, and programs such as NYSERDA and Illinois Shines.We're looking for a Senior QA Engineer to own automated product quality, with a particular focus on formally validating our compliance engine and preventing regressions.This is not primarily a manual QA role. You'll build the systems that let us enumerate the compliance scenarios we support, tie them to the underlying regulations, automate their validation, and confidently determine whether a release is correct.You'll work directly with engineers and our Compliance team to turn regulations and interpretations into deterministic, executable tests.What You'll OwnBuild and maintain a registry of compliance scenarios across supported frameworksTranslate regulations, agency guidance, and internal compliance interpretations into structured, testable casesInclude citations to the authoritative regulatory or program sources behind expected behaviorDevelop automated tests that formally verify our compliance engineTest interactions between overlapping federal, state, and program-specific requirementsCover edge cases, exceptions, remediation flows, and previously identified production issuesMake scenarios easy for our Compliance team to review, update, and extendExpand automated coverage across high-risk product workflowsBuild and improve integration, API, end-to-end, and regression test suitesEstablish automated quality gates and release-readiness criteriaImprove visibility into scenario coverage, failures, and known gapsWhat We're Trying to BuildWe want our test infrastructure to become an executable specification of the Dili compliance engine.For each scenario, we should be able to define:The applicable regulation or program requirement, with citationThe relevant project, payroll, worker, wage, and apprenticeship inputsThe expected compliance determinationThe expected calculations, issues, remediation, and reporting behaviorThese scenarios should be understandable by Compliance, version-controlled, automatically executable, and tied directly to release readiness.Your First 90 DaysFirst 30 DaysLearn the architecture of the compliance engine and how our engineering and Compliance teams currently validate changesMap at least one major compliance framework into a structured set of scenariosIdentify the highest-risk gaps in our existing automated coverageBy 60 DaysBuild the initial version of the compliance scenario registryAutomate a meaningful set of high-priority scenarios, including regulatory citations and expected outcomesEstablish a repeatable process for turning production defects into regression testsBy 90 DaysHave critical compliance scenarios running automatically in CIGive Engineering and Compliance clear visibility into coverage, failures, and known gapsEstablish release-readiness criteria that provide concrete evidence that changes to the compliance engine are safe to shipMust HaveStrong experience in software QA, quality engineering, or test automationStrong Python skillsExperience building automated integration and end-to-end test suitesExperience integrating testing into CI/CD and release processesAbility to test a Python/React application in an AWS environmentAbility to systematically reason about complex combinations of rules, inputs, and expected outcomesAbility to turn written requirements into precise, deterministic test casesStrong attention to traceability: not just "did this test pass?", but "why is this the expected behavior, and what requirement supports it?"Ability to work closely with engineers and domain experts to resolve ambiguityNice To HaveRecent hands-on experience with PlaywrightExperience with QA Wolf or similar modern QA toolsExperience with parameterized, property-based, combinatorial, or model-based testingExperience testing payroll, tax, financial, legal, healthcare, insurance, or other rules-heavy softwareExperience with requirements traceability, release certification, or audit evidenceWhat Success Looks LikeDili has a structured inventory of the compliance scenarios we supportCritical scenarios are automatically tested and tied to authoritative regulatory sourcesCompliance can review and contribute to expected behaviorProduction defects become permanent regression testsChanges to regulations or interpretations can be traced to affected scenariosReleases provide clear evidence of what was tested and whether the compliance engine is ready to ship dili