Back to jobs
Some facts about a vehicle are held only by the vehicle: the software each module is running, the codes it has stored, the state of its battery. No database has them. The car does.
We read them through the diagnostic port, on dealer lots, one car at a time. You would own the device that does it: the board, the firmware, the enclosure, and the path from a bench prototype to a unit somebody on a lot can plug in and walk away from.
Every manufacturer speaks its own dialect over the same connector, and some of them lock the door. Getting a clean read from a car you have never seen before is the daily problem.
Who we are looking for
- You have taken a board from schematic to a manufactured run, and lived with the revision you shipped
- Firmware on microcontrollers in C or Rust. CAN at the frame level, not only through a library
- You have debugged against real vehicles, not a simulator: OBD-II, UDS, ISO-TP
- You care what happens after it ships: provisioning, updates, and the unit that comes back dead
- You are fine in a parking lot in February with a laptop on the hood
- Not for you if you want a lab with a test harness for everything. Much of the testing happens in the car.
