System Integrations Engineer
CurrentTroubleshoot functional regressions caught by system test of an autonomous vehicle.- document failure patterns with logs, telemetry, & memory dumps- isolate system failure to HW subsystem and SW module- investigate suspected regression culprits through code review and additional tracing- facilitate fix: inform regression authors; propose HW, SW, or process fix; define fix acceptance criteriaExamples.In response to unverified change release, defined calibration revision workflow.- highlighted a change management gap when an unverified calibration change caused system test regression- for future cal. changes, defined acceptance criteria, documentation requirements, & test workflow- coordinated & tracked process adherence with calibration revision owner & system test staffIn response to an out-of-memory (OOM) event, reduced excessive test scope.- isolated failure to an embedded environment by excluding VM- through code review of recent merge lists, identified OOM culprit within interface library- added tracing within library code generation for correlation with failure- reduced RAM usage sampling period from 5s to 100ms- root caused OOM to an unconstrained but, intended RAM use increase within backward compatibility logic; design intentionally increased mem. use with each interface revision - coordinated test scope change to reduce backward compatibility from the past 5 year to the last 2 yearsIn response to long SW deployment, defined & prototyped SW changes to reduce deployment time.- isolated perf. bottleneck to individual file transfer overhead for a file set with 1000s of KB sized files- to limit overhead impact, prototyped & benchmarked pre-transfer file archival into a mountable image- solicited SW deployment team to adopt prototype for 33% reduction in bundle transfer time
