QA Engineer - Quality Operations & Coverage

Apply

Description

About Us:

Run Buggy is the most technically advanced automotive logistics platform on the market. Period.

Backed by Porsche Ventures and Hearst Ventures, Run Buggy is transforming the way cars move. Our cutting-edge technology is trusted by some of the largest OEMs, captive finance companies, and automotive lenders in the world to streamline vehicle transportation at scale.

Run Buggy's end-to-end platform connects car shippers and haulers in real time - eliminating the friction of traditional load boards and costly custom software. For shippers, Run Buggy integrates directly into existing management systems, reducing transportation costs and accelerating delivery timelines. For transporters, we offer a smarter, more profitable way to find, accept, and manage loads - all from a single app.

Since launching in 2019, Run Buggy has grown to over 190 team members, facilitated the movement of hundreds of thousands of vehicles, and attracted tens of thousands of transporters across the U.S.

We're not just building a better logistics platform - we're redefining the future of automotive transportation.

About the Role:

We are looking for a QA Engineer who brings structure, consistency, and ownership to the quality process. This person will be a cornerstone of how the QA team tracks work, maintains test coverage, plans and designs tests, and keeps quality visible across multiple development streams.

Our ideal candidate is someone who finds satisfaction in having a clear picture of what is tested, what is not, and what needs attention. Test planning comes naturally to you. You are organized without being rigid, and you care about making sure the right work gets done - not just the easy work. You communicate well, keep your own records, and don't need someone to follow up with you twice.

This is a hybrid role based in Tempe, AZ.

Requirements

What You Will Be Doing:

* Own test planning, case creation, maintenance, and traceability for assigned features and services.

* Track QA status across active development work - features in progress, regressions, release readiness.

* Execute manual and automated test runs and document results with enough context to be useful.

* Write, review, and improve test plans and test cases based on requirements, API contracts, and observed system behavior.

* Participate in sprint ceremonies and work directly with developers and product managers to understand what is being built.

* Identify gaps in coverage and raise them proactively.

* Contribute to lightweight automation scripts and tooling that reduce repetitive manual work.

* Use AI-assisted tools to accelerate test case generation, documentation, and analysis - you bring the judgment; the tools bring the speed.

* Other duties as assigned.

What You Bring to the Team by Way of

Skills and Experience:

Technical Foundation

* Comfortable working in a Linux/Unix environment; basic command-line proficiency.

* Experience writing or reading scripts in at least one language (Python, JavaScript, Bash, or similar) - you do not need to be a developer, but you need to be able to open a script, understand what it does, and modify it when needed.

* Familiarity with REST APIs - you should understand what an HTTP request is, what a status code means, and be able to construct a simple API call using Postman, curl, or a test library.

* Experience with a test management system (Test Rail, Zephyr, Jira, or similar).

* Comfortable reading JSON or XML responses and knowing whether what you see makes sense.

QA and Process Skills

* 2 to 4 years of software testing experience, with a mix of manual and some automation exposure.

* Experience writing clear, reusable test cases from functional requirements or user stories.

* Ability to track multiple work streams simultaneously and communicate status clearly.

* Some exposure to CI/CD pipelines - you do not need to build them, but you should understand where tests fit in the build process.

Soft Skills That Matter Here

* You manage your own work. You don't wait to be told what to test next - you look at what's changing and figure it out.

* You document as you go. Your test cases and notes are useful to someone who wasn't in the meeting.

* You ask questions early rather than make assumptions late.

* You are comfortable with ambiguity and know how to make progress when the requirements aren't perfect.

Bonus

* Experience with Robot Framework, Selenium, or a similar test automation framework.

* Familiarity with logistics, fleet management, or marketplace-style platforms.

* Experience working in agile/scrum environments.

* Any exposure to micro-services architecture - understanding that testing one feature may involve tracing requests across several independent services.

* Basic familiarity with Kubernetes concepts (pods, name spaces, deployments) - comfort reading pod logs or understanding what environment a service is running in.

* Some awareness of Elasticsearch - querying an index, reviewing indexed data for test validation, or understanding log…