The specific signals an experienced embedded engineer hiring panel grades on during the eight-second scan.

• MCU family + RTOS named

  'STM32H7 + FreeRTOS' beats 'embedded systems experience.' Specific MCU + RTOS is the first scan.

• Protocols listed (SPI, I2C, UART, CAN, USB, BLE)

  Embedded JDs match against protocol tokens. Name yours precisely.

• Memory / real-time constraints

  RAM in KB, flash in KB or MB, ISR latency in μs. Embedded units of measure.

• Industry vertical + compliance

  Automotive (ISO 26262), medical (IEC 62304, FDA 510(k)), consumer IoT (FCC, CE). Industry signals the compliance demands.

• C / C++ / Rust depth

  C is universal; C++ is consumer + automotive; Rust is emerging in safety-critical. Name your primary.

• Hardware-bring-up signal

  Schematic review, board bring-up, oscilloscope + JTAG debug. The senior embedded signal.

1. 1

   Open with MCU + RTOS + industry

   Consumer IoT: 'Senior embedded engineer; STM32H7 + FreeRTOS primary; shipped firmware on 4 consumer products (1.4M units in field).' Automotive: 'Embedded engineer in automotive (Tier 1 supplier); ISO 26262 ASIL-B trained; STM32L4 + AUTOSAR; shipped sensor-fusion ECU on 2 vehicle platforms.' Medical: 'Embedded firmware engineer in medical devices; IEC 62304 Class B + IEC 60601 work; nRF52840 + Zephyr; FDA 510(k) cleared product.'

   MCU + RTOS + industry is the first scan.

2. 2

   Quantify in embedded units

   RAM (KB), flash (KB or MB), ISR latency (μs), task switching latency, power budget (mA at idle / active), boot time (ms). The specific numbers to favor: • Firmware footprint before/after (KB). • ISR worst-case latency (μs). • Boot time (cold + warm). • Power consumption (sleep mode μA, active mA). • Wireless throughput (KB/sec, BLE PHY rates). • MTBF (mean time between failures) if shipped product.

3. 3

   List protocols with specific stack / MCU context

   SPI on STM32H7 with DMA, I2C with multi-master arbitration on STM32L4, CAN with J1939 + ISO-TP for automotive, BLE custom GATT + GAP on nRF52840. Generic protocol lists ('SPI, I2C, UART') parse but read as junior — the stack + MCU + use-case context signals depth.

4. 4

   Surface industry compliance

   Automotive: ISO 26262 ASIL level + AUTOSAR + MISRA C. Medical: IEC 62304 Class + FDA 510(k) clearance + IEC 60601. Aerospace: DO-178C DAL level + DO-254 hardware certification. Consumer: FCC + CE + RED + UL + battery certs. Each industry has distinct demands — surface yours.

5. 5

   Close with portfolio + community signal

   Shipped products (with unit counts where possible), published HAL or driver layers, embedded-RTOS contributions (FreeRTOS, Zephyr), conference talks (Embedded World, Embedded.com Linux Foundation events). Entry-level: working side projects with custom PCB + firmware are the strongest credentials.

Each follows the [verb] [object] [number] structure hiring managers grade against. Copy them as a starting point, swap in your own numbers, and read the annotation to understand why each one works.

• Memory

  Cut firmware footprint from 380KB to 220KB on a 256KB-flash STM32L4 MCU through LTO + dead-code elimination + replacing printf-based logging with a 2KB ring-buffer protocol logger.

  Why it works: KB before/after on a specific-flash MCU, three specific interventions.

• Real-time

  Cut worst-case ISR latency on the motor-control loop from 14μs to 4.2μs (target 5μs for the FOC control loop at 20kHz) by moving the SPI sensor read to DMA + scheduling FOC math from a higher-priority FreeRTOS task.

  Why it works: ISR latency before/after, target context (FOC 20kHz), two interventions.

• Protocols

  Protocols shipped: SPI (driver + DMA bring-up on STM32H7), I2C (multi-master arbitration on STM32L4), UART (bootloader + log path), CAN (J1939 + ISO-TP for diagnostics), USB (HID + CDC composite), BLE (custom GATT + GAP on nRF52840), Wi-Fi (ESP32-S3 802.11ax).

  Why it works: Each protocol with specific stack + MCU + use-case context. Verifiable depth.

• Hardware bring-up

  Brought up a 4-layer custom PCB from schematic review → first power-on → MCU bring-up → peripheral bring-up; identified + escalated a sensor power-supply ripple issue at first power-on (PCB rev to fix in 2 weeks).

  Why it works: Bring-up workflow, specific catch + escalation. Hardware fluency is senior signal.

• BLE / medical

  Owned the BLE-stack integration on a wearable medical-grade hub (nRF52840 + Zephyr); custom GATT services for vital-sign data with HCI-spy debugging; passed Bluetooth SIG qualification + IEC 62304 Class B documentation gate.

  Why it works: Stack + MCU + RTOS, specific GATT detail, Bluetooth qualification, IEC 62304 compliance.

• Automotive

  Shipped sensor-fusion ECU firmware on 2 vehicle platforms (combined 880k vehicles); ISO 26262 ASIL-B per the V-model lifecycle (HARA, FMEDA, unit-coverage gates per SUP-10 plan).

  Why it works: Shipped product scope, ASIL level, V-model artifact list.

• Power

  Reduced power consumption from 14mA to 1.4mA in active-listening mode on a battery-powered IoT sensor (nRF52840 + Zephyr) by tightening BLE peripheral connection intervals + moving sensor sampling to a low-power timer + DMA path.

  Why it works: Power-consumption before/after, three interventions, BLE connection-interval detail.

• Bootloader

  Authored the bootloader + secure-firmware-update path on STM32H7 (custom HAL + MCUboot integration); signed-update verification + dual-bank A/B partition + rollback; zero field-update bricks across 280k units deployed.

  Why it works: Bootloader scope, named components (MCUboot, dual-bank A/B), zero-brick deployment scope.

• Migration

  Migrated the consumer-product firmware from a 384KB STM32F4 to a 1MB STM32H7 over 14 weeks; ported 38 device-driver modules; gained 7× CPU headroom for new ML-inference feature.

  Why it works: Source/destination MCU, duration, driver-module count, CPU headroom outcome.

• Open Source

  Two merged PRs to zephyrproject/zephyr — one closed a race condition in the nRF52 power-management subsystem under high-frequency wake-from-sleep; one extended the BLE HCI tracing for SPI-based controllers.

  Why it works: Named project (Zephyr), PR count, two technical descriptions.

• Mentorship

  Mentored 2 junior firmware engineers through MCU bring-up + RTOS task-design; both shipped sole-owner driver modules + completed their first SPI-DMA debug-from-scratch within 6 months.

  Why it works: Mentee count, specific deliverables + debug skill outcome.

• Entry-level capstone

  Built a BLE temperature-and-humidity sensor (nRF52832 + custom 2-layer PCB + Zephyr + custom GATT) as a university capstone; 14 sensors deployed across the engineering building for HVAC monitoring; 12-month battery life on a CR2032.

  Why it works: For entry candidates, a working PCB + firmware + deployment + battery-life metric is high-leverage.

Same intent, two phrasings. Read why the right column lands on the keep-pile and the wrong column doesn't.

Patterns our writers see most often when reviewing embedded engineer resumes — each one disqualifies candidates faster than weak experience does.

• Mistake

  Generic 'embedded developer' without MCU + RTOS.

  Fix

  Lead with MCU family + RTOS combo. 'STM32H7 + FreeRTOS' is specific.

• Mistake

  Memory + real-time claims without numbers.

  Fix

  KB / MB for memory, μs for ISR latency, ms for boot. Embedded units are specific.

• Mistake

  Protocol list without context.

  Fix

  Name each protocol with stack + MCU + use-case ('SPI on STM32H7 with DMA').

• Mistake

  Not naming industry compliance.

  Fix

  Automotive (ISO 26262), medical (IEC 62304), aerospace (DO-178C) — each is specific. Surface yours.

• Mistake

  Listing both C and C++ as equal depth across all use cases.

  Fix

  Name your primary. C dominates safety-critical + small MCUs; C++ is more common in consumer + automotive + large MCUs.

• Mistake

  No hardware bring-up evidence.

  Fix

  Senior embedded engineers operate across hardware/firmware boundary. Surface bring-up or schematic-review work.

• Mistake

  Two-page resume below tech-lead level.

  Fix

  One page until tech-lead / firmware-architect level.

• Mistake

  Listing every protocol you've touched briefly.

  Fix

  List protocols you've shipped at production scale. Touched-once protocols read as junior.

Strong verbs lead strong bullets. Replace generic openers (worked on, helped with, was responsible for) with the specific verb that matches what you actually did.

ATS pipelines weight your Skills section as a structured list. Include 15-25 of the items below if they match your experience — not soft skills.