Eduardo Sanchez Diaz

Foundry gives you Ontology, Workshop, Slate, Pipeline Builder — a huge toolkit. But most teams never get the full value out of it, for a simple reason: the business side knows exactly what they need but not what the platform can do, and a pure engineer can make the platform hum without ever asking whether the app actually solves the right problem. The result is either a wishlist nobody can build, or a technically solid app nobody wants to use.

I sit at that intersection. As the technical focal point between business and engineering and a developer, I translate what stakeholders actually need into applications that use Foundry's full power — Ontology objects, Workshop interfaces, Slate dashboards, PySpark/Spark SQL pipelines — and build them with the fluidity and UX that make people actually want to use them, not just tolerate them. Five years doing this in the aerospace sector taught me that the hard part is never just the code or just the requirements — it's holding both at once.

Track record:

Equally comfortable dropped into an existing team mid-sprint or leading adoption for a client from zero.