QA Engineer - Technical Investigation & Automation

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.

Run Buggy is looking for a QA Engineer - Technical Investigation & Automation who digs in. This is not a checklist role; it is a seat for someone who reads error logs before asking questions, who gets curious about why a system fails, and who does not stop investigating until they understand the root cause.

You will build and own the technical side of QA:
Test architecture, planning, design, automation frameworks, API test suites, deep‑dive investigations, and the infrastructure that makes testing reliable  are the person the team turns to when something breaks in a confusing way, and no one else knows where to start.

This is a hybrid role based in Tempe, AZ.

• Test planning, design, build, and maintain automated test suites covering API, integration, and end‑to‑end workflows.
• Investigate complex defects and system failures - trace execution paths, read logs, analyze API behavior, and identify root causes.
• Develop and maintain API‑level tests using Robot Framework + Requests Library against live and staging environments.
• Evaluate and evolve the automation architecture as the platform scales.
• Write scripts and tooling to support test data management, environment setup, and coverage analysis.
• Collaborate with developers and Dev Ops to integrate tests into CI/CD pipelines.
• Use AI‑assisted tools to accelerate test scaffolding, API contract analysis, and gap identification - you bring the depth; the tools bring the leverage.
• Serve as the technical resource in QA triage - the person who can get to an answer quickly when something breaks.
• Other duties as assigned.

• 3–6 years of software testing experience with a strong emphasis on automation and technical investigation.
• Hands‑on experience with at least one scripting or programming language (Python strongly preferred; JavaScript, Java, or Go also relevant).
• Solid understanding of REST APIs - you can read an API contract, construct requests, validate responses, and write tests that cover edge cases.
• Experience with a test automation framework - Robot Framework, Pytest, Mocha, or similar.
• Comfortable in a Linux/Unix environment; proficient at the command line.
• Ability to read and interpret application logs, stack traces, and HTTP traffic.
• Experience with a test management system (Test Rail, Zephyr, Jira, or similar).

• You approach failures methodically - you form hypotheses, test them, and do not give up because the first thing you tried didn’t work.
• Comfortable working across microservices - you understand that a test failure may involve tracing a request through several independent services before you find the actual problem.
• Experience working with CI/CD pipelines - building test stages, interpreting failures, and understanding where in the pipeline something breaks.
• Familiarity with distributed systems concepts: async messaging, eventual consistency, service dependencies.

• You take ownership of hard…