Companies call me when the pilot worked but the team never followed. I sit with the skeptics, map what's actually broken, and redesign from there.
Most companies force AI on their teams. I sit with them, understand their actual needs, and guide them there.
My framework — Describe → Diagnose → Redesign — is how I approach every engagement: understand what's actually broken before touching anything.
Every skeptic has an "aha" moment. Getting there is more art than science, but once it happens, they see the value themselves.
Engineering roots, AI in production, then the part nobody wanted to do — getting people to actually use it.
Lead AI adoption across a 7,000-person org. Standardized research workflows, ran literacy training for 1,000+ employees, and built internal tools that replaced six-figure vendor contracts.
Shipped production ML pipelines for signal-processing workloads. Owned the path from research notebook to deployed service, and partnered with PM to translate model behavior into product surfaces.
Applied ML to defense-adjacent signal-processing problems. Co-authored two papers and built simulation tooling still used by the lab.
Focus on machine learning for signal processing. Thesis on adaptive filtering with neural networks.
Founding member of the campus ML reading group. Internships across signal processing and embedded systems.
Tell me about the pilot that didn't land, the team that pushed back, or the workflow nobody questioned. I'll read it carefully and reply within two business days.