Senior Software Development Engineer in Test

Work Truck Solutions•Chico, CA

1d•$142,000 - $170,000•Remote

About The Position

Work Truck Solutions is the operating system for the commercial vehicle industry. We are the only platform that connects the entire ecosystem: OEMs, upfitters, dealerships, and fleet buyers. By digitizing complex inventory data (chassis + upfits) and streamlining the supply chain, we help dealers sell trucks and ensure American businesses get the mission-critical vehicles they need to work. We are a profitable, growing, and aggressively scaling technology company. This is a senior, hands-on remote role for someone who has built test automation programs before and wants to build the next one with AI at the center. You will own how we test our products end to end: the Playwright suite that covers our dealer software, our internal admin tools and Comvoy.com, the way tests get written and maintained, and the path from a pull request to a release we trust. Our engineering team is moving to an agentic way of working, where much of our code is written by AI agents under human review. You will use AI to write, expand and maintain test coverage far faster than a team could by hand. You will judge every test by the value it provides and remove the ones that don’t earn their place. You will sit on our Platform team, next to the engineers who own our cloud infrastructure, pipelines and environments, and you will work across every product team. A large part of the job is people. You will mentor our existing test engineers, pair with them, review their work and help them become strong automation engineers who build with AI every day.

Requirements

We are looking for a very senior engineer. You have built and run test automation at scale, you have made other test engineers better, and you have already changed how you work because of AI.
Deep test automation experience. 7+ years in test automation or software engineering in test, including designing and owning an automation framework that a whole team used, not just contributing tests to one.
Expert in Playwright. Production experience with Playwright and TypeScript: fixtures, page objects, network interception, authentication state, parallel runs, tracing and tracking down flaky tests.
Judgment about test value. You know when not to test. You can explain why a given test is or isn’t worth keeping, and you have a record of shrinking a bloated suite while making it more useful.
Hands-on AI experience (required). You use AI coding agents in your daily work and can talk about that work in specifics: tests or frameworks you built with AI, prompts or agent configurations you wrote, and a time AI-generated tests went wrong and how you caught it. You are curious about where this is going and want to push it further.
A track record of mentoring. You have coached test engineers, including people moving from manual testing into automation, and you can point to people who grew because of you.
Strong coder in more than one language. You write and read code in multiple languages, including JavaScript/TypeScript and at least one backend language such as C#. You can read our codebase (a .NET backend with SvelteKit and React frontends) and understand what you are testing. You understand the JavaScript behind Playwright well enough to debug async behavior, the browser and the test runner itself. You treat test code as production code.
API and data testing. Experience testing REST APIs and creating and managing test data, including in SQL databases.
CI/CD. Experience running test suites in pipelines (GitHub Actions, Azure DevOps or similar) with a focus on speed, reliability and clear reporting.
Strong Git workflow. Branching, pull requests and code reviews are second nature.

Nice To Haves

Testing in .NET (C#) with MSTest or NUnit, or frontend unit testing with Vitest.
Experience with SvelteKit or React applications.
Experience with Azure.
Testing LLM-powered features or building evaluations for AI output.
Performance, accessibility or visual regression testing.

Responsibilities

Own the test automation strategy. Decide what gets tested at which layer (unit, API, end to end) and drive automated coverage until it is the main way we know a release is safe. Define the measures that show progress, such as coverage, flake rate, run time and escaped defects, and report on them.
Decide what is worth testing. Set a clear bar for test value: what risk a test covers, what it costs to run and maintain, and whether a cheaper test at a lower layer would do the job. Review the suite against that bar regularly and delete tests that fall below it, including AI-generated ones.
Build and scale our Playwright suite. Lead the architecture of our TypeScript Playwright framework: page objects, fixtures, test data, environment handling, parallel runs and reporting.
Use AI to build and expand automation. Use AI coding agents (Cursor, Claude Code or similar) to write new tests, convert manual test cases and legacy tests, triage failures and fix flaky tests. Build the prompts, rules, skills and agent workflows that let the whole team work this way. Set the review standard for AI-generated tests so they check real behavior, not just pass.
Explore agentic testing. Evaluate and pilot newer approaches, such as agents that explore the application, generate test plans from requirements or repair broken locators. Bring in what works and drop what doesn’t.
Mentor the QA team. Coach our test engineers on automation design, Playwright and AI-assisted workflows through pairing, code review and hands-on teaching. You are measured on how much the team improves, not only on the tests you write yourself.
Build testing into the pipeline. Work with Platform engineers to run the right tests at the right stage of CI/CD, on short-lived test environments, with fast and reliable feedback to developers. Help us gate deployments on test results we trust.
Partner with developers. Help product engineers write testable code and own their own tests, including the test attributes and contracts that keep UI tests stable as the product changes.
Collaboration. Communicate clearly with a distributed team, raise quality risks early and work well with both technical and non-technical partners.