Roles they hire for
- Embedded software engineer for STM32 IP drivers and examples
- STM32Cube tools developer
- Software validation engineer
What they emphasise
- Low-level IP drivers and example applications for new STM32 products
- Embedded and real-time C, C++ and assembly with debugging and profiling
- Specification-to-support ownership of drivers on the STM32 roadmap
- Automated validation of STM32 tools and peripherals (I2C, UART, USB, SPI, CAN)
Brush up on
STM32Cube HAL and LLLow-power modesAssembly basicsProfilingPeripheral validationPython test automation
How the rounds usually run
A typical silicon vendor loop for embedded roles. Companies vary by team and seniority.
Online assessment or screen
- C output prediction, pointers and bit manipulation
- Digital logic and OS basics
- For experienced hires, often a recruiter and hiring-manager screen instead
Example: What does this print: an unsigned char set to 200 plus 100, printed as an integer?
Technical 1: C and embedded fundamentals
- Pointers, volatile, const, alignment and endianness
- Interrupts, stacks and memory layout
- Live C coding on bit fields, ring buffers or string handling
Example: Implement a lock-free single-producer, single-consumer ring buffer.
Technical 2: Drivers and architecture
- Designing a peripheral driver and its API
- DMA, caches and interrupt priorities
- RTOS internals and debugging stories
Example: Design a SPI driver that supports blocking, interrupt and DMA modes behind one API.
Technical 3 or hiring manager: system design and projects
- Deep dive into a past project and your design choices
- System-level trade-offs: power, memory, performance
- Sometimes a short presentation on a project
Example: Walk through the hardest bug you've fixed, and what you changed in the process afterwards.
HR and behavioural
- Motivation, teamwork and conflict
- Relocation, notice period and compensation
Example: Tell me about a time you disagreed with a design decision.
Practice questions
Original questions written for STMicroelectronics's focus areas, not leaked ones.
- Design the HAL and LL split for a new timer peripheral. What belongs in each layer?
- Write an example application that shows a low-power feature, and explain how you'd prove the current figure to a customer.
- Explain how you would profile an interrupt handler's worst-case latency on a Cortex-M.
- A peripheral works in debug but not after reset without the debugger. List the causes you'd check.
- How do you validate that a driver behaves correctly across every clock configuration a device supports?
Your prep playlist
Design rounds to practise
Sources
Take an AI mock round styled on STMicroelectronics, with follow-ups that probe what you missed.
Start a mock round