Triage / Root Cause & Development Engineer - Automotive Infotainment & Connectivity

This six-month contract puts you right in the middle of automotive infotainment chaos, where you'll spend your days hunting down brutal, intermittent bugs across Android Automotive and embedded systems. If you like opening up a vehicle log, tracing a Binder IPC failure, and writing a C++ patch to keep a head unit from crashing, this gig gives you the technical depth to actually make an impact.

What You'll Actually Be Doing

Expect to live in the terminal and debug logs when things go wrong in the field, warranty claims, or validation fleets. You'll take raw symptoms—like a black screen on startup, audio routing failures, or CarPlay dropping out—and figure out whether it's an app issue, an Android Framework quirk, a kernel panic, or a CAN bus signaling problem. You will reproduce these failures on benches or actual vehicles, trace execution paths through C, C++, or Java, and write the actual code-level fixes to close out the tickets.

The Core Tech Stack

You need to be completely fluent in C, C++, or Java and comfortable tearing into Android Automotive OS, Embedded Linux, or QNX. This isn't just an API-wrangling role; you're going to need a deep understanding of multi-threading, IPC, memory management, and low-level debugging using tools like ADB, Wireshark, CANoe, and GDB. Knowledge of automotive protocols like CAN/CAN-FD, Automotive Ethernet, and UDS diagnostics will keep you from getting lost when the software talks to the vehicle hardware.

Interview Expectations

They are going to test your systematic approach to debugging by throwing a nightmare scenario at you, like an intermittent ANR or a race condition during system boot, and asking how you would isolate it using only logcat and kernel dumps. They want to see how you build a hypothesis, eliminate variables, and trace execution from the app layer all the way down to the HAL or kernel. They'll also probe your knowledge of Android's Binder IPC mechanism and native crash handling, so be ready to talk through past experiences where you fixed hard-to-reproduce memory corruption or thread synchronization bugs.

Application Advice

Skip the generic project management fluff on your resume and focus squarely on your low-level debugging and code-tracing wins. Highlight specific instances where you diagnosed complex system crashes in Android, embedded Linux, or QNX environments, making sure to drop keywords like logcat, tombstones, CAN/CAN-FD, and IPC right into your experience bullets so you clear the automated screening without a hitch.