Kingsley.

Welcome. Glad you're here.

I am Kingsley Agyenim-Boateng.

Based in Austin, Texas

Firmware engineer at AMD. I work on the code that runs before the OS knows it exists — memory bring-up, boot flows, and the kind of bugs that only appear when the system is barely alive.

LinkedInGitHubEmailResume

01 — About

A little about me.

Portrait of Kingsley Agyenim-Boateng

I’m Kingsley, a firmware engineer at AMD working on memory subsystem firmware. It is the kind of work that sits right between software and hardware. A lot of my day is spent around early boot, DDR5 and LPDDR5 enablement, memory initialization, silicon bring up, validation, and the weird bugs that only show up when the system is barely alive.

I like the parts of engineering that force you to slow down and actually understand what is happening. Debug logs, register dumps, protocol traces, timing issues, boot failures, and performance regressions are where the work gets interesting to me. It is not always clean, but that is the point. Real engineering is usually messy before it makes sense.

This site is my space to document that journey. Some posts will be technical, covering firmware, memory systems, debugging, C/C++, tooling, side projects, and low level systems. Some will be more personal, covering career lessons, interview prep, advice for young engineers, and things I wish someone explained earlier.

Outside of work, I enjoy soccer, photography, travel, and whatever side project has my attention at the moment. I like having things outside of engineering that still make me think, compete, create, or look at the world a little differently.

I’m not trying to present a perfect version of engineering here. I’m trying to show the real version: the bugs, the learning, the late night curiosity, the small wins, and the process of becoming better one problem at a time.

Download Resume

Expertise

  • Memory Subsystems
  • DDR5 / LPDDR5
  • Firmware Development
  • C / C++ / Python
  • Validation
  • Performance Optimization
  • Linux
  • Lab Debug
  • Automation

02 — Experience

Where I've worked.

  1. 2023 — Present

    Austin, Texas

    Firmware Engineer — Memory Subsystem @ AMD

    • Develop and debug low-level BIOS firmware for AMD client and server SoCs, focused on early-boot memory initialization, platform bring-up, and root-cause resolution of memory-related boot failures.
    • Support DDR5 and LPDDR5 enablement across multiple client and server platforms, collaborating cross-functionally during silicon bring-up and validation to analyze boot behavior and system-level failures.
    • Lead the team's transition to reStructuredText (.rst)-based documentation (FlexDoc), enabling firmware documentation to be versioned, built, and generated alongside firmware code.
    • Contribute to boot time optimization initiatives, identifying and improving performance-critical paths in early boot firmware.
    • Address static analysis and code quality issues, including large-scale cleanup of Coverity and keyword-scan (KWS) findings across the codebase.
    • Participate in code reviews and contribute to unit test development, improving firmware quality and regression stability through automated build and test pipelines.

  2. May 2022 — January 2023

    Austin, Texas

    System Design Engineering Intern @ AMD

    • Developed and executed post-silicon validation test plans for datacenter server SoCs, working closely with firmware teams.
    • Built and maintained post-si validation infrastructure, including software automation, hardware setup, and lab workflows.
    • Performed system-level debug using internal AMD tools (MemEye, MBIST, HDT) and lab equipment (oscilloscopes, logic analyzers), with exposure to x86 platforms and DDR5/LPDDR5 memory.

03 — Education

Where I studied.

  1. Expected Graduation — Dec 2027

    Georgia Institute of Technology

    M.S. in Computer Science (Computing Systems)

  2. August 2020 — May 2023

    Texas State University

    B.S. in Electrical and Computer Engineering

  3. August 2018 — May 2020

    Austin Community College

    A.S. in Engineering

04 — Engineering Insights

Thoughts on firmware engineering, debugging complex systems, and growing as an engineer.

05 — Contact

Get in touch

Whether you're an engineer who wants to chat about firmware, or a student curious about how to break into embedded — I'd love to hear from you.

I read every message. If you don't hear back within a few days, please ping me on LinkedIn.