I build the tools that
let teams ship faster.

I started as a frontend engineer and fell in love with building interfaces. But I kept asking “what happens on the other side?” — and never stopped pulling that thread.

Over the years I've grown from building UIs into a hybrid role that spans product engineering, internal platform tooling, and end-to-end delivery. I've designed internal libraries like shared form and wizard libraries that other teams adopt as standards. I've architected CI/CD pipelines on Azure DevOps, integrated auth and API security across frontend and backend layers, and owned config-driven architectures that let teams ship merchant-facing features safely through feature flags.

Along the way, I've led teams of up to 23 developers, coordinated cross-functional rollouts, and mentored engineers through migrations and platform adoption. Leadership for me isn't a title — it's about creating the systems and documentation that help other people do their best work.

I hold an MS in Computer Science from Northeastern University, where I built a job application tracker during a hackathon that was featured in Northeastern News — a small tool born from a real frustration that I'm now rebuilding at a larger scale. Before grad school, I spent three years building Industrial IoT applications, leading UI teams through AngularJS-to-React migrations, and shipping D3.js data visualization dashboards. Today I'm building in the AI developer tooling space. I've shipped two open-source Claude Code plugins — PromptOps, which treats prompts like tested code, and Shipwise, a 15-skill launch lifecycle plugin that makes Claude Code's answers production-ready. Shipwise covers the full journey from idea validation through post-launch growth, and was validated with a 12-scenario QA suite showing 2× auth security improvement. I'm also exploring RAG agent workflows and building a cross-platform mobile app from scratch.