Tawfic Alexander
Shnoudeh

I grew up wanting to understand how things work — not just mechanically, but systemically. Why does a city build a subway line here and not there? What makes a power grid reliable under stress? Why does a bridge last a hundred years and a software company last ten? These aren't separate questions. They're all asking the same thing: what does it take to build something that endures?

That curiosity pulled me toward mechanical engineering first — because physical systems are honest. If your analysis is wrong, the structure fails or the mechanism jams. There's no hiding behind a spreadsheet.

Then I started reading about infrastructure finance, and found the same quality of rigor applied to questions I'd never thought to ask: how do you price a thirty-year concession? How do you structure a toll road deal so the equity investor and the government don't have misaligned incentives? What discount rate do you use for an asset that's politically contentious but physically essential?

I'm studying engineering, but I think about capital. I'm learning finance, but I start from systems. Most people in each field don't cross over — and that's the gap I want to occupy.

I want to work at the intersection of infrastructure, capital, and engineering judgment — specifically in infrastructure investment or project development, where both skill sets are genuinely necessary and neither is optional. The job I'm building toward doesn't have a clean title yet, but it looks something like: evaluate projects that engineers under-price and investors misprice, and find the structures that make them work.

My medium-term goal is to build technical and financial credibility simultaneously — not sequentially. Most people in this field start in engineering, spend five years there, then pivot to finance. Or they start in finance and hire engineers as consultants.

I want to understand both well enough to make decisions that integrate them from the start: to read an interconnection study and a project finance model and understand how they constrain each other.

Longer term, I'm drawn to the kinds of projects where the engineering constraints are poorly understood by investors, or the financial constraints are poorly understood by engineers. Energy transition infrastructure — grid upgrades, utility-scale storage, new generation — is the obvious candidate right now. So is urban mobility in dense, underbuilt cities.

These are places where the gap between what engineers know and what capital does creates real, persistent inefficiency. That inefficiency is both a problem worth solving and a place where someone fluent in both sides can add disproportionate value.

Most of the value in the modern economy flows through physical infrastructure. Not around it, not above it — through it. The internet runs on fiber and data centers. Electricity runs on transmission lines and transformers, most of them built decades ago. Goods move through ports and rail yards that are largely invisible to the people who depend on them.

The gap between how essential these systems are and how poorly they are understood by the people who finance and govern them is, I think, the defining problem of the next two decades.

This isn't just a policy argument. It's a market observation. When engineers and investors don't share a common model of a system, assets get mispriced. Projects get structured in ways that optimise for the wrong constraints. Regulatory frameworks get written by lawyers who understand neither the engineering nor the economics. The result is chronic underinvestment in systems that are too important to fail but too complex for any single discipline to fully hold.

I believe the energy transition makes this problem more acute before it makes it easier. Adding large amounts of variable generation to a grid that was designed for dispatchable power requires not just new technology but new financial instruments, new regulatory models, and new ways of thinking about risk across a thirty-year asset life.

The people who will do the most important work in that transition will be the ones who can hold the engineering and the finance simultaneously — who understand why a battery storage project's revenue stack looks the way it does because they understand the physics of the grid it sits on.

That's the capability I'm building. Not because it's a clever career strategy, but because the problems that interest me most require it — and because most of the people currently working on these problems are operating with half the model.