I like taking fuzzy product problems and turning them into systems people can rely on.

I lead backend engineering here now. A lot of the work is still close to the metal: shaping agent workflows, reviewing tricky integration designs, improving internal engineering flow, and helping teammates turn messy requirements into systems we can ship and trust.

I joined as the first engineer and built the backend from scratch: ticketing on top of Slack and Teams, real-time sync with tools like Zendesk, Jira, and Salesforce, event pipelines for analytics and SLAs, and early AI helpers that could classify, respond, create tickets, and trigger actions across other systems.

Part of a two-person tech team building a hyperlocal platform from scratch with Flutter, Node.js, Nginx, and a tiny DigitalOcean budget. We handled product work, deployment, scaling, and customer onboarding ourselves, so every technical decision had to be simple and cheap enough to live with.

Built a geometry-aware instant quoting system for 3D manufacturing instead of the usual bounding-box shortcuts. I had to learn enough about materials, manufacturing constraints, and pricing logic to make the Three.js interface and quoting flow produce numbers customers could actually trust.

My first serious production work. I built the Flutter side of a kids' digital library app, handled responsive UI across devices, and wired Flutter into a Unity-based story engine so the app experience and backend stayed in sync.