The invisible computers
An embedded system is a computer built into another product — a car, a fridge, an insulin pump, a satellite. You interact with dozens every day and rarely notice, because they are designed to disappear into the product they serve.
The defining trait: constrained resources and hard real-time requirements. A cloud server can afford to be slow. An anti-lock brake controller cannot.
The stack, from silicon up
Microcontroller
The heart of the system — a small CPU with integrated memory and peripherals. Popular families include ARM Cortex-M, ESP32, RISC-V and 8-bit AVR / PIC.
Firmware
Software that runs directly on the microcontroller, often in C or C++. Real-time operating systems like FreeRTOS or Zephyr manage tasks; some products run bare-metal.
Peripherals
GPIO, ADC, DAC, UART, SPI, I2C, CAN — the language embedded engineers speak. Understanding these buses is the difference between a prototype and a product.
Communication
BLE, Wi-Fi, LoRa, cellular. Modern embedded work is heavily networked.
What embedded engineers actually do
- Read datasheets carefully — sometimes hundreds of pages.
- Bring up new boards, one peripheral at a time.
- Debug with oscilloscopes, logic analysers and JTAG.
- Optimise memory and power to the last byte and microamp.
Why this discipline stays evergreen
Every new product category — electric vehicles, wearable health devices, industrial IoT, robots — needs firmware. Cloud engineers will always outnumber embedded engineers, but embedded engineers are increasingly rare and correspondingly well-paid.
If you like getting close to the metal, this is the field.