I am a computer engineering student at the Georgia Institute of Technology who enjoys understanding systems all the way from their physical inputs to the software that controls them.
That interest has taken me through embedded software, firmware, device drivers, hardware test automation, and computer vision. In each setting, I have been drawn to the same kind of question: how do you make a complex technical system observable, testable, and trustworthy? I like work that requires both low-level attention and a wider systems view—reading a datasheet, tracing a timing issue, designing an interface, and then stepping back to ask whether the whole product behaves the way a person expects.
My experiences have also shown me that good engineering is collaborative. A reliable solution is not only correct code or a clean circuit; it is also clear documentation, thoughtful abstraction, reproducible testing, and communication that helps a team make decisions. I have learned to value the moments when an experiment disproves an assumption, because those moments turn uncertainty into useful evidence.
Outside of engineering, chess and charcoal drawing shape the way I think. Chess trains me to examine consequences before acting, while drawing makes me slow down and notice proportion, texture, and detail. Both practices reward iteration. They remind me that strong technical work is rarely produced in one pass; it develops through observation, revision, and a willingness to look again.
