~10ms
End-to-end concurrent write latency
C++17 / Go / Linux / CI/CD
Engineering reliable systems with measurable impact.
I build low-latency software, release infrastructure, and backend platforms that stay understandable under load—and maintainable after launch.
Production impact
Verified from resume // 2026
68
Debian packages under management
50–60
Client environments released monthly
40%
Reduction in redundant C++ code
Selected systems
Case file // Read-only
C++17 / IPC / Multithreading01
Low-latency data storage
Designed a concurrent C++17 storage system with carefully optimized inter-process communication and multithreaded write paths for predictable performance under load.
~10ms end-to-end write latency
Debian / CMake / CPack02
Release platform
Built and owned the packaging and release workflow used to ship production software consistently across distributed client environments.
68 packages // monthly releases
Go / React / Database design03
Time tracking platform
Developed a full-stack internal application that automated weekly reporting and replaced repetitive spreadsheet entry with a focused workflow.
Hours of manual work removed
epoll / Networking / Linux04
Nonblocking data flow
Engineered epoll-based network services and multithreaded architectures to remove blocking behavior and improve high-frequency data-flow scalability.
Higher throughput // fewer bottlenecks
How I work
Engineering principles
Performance work starts with evidence: latency, memory behavior, throughput, and failure modes.
Build, test, package, and deploy workflows should behave the same way every time.
A system is more than its code; observability, releases, documentation, and maintenance all count.
OPEN_CHANNEL
Let’s build something dependable.
For engineering opportunities, systems work, or a conversation about Linux and backend architecture, send me a note.