From Concrete to Code.

The Pivot: Why I Stopped Watching

Before earning my M.S. in Computer Science, I spent seven years as a Project Engineer managing large-scale housing projects. I saw the technological innovations transforming other industries -- automation, data pipelines, predictive modeling -- and felt that construction was just beginning to catch up.

I realized I didn't just want to watch that transformation happen; I wanted to be the one building the solutions. That shift drove me to fully transition into engineering robust backend systems and ML pipelines.

Operational Grit & Resourceful Ownership

My background in engineering operations taught me that engineering isn't just about writing code -- it's about solving bottlenecks under constraints. Whether volunteering for non-profits like JerseySTEM and The Chad Foundation or building personal projects, I focus on end-to-end ownership.

I don't just reach for the most expensive tool. I design systems that solve real-world problems efficiently -- often figuring out the best possible solution within limited resource constraints.

What I Build Today

I combine operational grit with software architecture to build reliable infrastructure. My recent work includes:

• Material Forecasting Engine: An AI-driven pipeline (Python/FastAPI/Docker) tackling construction pricing volatility.
• Permit Workflow Service: A backend service (Node.js/TypeScript) modeling complex municipal compliance lifecycles.
• Integration Pipelines: Architecting cost-effective data syncs (Make.com/Integrate.io) that drastically reduce API costs for non-profits.