About
Engineering operational software
I don't just write code — I build systems that help teams work smarter.
I'm a Computer Science graduate who found my path through building software where it matters most: inside organizations that depend on accurate data, reliable workflows, and systems that don't break under real-world use.
My work spans baseball analytics, hospitality operations, and enterprise IT — three different domains united by the same principle: translate complex business requirements into software people actually use.
I think in systems. Before writing code, I ask what problem exists, who feels it, and what a successful outcome looks like. That mindset shaped every product in my portfolio — from pitch-by-pitch analytics to automated event pricing engines.
What drives me is the moment software removes friction — when a coach sees a pattern they couldn't before, when event staff stop double-booking rooms, when IT teams finally have one source of truth for their assets.
Career Path
Computer Science
Foundation in algorithms, systems, and software design
IT Internship
Enterprise infrastructure and operational support
Software Engineering Internships
Full-stack development in production environments
Building Operational Software
Shipping products that improve how organizations run
Approach
Engineering philosophy
Build Real Solutions
I focus on software that solves operational problems — scheduling, inventory, analytics, and workflows that teams rely on every day.
Design Before Code
I map user flows, data models, and system boundaries first so architecture supports the business problem, not the other way around.
Continuous Improvement
Production software evolves. I ship iteratively, measure impact, and refine systems based on real usage and feedback.
Technologies
Tools I build with
Organized by layer — from interface to infrastructure.
Frontend
Backend
Databases
Cloud
Developer Tools
Languages