Highlights
This project represents my interest in security-focused systems work alongside embedded and low-level software.
Instead of treating encryption as a one-off feature, I approached it as a library problem: define reusable interfaces, structure the code clearly, and think carefully about how protected data should move through the system. That made it a useful exercise in both software design and security-oriented engineering.
Why it is part of the portfolio
I wanted this project included because it shows that my interests are not limited to firmware on physical hardware. I am also interested in the lower-level software ideas that sit close to correctness, reliability, and trust, and cryptographic code is a good example of that kind of engineering mindset.
What it adds to my profile
This project broadens the portfolio by showing security-oriented library work next to embedded firmware, FPGA, telemetry, and system integration projects. It reflects the same habit of thinking I use elsewhere: understand the fundamentals, keep interfaces clean, and build from first principles where that depth matters.