What's up everyone, today we have the pleasure of sitting down with Elizabeth Dobbs, AVP of Marketing Technology, Data and Growth at Databricks.

(00:00) - Intro
(01:18) - In This Episode
(01:47) - Sponsor: Knak
(02:55) - Sponsor: MoEngage
(04:16) - Why Velocity Beats Permanence in Marketing Data Architecture
(12:00) - Why Databricks Embedded Data Engineers Inside Marketing
(15:02) - Inside Databricks' 3 Marketing Ops Agents
(18:56) - How Databricks Built an AI Analyst That Marketing Teams Actually Trust
(26:13) - How Agent Tagatha Cut Months of Manual Content Tagging to Hours
(30:07) - Sponsor: AttributionApp
(31:09) - Sponsor: GrowthLoop
(34:48) - How Agent Atlas Replaced the Rules-Based Segmentation Wheel
(39:28) - Why Marketers Don't Care Whether You Call It an Agent
(43:32) - How to Get Data Warehouse Access When Your Team Doesn't Own It
(48:36) - What Databricks Is Actually Testing for in Marketing Hires Now
(54:04) - What Gives Liz Energy Outside the Office

Summary: Elizabeth Dobbs spent 6 years at Databricks doing something most marketing leaders only talk about: building the data infrastructure before deploying the AI on top of it. She's shipped 3 production agents (Marge, Tagatha, and Atlas) and she'll tell you exactly what broke first and why the team kept going anyway. You'll hear how a marketing lakehouse becomes the foundation that makes every agent actually work, why the agent label debate is a distraction, and what Liz is genuinely testing for in marketing interviews now that AI-polished resumes all look the same in Greenhouse. If your AI ambitions are running ahead of your data foundation, this episode is going to reorder your roadmap.

About Elizabeth Dobbs

Elizabeth Dobbs is the AVP of Marketing Technology, Data and Growth at Databricks, where she leads the team responsible for the company's full marketing stack, including data engineers and data scientists embedded directly in marketing. Promoted to AVP in February 2025 after more than 5 years building Databricks' marketing data infrastructure from scratch, she architected the company's marketing lakehouse and deployed 3 production AI agents serving the entire marketing org. Before Databricks, she spent nearly 7 years at Khoros in a series of marketing operations and demand generation leadership roles, including Chief of Staff to the CMO.

Why Velocity Beats Permanence in Marketing Data Architecture

If you work at a company called Databricks, you assume the marketing data is fine. The word "data" is literally in the name. When Elizabeth Dobbs was interviewing 6 years ago and someone in sales ops told her straight up that the data was a complete mess, she thought they were being politely humble. She took the job. She found out they meant it.

What she encountered fit the startup playbook exactly. Agencies hired for agency's sake because headcount was thin. Systems that barely talked to each other. Stacks of what she calls "human middleware," people spending their days manually bridging gaps the infrastructure couldn't close. Databricks was probably no worse than any other high-growth startup at that scale. But fixing it meant accepting something most marketing teams resist: building for permanence is a waste of energy.

When Liz and her team sat down to fix things, they made a call that runs against how most marketing orgs are wired. They stopped trying to build the perfect foundation. At 1,000 people, you might get away with it. At 10,000, perfection is a distraction. By the time you finish, the company has changed shape again. So they optimized for velocity. Centralized data imperfectly. Built shared definitions that not everyone followed consistently. Accepted the bubblegum-and-duct-tape reality. And they stayed intentional about exactly 1 thing: knowing which decisions you cannot walk back.

The one-way door framework is how they sorted the rest. Some decisions hurt to make but compound over time. A marketing lakehouse, all first-party data in 1 governed and catalogued place, is the example she keeps returning to. There is no SaaS tool you would buy, no agent you would deploy, that wouldn't benefit from having that foundation underneath it. That makes it a no-regret decision even when it's brutal to build. The other category, the rip-and-replace bets, is where you move fast and hedge. Agents might automate an entire workflow in 18 months. They might not be ready. You place smaller bets there and iterate. What you don't do is apply the same level of commitment to decisions that actually shouldn't last.

6 years later, the core of Databricks' marketing stack looks a lot like it did when Liz started. LeanData. Familiar prospecting tools. The same basic webinar infrastructure. The vendors who survived are the ones who grew alongside the team, who stayed flexible as Databricks scaled well past what their standard playbook assumed. In a market that treats every tool as disposable, the ones that last are the ones that earned it. The companies that build durable AI systems in marketing will be the ones who made the unsexy architectural call first and let everything else follow from it.

Key takeaway: Before committing to any AI agent or new platform, split your roadmap into 2 categories: one-way doors and reversible bets. A centralized, governed marketing data layer goes in the one-way door category. Pour resources into it without condition and treat every setback as a speed bump. For everything else, including which agents you deploy and which tools you layer on top, move fast, hedge small, and iterate. Run that filter on your next planning cycle and you'll stop debating tools and start building the foundation that makes all of them actually work.

Why Databricks Embedded Data Engineers Inside Marketing

Marketing ops leaders who don't have embedded data engineers spend a lot of time explaining to others why they can't move faster. Liz's team has data engineers and data scientists who report into marketing, not into a central IT org. Most people assume she fought for it. The actual story is less dramatic and more instructive.

It came from 2 leaders giving the team room before they could prove the full return. Her CMO Rick and CCIO Mike Hamilton were direct about it: we have our own fires, you know enough to be dangerous, you know where the lines are. File Jira tickets if you need something outside your lane, but otherwise go run. That kind of organizational trust is rare. What made it stick was showing the velocity difference on something concrete. Bring in 1 or 2 data engineers with actual marketing domain experience, and the speed gap becomes obvious. Marketing data has its own rules. MDF means different things to different teams. ROAS has regional variations. Pipeline attribution is a political minefield. Someone who has lived in that domain moves 10 times faster than someone learning it in place.

That observation turns out to apply directly to the agents Liz's team built later. You spend months onboarding a new hire with marketing domain context. That person leaves before the investment fully pays off and you start over. Agents don't do that. You train them, you give them the context, they hold it. What Databricks figured out with internal resourcing, they've since encoded into how they think about deploying AI. The parallel is direct and Liz draws it explicitly: the reason domain knowledge matters for people is the same reason it matters when you're configuring an agent.

The team that resulted from this structure is part of why Marge, Tagatha, and Atlas were even possible. You can't build a marketing lakehouse without engineers who understand what the data is supposed to represent. You can't deploy an agent ...