Embedded firmware
Bare-metal and RTOS firmware in C and C++ on STM32, ESP32, and MSP430. Drivers, interrupt-driven I/O, low-power modes, and bootloaders.
[Available for hire]
Electrical & Computer Engineer
B.S. ECE, NC State University, 2026
Raleigh, NC · Open to relocation
Brady Geiger
I graduated from NC State in 2026 with a B.S. in Electrical and Computer Engineering, and I am looking for my first full-time engineering role. I want to join a team that puts real hardware in the field: embedded systems, hardware design, or test and validation. I am based in Raleigh, North Carolina, willing to relocate, and available to start immediately.
Why I fitBare-metal and RTOS firmware in C and C++ on STM32, ESP32, and MSP430. Drivers, interrupt-driven I/O, low-power modes, and bootloaders.
Schematic capture and layout in KiCad, two to four layers. Stackup, impedance control, power integrity, DFM checks, and hand assembly down to 0402.
Verilog and SystemVerilog on Xilinx 7-series. Pipelined datapaths, AXI peripherals, timing closure in Vivado, and simulation with testbenches.
Sampling, filtering, and FFT analysis in MATLAB and Python. PID loops tuned on real plants, not just in simulation.
Oscilloscopes, logic analyzers, spectrum analyzers, and SCPI automation in Python. Every board ships with a test plan and measured results.
Linear and switching regulators, battery charging, and protection circuits. Thermal budgets checked with a thermocouple, not a guess.
Hands-onNot hands-off
I would rather probe a board than argue over a block diagram. Every project on this page ran on hardware I designed, assembled, and debugged myself.
LearnsAt speed
Senior design put KiCad, LoRa, and FreeRTOS in front of me in the same semester. I shipped with all three. New stacks are a week of reading, not a blocker.
TestedOn the bench
Simulation is where a design starts, not where it ends. I bring measured numbers to every review: efficiency curves, noise floors, timing margins.
CH1 3.3V rail · 20 mV/div · 2 µs/div
Firmware on resource-constrained microcontrollers: drivers, RTOS tasks, power management, and the bring-up work between a bare board and a product. I have done this on three custom boards and would do it again on yours.
Four years in the labs at NC State, surrounded by the Research Triangle's hardware companies. The coursework is done. The next board I bring up should be yours.
0
Custom PCBs designed, assembled, and brought up
0
Projects shipped end to end, from schematic to firmware
0
Years of lab-based coursework and team projects
North Carolina State University
B.S. Electrical and Computer Engineering, 2026
Raleigh, North Carolina
Coursework: Embedded Systems, Digital Design with FPGAs, Analog Electronics, Power Electronics, Signals and Systems, Control Systems, Computer Architecture, Microelectronics, Senior Design I and II
Wireless vibration sensing node, industry-sponsored capstone, team of four
Hardware lead and firmware. Owned schematic, layout, and bring-up for two PCB revisions. Wrote the FreeRTOS firmware, the LoRa link layer, and the power budget that reached 30 days on one cell.
I build things that have to work when the power comes on. If your team ships hardware and needs an engineer who will own a board from schematic to field test, let's talk.
brady@bradygeiger.com
Brady Geiger
Replies in under a day. Quick answers below are instant.
Pick a 20 minute slot. It opens as a Google Calendar invite with a Meet link, Brady added as a guest.