B
Bruno Esquivel Embedded & Security Firmware
Currently looking for roles Firmware · IoT Security · Embedded C

I build secure & reliable firmware for connected devices.

I’m Bruno Esquivel, a firmware engineer focused on secure bootloaders, OTA updates, TLS, and resilient networking on resource-constrained hardware. I like turning system design and security ideas into working, testable firmware.

Based in Bay Area · Open to remote/hybrid Secure boot · OTA · RTOS (Zephyr/FreeRTOS) · C Networking: TLS · SSH · IPSec/IKE

Selected Projects

A few focused projects that combine secure boot, OTA, networking, and embedded constraints.

Secure OTA Update Pipeline (Zephyr + MCUboot + STM32)

End-to-end demo that fetches signed firmware from a hardened web server, stages it into a secondary slot, and hands off verification to MCUboot with rollback on failure.

Zephyr RTOS MCUboot STM32 TLS Dual-slot firmware

nRF + W5500 Ethernet Bring-Up with Secure Updates

Brought up an nRF-based board with a W5500 Ethernet shield, implemented robust reconnect logic, and used it as a testbed for secure firmware download flows.

nRF W5500 DeviceTree Network resilience

IPSec/IKE Strongswan Lab for Firmware Engineers

Designed a small Strongswan lab to experiment with key exchange, certificate-based auth, and failure scenarios relevant to devices establishing secure tunnels to a backend.

IPSec/IKEv2 Strongswan Linux Secure channels

Bootloader Rate Limiter (Token Bucket on MCU)

Implemented a token-bucket rate limiter in a custom bootloader to throttle update attempts and reduce brute-force behaviour, adapting patterns from large-scale systems to small MCUs.

C Bare metal Rate limiting Defensive design

Articles & Notes

Short, focused notes on topics I’ve implemented or debugged in real firmware.

MCUboot, in practice: how image verification really works A pragmatic walkthrough of how MCUboot chooses slots, validates signatures, and recovers from failures — from the perspective of a device actually in the field.
Mapping system-design rate limiters to microcontrollers Taking token-bucket and leaky-bucket patterns from system design interviews and implementing them inside a resource-constrained bootloader.
Zephyr networking gotchas: timeouts, reconnection, and W5500 quirks Notes from bringing up Ethernet on Zephyr, focusing on what actually breaks under bad networks and how to make it boring again.

Resume & Skills

Quick view of what I work with most often. For the full story, grab the PDF.

  • Core: C, embedded systems, ARM Cortex-M, RTOS (Zephyr, FreeRTOS), secure boot, OTA update pipelines.
  • Security & protocols: TLS, X.509, IPSec/IKE, SSH, key management, rate limiting, basic threat modeling.
  • Networking & Linux: TCP/IP, DNS, HTTP(S), Linux networking tools, Strongswan, Nginx, basic hardening.
  • Tooling: Git, CMake, GDB, logic analyzers, oscilloscopes, Wireshark.
  • Bonus: System design concepts translated to firmware rate limiting consistent hashing key-value stores
Download resume (PDF) View on LinkedIn

The best way to reach me for roles, chats, or collaboration.