March 2026 | Essay
Building a backend niche that compounds
I want to build my career as a backend-focused engineer with real depth in reactive Java,
OMS workflows, and the supply chain domain. The goal is not just to collect technologies, but
to compound technical judgment in a niche where reliability, throughput, and operational clarity matter.
I enjoy going deeper into system behavior, architecture, and execution quality.
Over time, I want that depth to create opportunities at
top companies and also keep the founding-engineer path open as my product instincts grow.
Engineering note | Reliability
What alert storms taught me about backend design
One lesson I keep coming back to in backend work is that correctness alone is not enough.
A system can be logically right and still behave badly under bursty conditions if downstream
dependencies are treated as if they are infinite.
In OMS workflows, the shape and timing of traffic matters as much as the business rule itself.
I want to keep writing about patterns like rate limiting, graceful degradation, and operational
safety because they are part of what makes backend systems dependable at scale.
Engineering note | Operability
Why operability is a product feature for backend systems
Some backend improvements are valuable not because users notice them directly, but because they
reduce friction for the people operating, supporting, and evolving the system every day.
I am increasingly drawn to work that improves runtime control, safer changes, and smoother
production workflows. Those improvements compound over time and often become the difference
between a system that is merely working and one that is actually comfortable to run.