// the long version

From the Bronx to the control plane.

roleproduct lead · agentic aicompanyibmbasedsouth floridasince2014

I build systems that hold up under pressure, and I care most about the part of the work nobody photographs: the layer that decides what runs, what stops, and who answers for it.

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. That framing never left. It is how I read 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.

Today I’m Product Lead for IBM’s Agentic AI Platform, brought in to reset strategy for the enterprise agent control plane: orchestration, evaluation, governance, and the shared context layer that lets teams operate agents with confidence rather than optimism.

Outside the day job I write, build side projects, and archive history that would otherwise go unrecorded. BlackStory pins Black history to the places it happened. I am a husband and a father, based in South Florida, still a Bronx kid about most things.

what i work on

Agent orchestrationEvaluation & governanceReliability intelligenceOperational systems

elsewhere

Writing →Résumé →BlackStory →

// how i workfour things I keep coming back to

01Start where it breaksIncidents and workarounds tell you what the roadmap missed. I read them before I read the strategy deck.

02Measure before you promiseIf there is no way to tell whether the system improved, the work is a demo, not a product.

03Constraints are the briefRegulation, latency, cost, headcount. Designing around them honestly beats pretending they will move.

04Build for the person on shiftField crews taught me that the operator at 2am is the real user. Everything else is a preference.