I build software the way the Army taught me to lead: deliberately.

My path into software didn't start with a bootcamp curiosity — it started with problems I couldn't ignore. Watching small healthcare businesses drown in disconnected tools. Watching leaders spend their mornings chasing personnel statuses through group texts. Watching people in the market I come from stay uninsured because the process was built for paperwork, not phones. Each of those became a product I designed, built, and shipped.

I'm an active-duty Noncommissioned Officer in the U.S. Army. Being an NCO means being the person responsible when things have to work: for people, for equipment, for the plan and the fallback plan. That responsibility translates directly into how I build software — I plan before I code, I design for the person who will actually use the system, and I treat security and reliability as part of the mission, not afterthoughts.

On the technical side, I work across the full stack — from data modeling and role-based access control to accessible, responsive interfaces — with formal education in software and web development and graduate-level study focused on AWS cloud computing. As a founder, I've carried products through the whole unglamorous middle: payments, onboarding, deployments, and the iteration that follows real users.

What pulls it all together is a simple conviction: the best software comes from people who understand the operation it serves. Healthcare workflows, unit accountability, small-business bookings, insurance in emerging markets — I build for problems I've seen up close, and I keep learning so the next platform is better than the last.