Specialist disciplines

Linux & RTOS

Real-time and embedded Linux engineers, from kernel and BSP work to RTOS-based systems.

The market

There are two distinct populations here and they get conflated constantly. Embedded Linux engineers — Yocto, Buildroot, kernel, BSP, device tree — and RTOS engineers working in VxWorks, FreeRTOS, RT Linux or similar. Both are described as "real-time" in job adverts. They are not interchangeable, and a brief that treats them as one market will produce a shortlist that satisfies nobody.

Embedded Linux work has grown as devices have got more capable: build systems, driver integration, boot time, and the long tail of making a distribution behave on custom silicon. RTOS work has stayed closer to hard deadlines and deterministic behaviour, which is where the safety and mission-critical requirements usually sit.

We ask which one a brief actually needs before we start, and if the honest answer is both, we say what that does to the timeline. That conversation is uncomfortable at the point of taking the brief and saves a great deal of time afterwards.

What we place

  • Embedded Linux Engineer
  • Linux Kernel Engineer
  • BSP Engineer
  • RTOS Engineer
  • Real-Time Software Engineer
  • Yocto / Buildroot Engineer
  • Device Driver Engineer
  • Platform Software Engineer

Why it's a narrow market

Linux and RTOS are separate populations.

Asking for deep experience in both is a legitimate requirement, but it's a much smaller market than either alone and the brief should reflect that.

Build-system depth is scarce.

Plenty of engineers have used Yocto. Far fewer can debug a broken layer or maintain a BSP without help.

Determinism is a specialism.

Engineers who genuinely understand hard real-time constraints — not just "fast" — are a fraction of the people whose CVs say real-time.

Live roles in this discipline

Current linux & rtos opportunities.

Start a conversation

Talk through the requirement.

Specific engineering evidence, an honest view of the market and a focused search.