Glenda Bautista-Baker

I started as a trafficker at DoubleClick when the industry was still arguing about what display advertising even was. I've been building the commercial layer of the internet ever since.

I came up through operations, which is a different education. I learned the industry from inside the failure: the misfiring tag, the reporting discrepancy, the gap between what the IO said and what the platform actually did. I know what those gaps cost, who feels them, and why they keep getting rebuilt wrong. The difference between a system that looks good in a review and one that holds up when someone actually has to use it is something I learned from the inside out. I design systems from the failure modes outward, not from a whiteboard.

From that foundation I built businesses — platforms, marketplaces, monetization standards, premium ad experiences — across many major format cycles before the industry standardized any of them. I know what's possible at the format level, the product level, the platform level, and the infrastructure level simultaneously — because I built through all four in sequence.

Most AdTech orgs split the product layer from the platform layer. I've never worked that way. I arrive where monetization infrastructure doesn't exist yet, hold both layers simultaneously, and build from the execution layer outward under live conditions — not as a consultant or an advisor, but as the person who owns it. Most roles I've held didn't exist before I walked in the door, built by being dropped in with no playbook, no team, no infrastructure, and having to invent from nothing. My work has spanned every variant of that problem: true greenfield builds, systems inherited mid-flight, mature platforms that needed to move faster than their infrastructure allowed — across publishing, broadcast, audio, video, gaming, and digital media.

The number of people who can walk into a non-adtech-native organization, read the terrain, design the infrastructure from scratch, and make it run under live revenue pressure is genuinely small. Seven times across structurally different terrain. Same pattern, different environment, every time.

I don't arrive without a hypothesis — I arrive having often been the customer, the operator, the person on the other side of the system that was supposed to work and didn't. Years before any product conversation started. When I read a new environment I'm calibrating against a highly informed prior, not starting from scratch. I know where it's going. I move there and set up shop. Shared language built from the same place — not frameworks, but from having actually been there.

What I do has gone by a lot of titles over the years: ad operations, programmatic, revenue strategy, ad product, monetization infrastructure — depending on who was doing the hiring and what part of the stack they could see. The work underneath was always the same. Platform strategy expressed through systems architecture, executed from the ground floor outward. The industry is only recently developing language for what that actually is. I've been doing it since before the language existed.

The gap between where the industry thinks AI is taking it and what actually holds up when you have to operate it at scale is the most interesting problem in the room right now. I can see it clearly because I learned this work before it had a name, when the reasoning had to be derived instead of inherited. The tools are changing. The infrastructure problem isn't.

Close to three decades in, the patterns are legible enough to me that I'm rarely surprised by where this industry lands. The bets I've made have mostly come in. I still find where it's going genuinely intriguing.