Lead Test Engineer - Scenario Coverage & Evaluation Data Sets

Lead Test Engineer — Scenario Coverage & Evaluation Datasets

Avride builds autonomous driving technology for vehicles and delivery robots. Our QA organization measures how well that technology drives, largely in simulation — and an evaluation is only as good as the data behind it. So we build our own datasets, keep track of what they cover, and keep widening that coverage as the technology takes on more of the road.

You will own test coverage for the autonomous driving stack, end to end. Scenario areas are owned by individual QA engineers. You own the whole: what our evaluation dataset must contain for a release decision to be trustworthy, where the gaps are that nobody working inside a single area can see, and how those gaps keep surfacing without you being the one who finds them.

Coverage is a data problem before it is a testing problem. A scenario that exists on paper is not covered until there are real scenes behind it, and closing that distance is the craft of this role: metric-driven search across driving data, VLM-assisted retrieval and clustering, criticality-based selection, variation in simulation, and structured capture in the field. You will use that toolkit yourself before you ask anyone else to, and turn what works into something the whole QA team can run without you.

You will lead through process first building it, and delivering through the QA engineers and operational resources already around you and grow a team of your own as the scope demands it.

• Own the evaluation dataset. What is in it, what is missing, and what it lets us claim about autonomous driving quality.

• Own the coverage model. Our scenario taxonomy and ODD parameter space have to stay accurate as the technology matures and the operating environment changes. You own that: spotting where the model no longer describes what our vehicles actually meet, and working with the QA engineer who owns each category to keep it current.

• Close the distance between scenarios and scenes. For each thin area, choose the method that will actually produce the scenes you need — mining, simulation or the field — and know what it costs before you spend it.

• Set the mining agenda for the QA team. Decide what each area owner should be looking for next, review what comes back, and keep a regular rhythm for collecting their feedback.

• Be the internal customer for our mining tooling. Use it yourself, turn what you learn into requirements for the development and analytics teams, and keep the feedback loop between QA and engineering running so the tooling keeps pace with what we ask of it.

• Bring in what works elsewhere. Track how other AV programs, research groups and vendors solve coverage, edge-case curation and data selection, and turn what is worth having into concrete proposals.

• Work through the teams you depend on. Coverage is only visible once scenes are labeled and only measurable when the right metrics exist, which makes labeling and analytics standing partners rather than occasional ones. Give them clear priorities and specific, actionable feedback, and stay close enough to see early when something you depend on is at risk.

• Report coverage and readiness. Put them in a form a release decision can be made on — clear about confidence and about blind spots.

• 8+ years in software testing or test engineering, including 2+ years owning the test strategy for a full system rather than a feature area.

• Coverage as a first-class problem. You can talk about equivalence classes, parameter spaces, risk-based