Job Description & Details
This is a heavy-hitting embedded gig working on a cutting-edge AI wearable and brain-computer interface product. If you enjoy sitting right at the hardware-firmware boundary—bringing up raw silicon, wrangling low-level drivers, and dealing with real-time sensor streams—this role will keep you deeply engaged.
What You'll Actually Be Doing
You'll spend your days buried in board bring-up, debugging signal integrity issues with an oscilloscope, and writing rock-solid C/C++ code for an RTOS like FreeRTOS or Zephyr. Your main battleground will be integrating multiple sensors, managing tight power budgets with complex sleep-wake states, and ensuring that multi-sensor data acquisition runs without dropping packets. You are expected to take complete ownership of your firmware subsystem, pushing it all the way from initial bring-up to final integration and validation on real hardware.
The Core Tech Stack
You need absolute fluency in Embedded C/C++ and hands-on scar tissue from working with MCU/SoC platforms like STM32, Nordic, or ESP32. Mastery over low-level protocols (SPI, I2C, UART, USB) and DMA-driven data transfers is non-negotiable because of the heavy data throughput required by biosensors. Experience with RTOS internals, JTAG/SWD debugging, and logic analyzers will separate you from the pack. If you've previously shipped a consumer product and have touched BLE or OTA updates, you're speaking their exact language.
Interview Expectations
Expect the hiring manager to grill you on race conditions and memory corruption issues in a constrained RTOS environment; they want to know how you isolate hardfaults without relying solely on a debugger. They will likely present a scenario where a sensor is dropping data over SPI due to an interrupt priority mismatch, and they'll want you to walk through your debugging methodology using logic analyzers and scope traces. They aren't looking for textbook definitions; they want to see the scars of someone who has actually stared at a logic analyzer at 2 AM trying to figure out why an I2C bus locked up.
Application Advice
Skip the generic project summaries and make sure your resume immediately highlights specific microcontrollers you've worked with, RTOS environments you've built on, and protocols you've implemented from scratch. Explicitly mention the phrase 'board bring-up', 'low-level drivers', and 'DMA' to get past the initial ATS screening, and make sure you call out any shipped consumer electronics or wearable devices sitting on your resume. If you've touched biosensors, EEG, or PPG, put those right at the top.