While reading the thread, a red flag[1] was immediately raised in my mind when:
> We couldn't reproduce it, but we did come up with a theory for why it was happening.
...going right into mechanical subsystem redesign. Surely a cursory review would have challenged such a reactionary proposal: What meaningful steps were taken to falsify the prevailing theory?
There's something implied about discipline when this vacant QA Tester Hardware/Software engineering position description[2] bundles verification/validation test roles on the design/development/production/field support fronts with the following caveat:
> Initially, you'll be the only QA engineer and will perform active testing of new product releases in our lab and in the field at construction sites.
Also, non-rhetorical question: Selenium for industrial hardware test automation...is that really a thing in the wild?
[1] https://twitter.com/tessalau/status/1604018887603138561
[2] https://boards.greenhouse.io/dustyrobotics/jobs/5373908003