Curiosity first.
Engineer always.

A LITTLE BACKSTORY

Learn by making.
Then make it better.

My work spans product interfaces, backend architecture, reliable application workflows, cloud delivery, and the debugging that begins after software meets real users.

Programming first became practical for me in school, when I started learning Python and building small experiments with the tools I had available. The important lesson was not a language; it was that a system could be understood by making it. That habit — learn by building, then test the understanding against reality — still shapes how I work.

My professional path moved through customer-facing software at SalesHarbor and into a founding engineering role at Bearconnect. Across those roles, I have worked through the product lifecycle: translating requirements, designing systems, shipping features, supporting releases, and resolving failures across the stack.

That work sharpened my definition of engineering. Writing code matters, but ownership also means understanding the surrounding system, responding when assumptions meet reality, and treating reliability and operating cost as product concerns.

Outside my production work, I use projects to explore harder technical terrain. AegisMind combines Go and Python services, gRPC, streaming RAG, and multi-agent workflows. CandidAI explores semantic candidate retrieval and portable CUDA/ROCm inference behind a BFF. Aevum tests offline-first synchronization against retries, duplicate delivery, out-of-order events, and clock drift using simulated wearable data.

I am interested in founding and product engineering because it rewards breadth without excusing shallow thinking. The long-term direction is straightforward: keep becoming better at building useful systems, work with people who care about the problem, and eventually turn that capability into products and a company of my own.