Embedded systems/RTOS trouble shooter

• 8-15 years’ experience expected

• Must have full LinkedIn

• 3-stage interview: technical screen (Kyndryl) * behavioural/technical (Wind River) * final round of three back-to-back 30-min interviews with different Wind River engineers

Must have:

Look at what reproduce customer environments and identify root causes actually mean in this stack:

• VxWorks is an RTOS written in C. Its kernel, drivers, BSPs (board support packages) - all C, with some C++ in newer components. If a customer reports a kernel panic, a driver hang, or a timing bug, you’re reading disassembly, stack traces, and C source to figure out what broke.

• Wind River Linux - same story at the kernel/driver level (C), though more of the user space tooling (system, udev, Yocto build layers) is scriptable.

• BSPs and drivers - this is entirely C/C++. You cannot debug a device driver interacting incorrectly with hardware without reading (and often instrumenting or patching) that C/C++ code directly.

• Toolchains like Diab, GCC, Clang, Workbench - these compile C/C++. Understanding compiler behaviour, optimization bugs, linker issues, or toolchain diagnostics requires fluency in what the C/C++ source is supposed to produce at the binary level.