From shipping docks to shipping code
I spent 7 years in logistics operations, watching good processes fail because the right tools did not exist. So I learned to build them.
The short version
I started in logistics ops at 18, inventory, carrier relationships, the whole grind at a freight forwarding company. By 22, I was managing enterprise accounts and negotiating carrier contracts. By 24, I realized the problems I kept hitting weren’t going to be solved by better spreadsheets.
So I learned to code. Not in a bootcamp way, in an “I’m going to build a homelab, break things, and ship real projects” way. I built my own Proxmox cluster. I self-hosted everything. I deployed production AI systems that actually handle real workloads.
Today, I bridge two worlds: I understand operations from the ground up, what makes carriers tick, how inventory actually flows, where processes break, and I can build the systems that fix those breaks.
I’m not a pure engineer who has never seen a warehouse floor. I’m someone who has lived the problems and learned to build the solutions.
Quick facts
- 7 years in logistics & supply chain operations
- Self-taught engineer with production AI systems
- Homelab enthusiast with 40+ Docker services
- 30+ active users on production AI system
- 98%+ performance optimization on logistics workflows
Currently
Open to W-2, 1099 contracts, or project work. Targeting full-stack roles where real problems have real stakes — platforms that move things, automate workflows, or apply AI to messy real-world data.
Target: $100K+ W-2, open to negotiating on 1099 or project arrangements — just want to work on problems that actually matter.
The journey
I got promoted out of an operations role into engineering because I apparently cared too much about the broken systems around me. Now I own the logistics platforms that move 7,000–10,000 shipments a year. Fixed a legacy PHP nightmare (80-90s load times → 1.26s), shipped a RAG AI agent that 30 people actually use instead of ignoring, and hit 99.99% uptime on our APIs. Turns out caring about the thing you're forced to work around is a good way to end up owning it.
Managed enterprise logistics for clients moving 500–1,000 containers a year across ocean and air routes from Asia. Negotiated rates, managed carrier relationships, and spent a lot of time explaining to carriers why their tracking data was garbage. Made clients happy, saved them money, and noticed every process that kept breaking — which turned out to be useful later.
Data entry. The glamorous stuff. Except I kept running into the same data quality problems over and over, figured out why they existed, and fixed them — saving ops about 20 hours a week in the process. Turns out if you pay attention in a job nobody expects you to pay attention in, you find all the problems.
I was the guy who explained HDMI vs USB-C to 100 people a day and got paid accordingly. Useful for learning patience. Also learned how retail really works from the inside, which ended up being more applicable than expected.
How I work
Ship, then iterate
Perfect is the enemy of shipped. I'd rather get something real in front of users and improve it based on feedback than spend months on something theoretical.
Ops first, tech second
Technology is a tool for solving real problems. I start with understanding the problem space deeply before touching any code.
Own the whole stack
I do not hand off deployment, infrastructure, or design thinking to somebody else. If I build it, I want to understand and own it end-to-end.
Real over impressive
Production systems that work reliably beat flashy demos every time. I care about things that actually hold up under real-world conditions.
Want to work together?
I'm always interested in projects that solve real problems. Let's talk about yours.