About · Engineering trajectory

Engineering is the territory. AI is the technology. Delivery keeps them connected.

I build intelligent software for complex engineering workflows, connecting domain context, systems architecture, applied AI and technical delivery.

01
FIELD
I had to make physical systems work.
My first engineering loop connected customer discovery, electrical loads, photovoltaic design, economics, installation and operating feedback. Residential, commercial and industrial projects taught me that a technically sound answer also has to make economic sense and survive field conditions.
02
MODEL
I learned to represent them computationally.
Electrical BIM/VDC added Revit, coordination, constructability and prefabrication. The gap between design intent, model state and field reality became visible. A model was useful precisely because I knew what it could leave out.
03
CONSEQUENCE
Mission-critical projects made failure matter.
Data centers, healthcare and industrial work brought dependencies, redundancy, maintainability and sequencing into every decision. Evidence and change control mattered because the consequences continued beyond the drawing.
04
SOFTWARE
I moved from using tools to building them.
Revit automation grew into full-stack systems, data and evidence architectures, QA, installers and release workflows. Software did not replace the domain; it made domain knowledge programmable.
05
AI
Now software can investigate more of the system itself.
My current work connects requirements, models, drawings and schedules so software can search evidence, call tools and keep investigating. Fixed checks and human review define which decisions it can make. The result has to return to the working environment.

The system is not the model. It is the accountable workflow around it.

Three principles I carry into the work.

Based in Mexico · Working globally · English and Spanish.