Career chapter · NIST Engineering Laboratory

Five years of field-test engineering.

From June 2020 to September 2025, I worked at the NIST Engineering Laboratory on how the robots and small drones used in emergency response are evaluated: first as a PREP Researcher, then from December 2023 as a Robotics Research Engineer. One question ran through all of it: when a machine is sent to help, what can it actually do, and how would you prove it?

Role
PREP Researcher, then Robotics Research Engineer
Period
June 2020 – September 2025
Systems
Small UAS · ground robots
Domain
Emergency response
01Test methods

Turning operational tasks into repeatable tests.

Emergency responders needed a way to state what a response aircraft could actually do, not in a demonstration but in numbers another team could reproduce. I developed, validated, fabricated, and documented aerial test methods and their field apparatus: buildable procedures, machine-readable image targets, and more than ten CAD models.

The CAD was part of the method rather than decoration. It carried enough geometry that another site could build the same setup and obtain comparable results.

10+ CAD modelsBuildable proceduresMachine-readable targets
Test apparatusIllustrative schematic
A drop-test rig of the general kind used in aerial test methods. Schematic, not a specific NIST drawing.
Apparatus in the field
Apparatus CAD model
02UAS field programs

Taking the tests outdoors.

Field programs introduce wind, distance, terrain, operator workload, and imperfect observation. I administered tests for a public-safety UAS challenge and evaluated 3D-mapping outputs across six teams; the resulting write-up ran to a 109-slide technical report.

I also ran an outdoor drop-test program for small UAS, with releases from altitudes up to 400 feet measured by non-contact video trajectory analysis. That work is documented in internal NIST technical reporting.

6 teams evaluated109-slide reportReleases up to 400 ft
Outdoor UAS test range
Drop-test release footage
03Automated scoring

Scoring runs from partial evidence.

A camera in flight rarely captures the clean, complete view a scoring rule assumes. I designed and implemented an experimental computer-vision scoring workflow in Python that samples robot-camera video, applies partial-target logic, and resolves detections through a versioned score schema. Scoring ran automated, with human review retained where judgment mattered.

The workflow scored more than eight evaluation events, and every score remained traceable to the exact frames behind it. A disputed score could be settled by inspection rather than argument.

8+ events scoredFrame-level traceabilitySolo implementation
Scoring pipelineIllustrative schematic
Video to frames to detection to a traceable score: the shape of the workflow.
Scoring output view
04RoboCupRescue · ICRA · IROS

Testing in public at international events.

International events are where a test method meets other teams' robots. I ran more than one hundred quadruped mobility trials and contributed slip-disc terrain concepts used at RoboCupRescue, ICRA, and IROS.

For the 2024 championship, the arena geometry, including a metric 3D floorplan, was modeled in CAD so another venue could reconstruct it exactly. A test method has to be portable for its scores to mean anything across venues.

100+ quadruped trials3 event series2024 arena CAD
Event arenaIllustrative schematic
Mobility terrain and slip discs of the kind used at events. Schematic, not a specific arena.
05ASTM E54.09

Moving test methods into the standards process.

A test method starts to matter when it works without its author in the room. I contributed to ASTM E54.09, the standards subcommittee for response robots, through technical review and subcommittee work, including reballot support.

It is slow, careful work, and it is how a lab-proven method becomes something any agency can adopt and run.

Technical reviewSubcommittee participationReballot support
Standards committee work
06Wildfire adaptation

Rebuilding the tests for wildfire response.

Wildfire response broke the assumptions the aerial tests were built on. Visual targets became thermal. Controlled sites became uncontrolled. One capability became three separately testable tasks: identification, inspection, and suppression.

I led the NIST and XPRIZE wildfire drone-response collaboration and co-led the student team that built the new apparatus: the Treefire Post, the Thermal Campfire Omni, and 3D-printed concentric-C thermal acuity targets. The work produced a peer-reviewed conference paper.

3 task classesPurpose-built thermal apparatusIEEE CCWC 2025 paper
Read the full case studySee the publication
Thermal targetIllustrative schematic
Concentric-C acuity target geometry. Schematic of the concept, not a drawing of the built apparatus.
Thermal test apparatus
Wildfire field exercise
07Collaboration

Mentoring and collaborative apparatus work.

The wildfire apparatus team was largely students, and co-leading it was among the most rewarding work of those years.

A test method matters only if other people can pick it up, question it, and improve it. Teaching someone to run a test is also the fastest way to find out whether the procedure is actually written down.

Student apparatus teamMentoring and collaboration
Apparatus team in the field

That is the chapter in outline. The engineering stories carry the detail.