I write about problems I run into at work, things I learn while studying, and decisions I make along the way. If you're navigating a similar path in software engineering, I hope some of it is useful.
Background
I came to the US from South Korea in 2016 after military service, starting college a bit later than most. Studied Computer Science at UC Irvine, then spent about 4.5 years in the automotive industry — from internal tools to customer-facing products — working on vehicle diagnostics.
In 2025, I moved to the Bay Area and joined a biotech company focused on laboratory automation. Day to day, I work on software that coordinates lab robots and integrates with scientific instruments. Different domain, same underlying challenge: making complex systems behave predictably.
I'm also pursuing a master's degree through Georgia Tech's OMSCS program, focusing on AI and machine learning — to broaden the range of problems I can tackle as a software engineer.
Perspective
Most of my experience comes from building internal tools and production systems where reliability matters more than novelty. I've learned that good communication is often as important as good code — especially when working with cross-functional teams or systems that other people depend on.
Outside of Work
When I'm not coding, I'm usually listening to music or watching YouTube. Nothing fancy — just the usual ways to unwind.
Get in Touch
If you have questions, want to talk about software engineering, or just want to say hi, feel free to reach out via email or connect with me on LinkedIn.