Technical interview guide

Firmware & Bootloaders

What runs before application code, how a device updates itself in the field, and the linker script details that decide where everything ends up in memory.

Read: 60 min
Practice MCQs: 25
Interview QA: 25
Edition: v3
Editorial status: Reviewed
Relevant for: Embedded Systems Engineer

Scope: Current MCUboot design/imgtool/recovery guidance; RFC 9019 and RFC 9124; NIST SP 800-193; CMSIS-Core 6 reviewed 2026-09-04.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: 2026-10-05 · Written: 2026-10-05 · Reviewed: 2026-10-04

QA-1

Design and validate a boot/update mechanism for root of trust.

QA-2

Design and validate a boot/update mechanism for image authentication.

QA-3

Design and validate a boot/update mechanism for anti-rollback.

QA-4

Walk me through the embedded boot sequence from power-on reset (POR) through ROM, primary bootloader, secondary bootloader, to kernel/application handoff.

QA-5

How do linker scripts and memory maps define vector tables, RAM, flash sections, and stack/heap allocation during early bootloader initialization?

QA-6

Design and validate a boot/update mechanism for key rotation.

QA-7

How do you recover a device from an interrupted or corrupt firmware flash update when neither A/B bank passes integrity checks?

QA-8

Design and validate a boot/update mechanism for A/B slots.

QA-9

Design and validate a boot/update mechanism for swap update.

QA-10

Design and validate a boot/update mechanism for image confirmation.

QA-11

Design and validate a boot/update mechanism for rollback semantics.

QA-12

Design and validate a boot/update mechanism for data migration.

QA-13

Design and validate a boot/update mechanism for boot selection metadata.

QA-14

Design and validate a boot/update mechanism for vector handoff.

QA-15

Design and validate a boot/update mechanism for runtime handoff.

QA-16

Design and validate a boot/update mechanism for watchdog.

QA-17

Design and validate a boot/update mechanism for recovery mode.

QA-18

Design and validate a boot/update mechanism for transport trust.

QA-19

Design and validate a boot/update mechanism for image encryption.

QA-20

Design and validate a boot/update mechanism for dependency ordering.

QA-21

Design and validate a boot/update mechanism for flash constraints.

QA-22

Design and validate a boot/update mechanism for failure injection.

QA-23

Design and validate a boot/update mechanism for manufacturing provisioning.

QA-24

Design and validate a boot/update mechanism for update observability.

QA-25