The long version.
Bronx-raised. Husband and father. Ex-IBM, ex-HashiCorp.
I grew up in the Bronx, where infrastructure is visible. Trains, grids, buildings, the crews who keep them running. You learn early that everything around you is a system somebody maintains, or doesn’t. What I learned harder was the people layer. Family is more than blood, and sometimes blood is not family. The block was a melting pot. Boricua next door, Dominicana down the hall, West Indian kitchens, music from windows that weren’t yours, elders who corrected you like you belonged to them. Community held when paperwork didn’t. That framing never left. It is how I read a room, an org chart, a codebase, and an incident review.
My path into product ran through operations. At AT&T I led field crews and built the controls and routines that made service outcomes measurable. In regulated healthcare, at Sentry Data Systems (later part of Craneware Group), I modernized pharmacy compliance and analytics for more than ten thousand hospitals, pharmacies, and clinics, where being wrong was counted in patients, not points. At HashiCorp (carried through IBM’s $6.4B acquisition of the company), I built reliability intelligence, change-risk, and recovery systems for a nine-figure cloud portfolio.
After the acquisition I was Product Lead for IBM’s Agentic AI Platform, brought in to reset strategy for the enterprise agent control plane, where orchestration, evaluation, governance, and the shared context layer sit so teams can run agents with confidence rather than optimism. Today I’m Product Lead for Platform at Panorama Education, which builds tools for the kind of student I was.
Outside the day job I write and I build. BlackStory puts census data and archive records on the map next to the streets they belong to. At home I’m a husband and a father of two, based in South Florida, still a Bronx kid about most things that matter. The systems I build have to answer to the people they affect, including mine.
- 01Start where it breaksIncidents and workarounds tell you what the roadmap missed.
- 02Measure before you promiseAgree on how you’ll know it worked before anyone commits to a date.
- 03Design around the constraintsRegulation, latency, cost, and headcount are part of the problem, so they shape the design from the start.
- 04Build for the person on shiftThe operator at 2am is who it has to work for, so that’s who I test it against.