The SFMC Skills Gap: What Most Companies Are Actually Missing

Salesforce Marketing Cloud is one of the most powerful — and most commonly underutilised — platforms in the enterprise marketing stack.

Most companies that run SFMC believe they have adequate capability in the platform. Their programme results suggest otherwise.

The gap between what SFMC can do and what most teams actually use it for is significant. And in nearly every case, that gap is not a platform problem. It is a talent problem — specifically, a skills gap that often sits undetected inside existing teams for years.

What Most SFMC Teams Actually Look Like

The majority of SFMC teams at ANZ enterprise companies are structured around a core of campaign managers and email marketers who have grown up using the platform at a functional level.

They understand Email Studio. They can build and send a campaign. They manage contact lists, configure send classifications, and navigate the reporting dashboards.

What is often missing is the layer below — the technical depth that determines whether the platform is actually being used for what it was built to do.

AMPscript is the clearest signal.

AMPscript is Salesforce Marketing Cloud's proprietary scripting language. It is the mechanism by which SFMC delivers genuinely dynamic, personalised content at scale. A team that cannot write AMPscript beyond copying documented snippets is a team that cannot meaningfully personalise. They are using SFMC as an expensive batch email sender.

This is more common than most marketing leaders realise.

The Three Layers of SFMC Capability

Understanding the skills gap requires mapping what genuine SFMC capability actually looks like across three layers.

Layer 1 — Campaign operation. This is the level most teams have. Send emails, manage audiences, run A/B tests, pull basic reports. The platform is used primarily through the UI, with minimal scripting or technical configuration.

Layer 2 — Technical configuration. This includes proficient AMPscript development, SQL querying inside Automation Studio, Data Extension architecture and relationship management, Journey Builder design beyond simple linear flows, and API calls into and out of SFMC. Teams with this capability can deliver meaningful personalisation and automation. Most ANZ enterprise teams have one or two people at this level — if they are lucky.

Layer 3 — Platform architecture. This is the level most companies are actively missing. It includes Data Cloud integration (previously CDP), Marketing Cloud Connect configuration with Sales Cloud and Service Cloud, custom application development in SFMC's app framework, advanced API orchestration, and governance of the overall SFMC data model as it scales. This level requires someone who understands SFMC not as a campaign tool but as a platform with infrastructure implications.

The skills gap that costs companies most sits at the boundary of Layer 1 and Layer 2 — and the complete absence of Layer 3 thinking in most teams.

The AMPscript Problem

AMPscript deserves specific attention because it is the single most reliable signal of technical SFMC depth — and the skill most commonly missing.

A candidate who can write clean AMPscript is someone who understands how SFMC data is structured, how to reference Data Extensions and relationships, how to handle conditional logic and null values gracefully, and how to build content that is genuinely dynamic rather than template-with-a-name-inserted.

Testing for this in an interview is straightforward. Show a candidate a content block with a conditional personalisation requirement and ask them to write the AMPscript to deliver it. The gap between those who can and those who cannot is immediately visible.

What is less immediately visible is the cumulative cost of running without this skill. Campaigns that were built with static content because the team did not have the technical capability to personalise them properly. Data Extension structures that are increasingly tangled because nobody has the SQL knowledge to query them correctly. Automation Studio automations that break quietly because nobody on the team understands the underlying data flow.

Journey Builder: Used but Not Mastered

Journey Builder is the second major area where the skills gap concentrates.

Most SFMC teams can build a Journey. The basic logic of entry, decision splits, and message steps is accessible enough that campaign managers learn it relatively quickly.

What they rarely master is the architecture of scalable journeys — and the mistakes that happen when Journey Builder is used without that understanding.

Re-entry logic. Understanding when to allow re-entry, how to handle contacts who are simultaneously in multiple versions of a journey, and how to structure exit criteria to avoid message duplication requires a level of technical precision that is not intuitive.

API-triggered journeys. Journeys triggered by real-time events — a transaction, a support ticket, a loyalty tier change — require API configuration that most campaign managers have not done. Without this, SFMC journeys are scheduled and batch-driven rather than genuinely event-triggered.

Journey governance. In organisations with multiple teams using Journey Builder, the absence of governance creates compounding problems. Contacts getting conflicting messages across journeys, suppression lists that do not interact correctly across programmes, contact limits being hit without clear visibility into which journeys are responsible. These are architecture problems that require someone who owns the SFMC data model, not just individual campaign owners.

What Data Cloud Changes About the Skills Picture

The emergence of Salesforce Data Cloud — SFMC's customer data platform layer — has materially changed the skills requirement for organisations that have adopted it or are evaluating it.

Data Cloud integration with SFMC requires a level of data architecture understanding that sits outside traditional marketing skillsets. Unified profiles, identity resolution, data streams from multiple source systems, segment activation — these concepts require someone with a background that spans both marketing technology and data engineering.

The talent pool for this combination is thin in ANZ. Companies that have Data Cloud live, or that plan to activate it in 2026, need to be deliberately searching for this profile — because it will not appear in a standard SFMC campaign manager shortlist.

Why the Gap Stays Hidden

The skills gap in SFMC teams persists in part because it is genuinely difficult to see from inside the organisation.

Marketing leaders evaluate programme performance, not platform depth. If email campaigns are going out and the metrics are acceptable, the platform appears to be working. The counterfactual — what would the programme look like with proper technical depth — is invisible.

The gap typically becomes visible in three scenarios.

First, when a platform migration or re-implementation is required — and the team discovers they do not have the capability to architect the new environment themselves. The audit that precedes this work often reveals structural problems that have been accumulating for years.

Second, when a new hire joins at a technical level above the existing team — and immediately identifies the limitations in the current data model, journey architecture, or AMPscript implementations. This creates friction, because fixing the legacy structure requires political capital as well as technical skill.

Third, when a competitor or peer organisation runs a visibly more sophisticated personalisation programme — and leadership asks why the same platform is producing very different outcomes.

Hiring for the Right Layer

The practical implication for hiring is that the job description for an SFMC role needs to be much more specific than most companies make it.

"Marketing Automation Specialist with SFMC experience" will generate a large pool of Layer 1 candidates. Some Layer 2. Almost no Layer 3.

If Layer 2 is what you need, the job description needs to specify AMPscript proficiency, SQL querying in Automation Studio, and Journey Builder at a technical level — not just campaign building. And the interview process needs to test for it directly.

If Layer 3 is what you need, the specification needs to describe the platform architecture context — which clouds are connected, what the current data model looks like, what Data Cloud involvement exists — and the candidates need to demonstrate systems thinking about SFMC rather than campaign delivery capability.

The difference in hire quality between a generic SFMC job description and a specific one is significant. And the cost of hiring at the wrong layer — and discovering it six months later when the programme has not moved — is material.

FutureHero places Marketing Automation specialists across ANZ and Southeast Asia — including SFMC developers, architects and campaign specialists at every level. If you are hiring for an SFMC role and want a specialist shortlist, talk to us.