• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

What’s up everyone, today we have the pleasure of sitting down with Angela Rueda, Director of Business Martech at Meta.

Summary: Angela walked into Meta’s engineering-first culture, discovering a sprawling mess of DIY custom martech solutions, and leading the organization through a fundamental mindset shift about build vs. buy decisions. She brings us through the technical and emotional journey of aligning more than 150 stakeholders ultimately forcing them to embrace a hybrid build-and-buy approach during a pivotal merger. Angela shares an honest look at what it means to lead big changes at a company like Meta, showing what really works when you’re trying to transform how marketing and technology work together.

In this Episode…

• Build vs Buy: Meta’s Transformation to a Hybrid Martech Stack
• Why Meta Ultimately Ditched Their DIY Martech Stack
• How to Navigate Enterprise Martech Vendor Selection Successfully
• How 150 Stakeholders at Meta Actually Agreed on a Martech Stack
• TL;DRs Can Save Your Calendar From Technical Quicksand
• How Meta Streamlines Marketing Asset Creation at Scale
• Marketing Tools Live and Die By Your Data Architecture
• Martech Leaders Will Outgrow Their Technical Roots

About Angela

• Angela started her career in the agency world before moving over to the financial services sector at Capital Group 
• She took a break from the corporate world and co-founded a lifestyle product company for moms and babies
• She later returned to finance and joined Citibank where she would spend the next 8 years growing into a Director of Marketing Capabilities role
• Today Angela is Head Director of Business Martech at Meta where she’s building a new team of data and performance marketers

Disclaimer: The views and opinions expressed by Angela in this episode are her own and do not necessarily reflect the official position of Meta.

Build vs Buy: Meta’s Transformation to a Hybrid Martech Stack

Building custom marketing technology sounds like a tech leader’s dream: unlimited resources, world-class engineers, and total control over the final product. Angela walked into Meta with stars in her eyes, ready to architect a marketing infrastructure that would reach 200 million global businesses. The mandate sparkled with possibility – create something truly custom, uniquely Meta, uniquely powerful.

Then reality hit. Meta’s growth had spawned a sprawling organism of marketing tools, each piece stitched onto the next as urgent needs arose. What looked like a blank canvas from the outside turned out to be a complex tapestry of tactical solutions, each thread woven tight to solve an immediate problem. The engineering team kept adding features:

• Custom targeting modules for specific campaigns
• Program-specific deployment tools
• Siloed analytics systems
• Fragmented automation workflows

For that first year, Angela doubled down on the in-house vision. Meta’s engineering DNA made external tools feel almost taboo. The team kept building, feature by feature, convinced they could craft the perfect solution. You might recognize this mindset – when you’re surrounded by brilliant engineers, buying off-the-shelf software feels like admitting defeat.

A major organizational shift cracked the foundation of this thinking. Business marketing teams merged, exposing a stark reality: half the company used internal tools while the other half relied on third-party platforms. Maintaining multiple stacks drained resources and created confusion. The breaking point arrived organically – continue forcing an internal-only approach, or step back and reimagine the entire stack?

This constraint sparked the creative breakthrough Angela had dreamed of, just not in the way she expected. The pressure to consolidate forced hard questions about build versus buy decisions. The team had to examine their assumptions about custom development and weigh them against business needs. That original blank canvas materialized after all, painted with the colors of experience rather than theory.

What makes Meta’s story feel universal is that enterprise teams everywhere build tech kingdoms in isolation, they’re all racing toward their own goals with blinders firmly in place. Marketing squads assembling custom tools and processes at breakneck speed, treating enterprise-wide alignment as a distant luxury and a future-team problem. Then all of a sudden, organizational shifts take place. Restructures, mergers, leadership overhauls… they generate enough force to crack these silos open. When the dust settles and processes collide, teams finally see the cost of their fragmented systems.

Key takeaway: Build a hybrid Martech approach: identify core functions that need customization, integrate best-in-class tools for standard operations, and focus engineering resources on unique competitive advantages. Track implementation time and team satisfaction to measure impact.

Back to the top ⬆️

Why Meta Ultimately Ditched Their DIY Martech Stack

Meta’s engineering culture practically demanded they build everything in-house. You could feel it in every meeting: the subtle eye rolls when someone mentioned third-party tools, the reflexive reach for custom solutions, the collective pride in crafting bespoke technology. Their homegrown marketing stack embodied this philosophy, sprouting feature after feature until it required a small army of PhDs just to create basic audience segments.

Angela walked into this technical labyrinth with a mandate to reach 200 million global businesses. The existing tools scattered across Meta’s landscape told a story of rapid growth and tactical thinking:

• Data lived in isolated kingdoms, making it impossible to identify true marketable audiences
• Campaign targeting required advanced degrees and dedicated data science teams
• Channel activation cobbled together “omnichannel” experiences through manual patches
• Sales and marketing data existed in parallel universes, never quite connecting

Then came the organizational earthquake: a massive merger that exposed half the company running on internal tools while the other half relied on external platforms. The duplicate systems drained resources faster than a leaky pipeline. This crisis created a rare moment of organizational clarity, pushing Angela’s team to step back and question their build-everything DNA.

The evaluation process sparked intense emotions. Engineers who poured years into custom solutions defended their work with spreadsheets and scoring frameworks that mysteriously always ended in perfect ties. You could see the internal struggle written across faces in every meeting: let go of years of custom development or double down on the DIY approach? The breakthrough came through radical simplicity. Meta chose to build where they held unique advantages (their data foundation) and buy proven solutions for standard capabilities. This hybrid model gave both the engineering perfectionists and practical business stakeholders something to embrace.

Key takeaway: Start with ruthless problem definition before touching tools. Map your unique challenges, build organizational alignment around those problems, then evaluate build versus buy decisions through that lens. Your best solution might combine internal strengths with external innovation, creating a practical path forward that serves both technical excellence and business reality.

Back to the top ⬆️

Build vs Buy Was Really Privacy Control vs Speed to Market

Engineering pride runs deep at Meta. Their developers wield a particular swagger, architecting some of the world’s most sophisticated social platforms. So when Angela’s team questioned whether to keep building marketing tools in-house, the debates turned fierce. The war room crackled with strong opinions about resource allocation, privacy constraints, and the true cost of maintaining bespoke systems.

The arguments for building centered around three thorny challenges:

• Privacy requirements demanded granular control over data handling
• Data transfer costs between systems could balloon into millions
• Complex account mapping for B2B marketing defied off-the-shelf solutions

Yet the buy advocates painted a compelling picture: Meta’s elite engineers could focus on revenue-generating products instead of reinventing marketing wheels. Angela watched the back-and-forth intensify as both camps dug in their heels. One side championed engineering autonomy; the other preached speed to market. The spreadsheets grew more elaborate, weighted scoring frameworks multiplied, and still no clear winner emerged.

The reality of corporate priorities added another wrinkle. Internal tools live and die by shifting company focus. One quarter’s strategic initiative becomes next year’s legacy system, starved for resources and innovation. Third-party vendors, by contrast, must evolve their products to survive. They pour consistent development effort into features and integrations, freed from any single company’s strategic whims.

Meta ultimately landed on a hybrid model that would make a purist’s head spin. They kept core data handling and identity resolution in-house while embracing external tools for standardized capabilities. This pragmatic split delivered new marketing capabilities within a year, far faster than their traditional build cycle. The lesson? You need enough internal engineering to make external tools sing, but trying to build everything yourself turns into an endless resource sink.

Key takeaway: Ground your build vs buy decisions in cold hard math. Calculate the true cost of engineering time, factor in long-term maintenance burden, and be honest about your unique requirements versus standard industry needs. Then build only what truly demands custom development and buy proven solutions for everything else.

Back to the top ⬆️

How to Navigate Enterprise Martech Vendor Selection Successfully

The Martech purchase cycle at large companies often resembles a high-stakes poker game where millions ride on decisions made under intense time pressure. When Meta tackled their marketing technology unification project, they faced a perfect storm: reorganization deadlines, investment cycles closing, and fiscal year pressures all converging at once. Yet their team resisted the urge to rush straight into vendor demos.

Instead, they anchored their entire selection process in ruthless quantification. Their business case focused on two measurable targets:

• Campaign capacity: How many additional campaigns could teams run with freed-up resources?
• Campaign impact: What precise lift in targeting and personalization metrics would justify the investment?

The vendor evaluation process shattered typical enterprise software buying patterns. Meta assembled an unusually diverse selection team:

• Marketing strategists who owned campaign results
• Engineers who would handle technical integration
• Data scientists focused on measurement frameworks
• Operations leads responsible for daily execution

Their sandbox testing phase spotlights an often-overlooked reality in enterprise software buying: sales demos paint an incomplete picture. Meta’s teams rolled up their sleeves and tested real scenarios, uncovering limitations that glossy presentations often gloss over. “Everything seems possible during a vendor pitch,” Angela notes. “You have to push hardest for details when everyone’s putting their best foot forward.”

The Meta team’s network proved invaluable during final selection. They sought out companies who had walked similar paths, gathering practical wisdom about implementation roadblocks and vendor relationships. This reconnaissance paid off in unexpected ways – they uncovered patterns in how different solutions handled edge cases and scaled over time. Most crucially, they drove toward genuine consensus rather than mere majority agreement. “We made everyone’s job harder over the last year,” Angela admits. “But securing true buy-in meant people stuck with us through the tough transition period.”

Disagree and commit is such an important part of this. A leader who takes time to fully grasp opposing perspectives – to really sit with them, turn them over, understand their core – creates something electric. Picture that moment in a meeting when your boss reflects your viewpoint so clearly that even though they’re heading in a different direction, you feel the thrill of being deeply understood. Not empty nodding, but the raw power of acknowledgment rewiring how teams process tough calls. The stark difference between feeling heard versus feeling steamrolled ripples through every conversation, every project, every outcome.

Key takeaway: Skip the fancy demos and focus on three critical elements: build a business case with specific efficiency metrics you can measure, test technical capabilities hands-on in a sandbox environment, and secure genuine cross-functional agreement before signing any contracts.

Back to the top ⬆️

How 150 Stakeholders at Meta Actually Agreed on a Martech Stack

Angela’s team built a brutally practical framework that turned a chaos of Martech opinions into coordinated action.

Start with microscopic detail. Your scoring matrix needs surgical precision. Angela’s teams mapped out every technical requirement with obsessive specificity:

• Engineering teams probed system scalability limits and API robustness
• Privacy squads picked apart data handling with regulatory scrutiny
• Marketing ops dove into integration scenarios and workflow patterns
• Business users stress-tested everyday usability in real conditions

The organizational structure hits like a well-oiled machine. Each layer serves a clear purpose: sponsors steer the ship, 150 stakeholders provide domain wisdom, and working teams execute. Think data engineering, data science, marketers, and implementation partners all moving in sync. The Martech team grows muscle where needed, expanding through the business case.

Angela weaponized her team structure. Two distinct units operate with laser focus: product builders advance core tech while delivery squads hunt business wins. “You can’t distract builders with constant business demands,” she says. This creates a forcefield around technical development while business impact stays red hot.

Want to see pure genius? Watch how they proved value. Angela’s team picked the gnarliest pilot projects possible – her “shiny objects” that pushed every boundary. Marketing teams got the golden question: “What’s the most audacious thing you want to build?” These pilots went full throttle: bleeding-edge personalization, real-time everything, multi-channel mayhem. While infrastructure scaled quietly in the background, these early wins lit up the ROI dashboard in year one.

Each team sent one voice to the table. These representatives carried their tribe’s wisdom into battle. The selection moved like clockwork: initial demos sparked questions, technical teams dug trenches, cross-functional scoring brought clarity, final selection emerged from data. No requirements surfacing six months late. No death by committee. Just clean, clear decisions backed by 150 minds working as one.

Key takeaway: Your Martech selection needs three weapons: hyper-detailed scoring that covers every technical corner, single representatives who distill team wisdom into actionable input, and bold pilot projects that prove value while you build foundations. Split your technical and delivery teams. Let builders build. Let business wins flow. Watch ROI appear in year one.

Back to the top ⬆️

TL;DRs Can Save Your Calendar From Technical Quicksand

Technical brilliance becomes a curse when no one understands what you’re saying. Angela’s journey from journalism to Martech leadership at Meta taught her that painful lesson. You might write beautiful architectural diagrams. Your integration patterns could bring tears to an engineer’s eyes. But when decision time comes, none of that matters if you can’t speak human.

The TLDR mindset transforms how your work lands with others. Angela’s team developed a ruthless framework for cutting through noise:

1. Start with pure impact: “50,000 new customers reached”
2. Strip every technical term that doesn’t serve the story
3. Package updates in tight, three-part rhythms:
   1. Promise what you’ll build
   2. Show progress in bite-sized chunks
   3. Celebrate concrete wins

Your technical depth creates blind spots. Every week someone asks Angela “What’s a CDP?” Your brain screams the obvious answer, but pause. That question reveals a gap between your technical paradise and everyone else’s reality. Angela learned to cherish these moments – they force you to translate complexity into value that resonates.

Watch what happens when you embrace radical simplicity. Angela’s journalism background taught her to hunt for headlines that grip attention. Now she challenges her team: “Make every update so clear my mother would understand it.” The results shocked them. Projects moved faster. Budgets got approved. People actually read their status reports. The same technical excellence, wrapped in words that connect.

Take your next technical update. Rip out every word that sounds like insider baseball. Replace architecture diagrams with concrete outcomes. Tell the story in crisp, human language that a high school student would get. Because here’s the raw truth: if you need a technical dictionary to explain your work, you’ve already lost your audience.

Key takeaway: Trade your technical comfort zone for brutal clarity. Lead with concrete wins in language anyone could understand. Document your work in clear, consistent cycles. Make your mother proud – write updates she’d actually want to read.

Back to the top ⬆️

How Meta Streamlines Marketing Asset Creation at Scale

Enterprise asset creation at Meta used to feel like juggling flaming chainsaws while riding a unicycle. Angela, who spearheads Meta’s marketing operations, transformed their content development from a tangled mess of Google Sheets and endless email threads into a precision machine that powers hundreds of global marketers.

Meta’s marketing team made an audacious bet: expanding Knak from a small-scale experiment to their central content hub. The results stunned even the seasoned veterans on Angela’s team. The platform became their virtual war room where content creation, editing, and translation coexist in perfect harmony. You know that moment when you realize your elaborate system of post-it notes could be replaced by a single digital dashboard? That’s what happened at Meta.

• Translation integration eliminated language barriers
• Real-time content alignment reduced approval cycles
• Centralized editing slashed revision time
• Brand consistency improved across global markets

The platform marriage with Salesforce proved particularly important. Enterprise platforms pack tremendous power, but power means nothing without accessibility. Meta’s marketing team discovered that user-friendly plugins could bridge the gap between complex capabilities and practical daily use. Think of it as adding training wheels to a motorcycle; you still get the horsepower, but now everyone can ride.

Angela’s team went further, integrating Movable Ink and experimentation tools directly into their Knak workflow. This created what Angela calls their “recipe of tools and solutions.” Her cooking metaphor rings true: just as a master chef combines ingredients to create signature dishes, Meta’s marketing ops team crafted their unique blend of built and bought solutions. The result was a content creation system that actually works for both technical teams and everyday marketers.

As Darrell puts it, marketing ops magic is like having a well laid out diaper changing station lol. 

Key takeaway: Build your marketing tech stack like a master chef builds a signature dish. Start with a robust central platform, carefully integrate complementary tools, and focus on making complex processes feel effortless for your team. Meta’s experience shows that the right combination of tools, thoughtfully implemented, can transform marketing chaos into controlled creativity.

Back to the top ⬆️

Marketing Tools Live and Die By Your Data Architecture

You want AI-powered personalization? Cool. First, Angela suggests you grab a shovel and dig into the unglamorous world of data architecture. Meta’s marketing team learned that structured data forms the bedrock of every flashy capability you dream about. Your beautiful Martech purchases turn into very expensive paperweights without:

• Clean, mapped audience segments
• Rock-solid consent tracking
• Sales data pipelines that actually work
• Measurement systems that tell the truth
• Smart form design that captures critical fields

“Building advanced marketing capabilities without proper data structure feels like trying to build a treehouse in saplings,” Angela says. At Meta, simple oversights in form field requirements cascaded into major technical debt. Optional fields that seemed harmless at signup became gaping holes in their customer data six months later.

Angela now advocates tripling down on data infrastructure before touching a single marketing tool. Meta’s painful journey taught her that executives who push for immediate results often create long-term disasters. Every time someone demands instant AI capabilities, she reminds them: mighty oaks grow from carefully tended saplings, and powerful marketing programs grow from meticulously structured data.

Marketing technology vendors love showing you shiny demos of real-time personalization. They conveniently skip the part about spending months cleaning your data swamp first. Want to avoid Meta’s expensive lesson? Grab your tech team, lock yourselves in a room, and map out every single data point you’ll need. Your beautiful marketing dreams depend on ugly data reality.

Key takeaway: Stop buying marketing tools until you’ve documented your data architecture requirements. Map your customer data flows, establish rigid collection protocols, and build a foundation that will actually support the capabilities you want. Marketing runs on data; make yours pristine before attempting anything fancy.

Back to the top ⬆️

Martech Leaders Will Outgrow Their Technical Roots

Martech professionals straddle an unusual career fence: too technical for pure marketing roles, yet rarely interested in managing engineering teams. Angela, Meta’s marketing operations leader, sees this hybrid skill set as a powerful catalyst for career growth rather than a limitation.

The classic Martech career path ends in a technical dead end. You master the tools, shepherd a transformation, then… what? Angela reframes the entire question: Martech professionals solve business problems through technology. That core skill transcends any specific tool or transformation project. While other specialists stay in their lanes, Martech pros develop a rare blend of capabilities:

• Deep technical understanding without getting lost in code
• Business strategy skills that drive real revenue
• Product development instincts from constant tool evaluation
• Marketing innovation expertise from the front lines
• Consulting mindset from solving complex problems daily

“We’re not here just for the transformation,” Angela emphasizes. Her team at Meta focuses on enabling marketing’s vision through technology, acting as a bridge between ambitious goals and technical reality. This positioning elevates Martech professionals from tool jockeys to strategic advisors who shape what’s possible.

The Martech skill stack opens doors far beyond traditional marketing technology roles. Angela’s team members regularly move into product management, business strategy, and innovation leadership. Some start in pure marketing roles but gravitate to Martech because they love solving complex puzzles. The common thread? A rare ability to translate business dreams into technical reality while keeping the human element front and center.

Key takeaway: Build your Martech career beyond the tools. Focus on developing broad business problem-solving skills through a technical lens. The most valuable Martech professionals think like strategic advisors first and technologists second. Your hybrid skill set prepares you for leadership roles across product, strategy, and innovation.

Back to the top ⬆️

Building Tech Leadership Career Without Sacrificing Family Life

Professional ambition collides with personal reality for every working parent. Angela, Meta’s marketing tech leader, transforms that daily tension into rocket fuel for both domains. Her approach smashes the myth that career passion must devour family time.

You’ll find Angela pumping herself up during morning commutes, turning her car into a personal hype machine. But the real energy flows from solution-building sessions with her team. She lights up describing collaborative calls where ideas ping-pong between minds and laughter punctuates breakthrough moments. That human connection, combined with genuine love for the work, creates sustainable career momentum.

Her leadership toolkit runs deeper than technical chops:

• Building solutions through human connection, not just code
• Creating space for idea cross-pollination in every meeting
• Injecting moments of joy into problem-solving sessions
• Drawing energy from team wins rather than solo achievements
• Using commute time for mental preparation and mood-setting

At day’s end, Angela powers down her laptop and dives into what she calls her “home caves,” where two toddlers await. These moments fuel her professional drive in unexpected ways. She wants her daughter and son watching her tackle complex challenges, absorbing lessons about work ethic and resilience through osmosis.

This dual motivation, the intrinsic reward of solving thorny problems plus the desire to model determination for her kids, creates a powerful feedback loop. Angela’s technical expertise opens doors, but her ability to weave together professional passion and family purpose keeps them from slamming shut. The result? A leadership style that draws strength from life’s beautiful mess instead of trying to compartmentalize it.

Key takeaway: Stop trying to balance work and life like they’re separate entities. Find ways your family motivates your career growth and let your professional wins inspire your parenting. When both domains fuel each other, you’ll discover sustainable success that doesn’t require sacrifice.

Back to the top ⬆️

Episode Recap

Four years ago, Meta handed Angela Rueda what looked like a dream project: “Build our internal marketing infrastructure using Meta engineers.” The promise glittered… but reality bit back. Angela walked into a technical debt labyrinth where years of rapid growth had created a patchwork of custom DIY Martech solutions. Marketing teams operated in silos, each with their own stack, while the engineering culture strongly favored building everything in-house.

Organizational change sparked the transformation. When small business marketing merged with enterprise, multiple Martech stacks suddenly needed consolidation. Different teams brought opposing philosophies about build vs. buy, and 150 stakeholders needed alignment. “For the first year, I was all about it,” Angela says about building custom solutions, her voice carrying the wry wisdom of someone who’s learned things the hard way. “We are an engineering company, and it’s really hard to think about going 3rd party.”

The transformation began with brutal honesty about core problems. Source data lived in chaos. Audience targeting required “a Ph.D.” to operate. Channel activation remained disconnected. Measurement sat fragmented across systems. Sales and marketing data lived separate lives. Angela’s team created detailed scoring frameworks, evaluated privacy implications, assessed scalability requirements, and analyzed integration complexity. But technical evaluation proved simpler than human alignment.

“At some point, a leader needed to make a decision,” Angela reflects. The team chose a hybrid approach: custom data foundation paired with third-party tools. They built a rigorous business case around efficiency and effectiveness. To maintain momentum, they picked high-complexity pilot projects as proof points – “shiny objects” that demonstrated value while the broader transformation continued. “Give people a flavor of what this can give you,” she explains.

Data architecture emerged as the bedrock of success. “Triple down on the data,” Angela advises. “The data enables everything.” She points to seemingly trivial decisions that create major downstream impacts: “Sometimes the biggest problem we face is that you didn’t capture that in the form, because you didn’t make that field obligatory.”

The human dimension demands constant attention. Angela spends nearly 50% of her time on internal communication, perception management, and executive alignment. Her journalism background helps her translate technical complexity into clear stories for diverse audiences. Her four-year-old says she “works in internet” – a description that makes her laugh but captures something essential about modern Martech leadership: technical expertise must blend with human understanding to drive real change.

Angela’s journey at Meta illuminates how technical transformation succeeds: through equal parts data architecture and human psychology, backed by unflinching honesty about what works and what doesn’t.

Listen to the full episode ⬇️ or Back to the top ⬆️

Follow Angela 👇

• LinkedIn

✌️

—
Intro music by Wowa via Unminus
Cover art created with Midjourney (check out how)

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

Related tags

See all episodes

Future-proofing the humans behind the tech

Apple •Pocket Casts•Google •Overcast •Spotify •Breaker •Castro •RSS

• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed