Sunnyvale, California, United States
I have worked extensively on the embedded software stack running on prototype vehicles. My work has spanned across the Robot Compute Module (RCM), controllers, and vehicle interface components, focusing on ensuring reliable communication and execution between hardware and software layers.
End-to-end integration workflow
I have contributed to multiple stages of the embedded software integration lifecycle: writing and deploying vehicle driver nodes, supporting calibration through software hooks, and validating safety-critical paths during commissioning.
Cross-team technical collaboration
My work has required continuous collaboration with hardware engineers, control system developers, calibration specialists, and operations teams to ensure smooth integration of embedded software with the vehicle platform.
Change management in embedded software
I have worked within established software release pipelines, assessing impacts of changes on CAN signal mappings, configuration files, and driver node implementations to maintain system stability.
Stakeholder-facing software integration
I have engaged with OEM partners to align software integration with vehicle-specific requirements, ensuring that embedded driver nodes, gateways, and communication interfaces match external system expectations.
Requirements to implementation
I have translated OEM requirements—such as safety signal handling or trajectory data sharing—into embedded software specifications and ensured they were implemented and validated on-vehicle.