Netradyne - IDMS
Driver.i was the main project. But most of my time at Netradyne was spent on the product team's ticket backlog, six feature areas that fleet operators and drivers had flagged as broken or missing. None of it was glamorous. All of it was real. Enterprise design at this scale means a small change in the wrong place touches thousands of operators and the drivers they manage.
GDPR compliance design isn't about adding a settings page. It's about understanding what enterprise clients in different regions actually need to operate.
The Privacy and GDPR work was the most structurally complex of the six areas. Enterprise clients like Amazon EU and Cintas had different compliance requirements than US-based fleets. Privacy settings that worked fleet-wide stopped working when you had thousands of drivers across different regulatory contexts. The solution wasn't one feature. It was a set of granular controls that let fleet managers configure privacy at the level their business actually operates — fleet, vehicle, or individual driver.
Context was missing everywhere. Drivers got alerts with no explanation. Operators pulled footage with no memory of why.
The video search and ADAS tickets had the same underlying problem. Information existed in the system but wasn't surfacing where people needed it. A driver receiving an ADAS alert had no way to know if the hardware was functioning correctly when it fired. A fleet manager pulling a saved video had no record of the search that led them there weeks ago. The fixes were small. A colored dot. A tag column. A search term preserved in a table row. But each one put the right context in the right place at the right moment.
