Salesforce Marketing Cloud Next Consultant

Greetings from zealous services!

Position: Salesforce Marketing Cloud Next Consultant

Contract | Project Nova

Experience: 10 - 12 Yrs

Work Mode: Remote (Contract)

About the Role

Our Company is delivering Project Nova, a multi-division Salesforce programme spanning Court & Process, Investigations, Digital, Depositions, Records, eDiscovery and Client Care. As part of that program we are standing up our marketing capability on Marketing Cloud Next, built natively on the Salesforce core platform and Data 360.

We are looking for a hands-on technical consultant to own the configuration and build of that capability. This is a core platform role. Segmentation, campaign orchestration, consent and deliverability all live inside Salesforce, and the work sits directly alongside Sales Cloud and Service Cloud rather than in a separate stack connected by sync.

Please note: this is not a Marketing Cloud Engagement role. If your experience is primarily Email Studio, Journey Builder, Automation Studio and AMPscript, we would still encourage you to read the section below on how that background maps across but it is not sufficient on its own.

What You Will Do

• Own the Data Cloud model underpinning our marketing capability data streams, DMOs, identity resolution, calculated insights and data graphs and make the modelling decisions before the build starts rather than after.
• Design and build segments, campaigns and campaign flows, and take them from requirement through to live send.
• Configure sender authentication and domain setup, manage IP warming, and own bounce and suppression handling.
• Implement consent and preference management to a standard that stands up to scrutiny in a legal services context.
• Build email content in the Lightning email builder, including responsive templates and rule-based dynamic content.
• Design Campaign, Campaign Member and lead lifecycle structures that work for both marketing and the wider CRM.
• Work from user stories and acceptance criteria: take part in grooming, size realistically, flag dependencies early, and support QA when defects come back.
• Tell us when a requirement will not work. We would rather hear it in refinement than discover it in UAT.
• Document solutions properly in Confluence and explain technical constraints in plain language to marketing stakeholders.

Essential Experience

1. Data Cloud / Data 360

This is the foundation of the platform, not an adjacent skill. We expect practical experience with data streams, DMOs, identity resolution and the Unified Individual, calculated insights, data graphs, segment build and activation, and Contact Point Email and Phone. You should be able to explain why the data model has to be settled before the build begins, and what it costs to unwind it later.

2. Core Salesforce platform fluency

Flow Builder across both Campaign Flows and admin Flows, including how a flow is coupled to a campaign as its automation engine. Also permission sets and the sharing model, record-triggered automation, and custom objects and fields. This role needs someone who can build on the platform, not only configure within a marketing interface.

3. Campaign and Campaign Member on core

Because there is a single data model rather than a connector between two clouds, Campaign, Campaign Member and lead lifecycle design is central to the role. Familiarity with how Marketing Cloud Next handles attribution through Opportunity Influence — based on engagement rather than campaign membership — is expected.

4. Deliverability and sender configuration

SPF, DKIM and DMARC, private domain setup, IP warming, sender configuration, bounce handling and suppression. This is live on our project now and it is the area where mistakes are most visible to the client.

5. Consent and preference management

Individual and Party Consent, Contact Point Type Consent, Communication Subscriptions, and preference pages built in Experience Cloud. Working knowledge of CAN-SPAM and GDPR obligations. In legal services this is not optional. Experience with LWR sites is a distinct advantage given our parallel portal work.

6. Content build in the Lightning email builder

Solid HTML and CSS for responsive templates, plus personalization through merge fields against the Unified Individual and related DMOs and rule-based dynamic content. Note that personalization here is not AMPscript-based.

7. Marketing operations judgment

Lead lifecycle, campaign lifecycle, segmentation logic and attribution understood as concepts rather than as buttons in a tool. On a platform this new, a significant part of the job is knowing what the product cannot do yet and designing around it. We weight this heavily.

Desirable Experience

• Marketing Cloud Engagement background — Valuable as transferable judgment in journey design, deliverability and data modelling instincts.
• Agentforce and Prompt Builder — Relevant as our marketing scope moves toward agentic capability.
• Migration or coexistence experience — Running Marketing Cloud Engagement and Marketing Cloud Next in parallel.
• SQL — For calculated insights and data transforms — Data Cloud SQL rather than Automation Studio SQL.
• Marketing Intelligence and reporting — Our reporting scope is expanding.
• Apex and Lightning Web Components — For extending beyond declarative configuration.

A Note on Marketing Cloud Engagement Experience

We are being explicit about this because we know the market is confusing right now, and we do not want strong people to self-select out or apply on a mistaken basis.

Marketing Cloud Engagement and Marketing Cloud Next are architecturally different products. Engagement runs on separate infrastructure with batch data syncing and Journey Builder for orchestration. Marketing Cloud Next is built on the Salesforce core platform on Data 360, with real-time data processing and flow-based orchestration. There is no Automation Studio, no AMPscript, no Marketing Cloud Connect, no Contact Builder, and no Business Units in the Engagement sense.

If you have deep Engagement experience, your judgment transfers — journey and lifecycle design, deliverability discipline, and the instinct that data modelling decisions are expensive to reverse. Your tooling does not. We are open to candidates in that position, provided you have genuinely started building on Data Cloud and the core platform and can talk about it concretely. Please make that part of your background explicit in your application.

Relevant profiles kindly share your updated CV to [email removed]