QA Automation Engineer

They are hiring a QA automation engineer to bring that intent, and more than that, to bring an opinion. This role defines what quality assurance looks like on a team building at AI speed. If you have thought hard about that question and can back your answer with a method and real outcomes, this is a rare chance to build the practice rather than inherit it.

What you will do

• Own and grow automated test coverage across a suite of applications, with Playwright as the primary framework

• Define and defend how testing works in an AI assisted development environment, and put your approach into practice

• Use AI tooling deliberately in building and maintaining tests, with a clear method for where it helps and where human judgment is required

• Dig into existing applications, understand what each feature does and why users rely on it, and build coverage that reflects real intent

• Mentor a junior test engineer and raise the quality bar for the whole team

• Mid to senior QA automation experience with real ownership of automated coverage

• Playwright strongly preferred; deep experience in a comparable modern framework considered

• Unit testing depth alongside end to end automation

• Demonstrated, articulate use of AI tooling in test development: how you use it, why, and what outcomes it produced

• A defensible point of view on QA in the age of AI assisted development

• Communication and flexibility suited to a fast moving product team

• Contract to hire: contract through Trustech, converting to a full time salaried role with the client

• Hourly rate during contract: $55 to $75 per hour, depending on experience

• Conversion salary range: $120,000 to $150,000

• Benefits: eligible for Trustech contractor benefits during the contract period, including health coverage options. Upon conversion, client benefits include PTO and healthcare

• Fully remote within the United States

Our client is a growing legal technology software company whose engineering team builds with AI coding tools every day. That speed creates a real quality question, and they have a clear point of view on it: the tooling that writes the code should not be the only author of its tests. Tests carry intent, and intent comes from a person who understands what a feature is for.