Embedded Engineer- US Site

Kela Technologies
•Onsite

About The Position

We are seeking an Embedded Engineer to own firmware end-to-end on safety-critical embedded systems. Our products utilize ARM Cortex-M class hardware and operate in demanding field environments. While the current codebase is Rust-on-Embassy, we are open to strong C, C++, or Rust embedded engineers. You will collaborate closely with the hardware engineer throughout the product lifecycle, from bring-up through qualification.

Requirements

  • 7+ years of professional embedded firmware experience on ARM Cortex-M (or comparable) in C, C++, or Rust, with shipped or fielded products.
  • Deep comfort with the bare-metal stack: interrupts, DMA, clocks, timers, low-power modes, linker scripts, and memory maps.
  • Strong experience with peripheral protocols (I²C, SPI, UART, USB CDC) and debugging them using a scope or logic analyzer.
  • Experience building and reasoning about real-world safety-relevant state machines, including guard conditions and timer-driven transitions.
  • Discipline around testability: separation of pure-logic code from HAL, and host tests for components not strictly requiring the target.
  • Working English, written and verbal.

Nice To Haves

  • Rust embedded experience (Embassy, embedded-hal, defmt, probe-rs, RTIC, no_std ecosystem).
  • Modern C++ embedded experience (C++17/20, freestanding builds).
  • Safety-critical firmware background (defense, automotive, aerospace, or medical).
  • Async firmware experience (Embassy, Zephyr, FreeRTOS with event loops, or bare-metal cooperative schedulers).
  • Bootloader, DFU, and secure-boot work; factory provisioning and programming flows.
  • Experience shipping a C SDK or FFI bindings to external integrators.

Responsibilities

  • Own firmware end-to-end, including drivers, state machines, communication protocols, command surface, bring-up, qualification, and programming flows.
  • Build and maintain a host-testable simulation layer to ensure state machines are testable on a laptop without flashing a board.
  • Collaborate with the hardware engineer on bring-up, register-map ergonomics, and timing decisions.
  • Carry firmware through environmental qualification (thermal, EMC, vibration).
  • Define and enforce the firmware-side safety case, including testing, proof, and shipping criteria.
  • Write terse, testable code that is clear about its safety story.
Ā© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service