The Question You're Not Asking Before Every Marketing Automation Hire

Before writing a job description, before shortlisting candidates, before a single interview — there is one question that should be asked and answered clearly.

Who is actually logging into the platform every single day to make this build happen?

It sounds simple. In practice, it exposes a gap that causes more failed marketing automation hires than any other single factor.

The Strategy vs Execution Mismatch

Marketing automation roles carry titles that attract strategic thinkers. CRM Manager. Lifecycle Lead. Head of Automation. Marketing Technology Director. These titles suggest leadership, vision, and programme ownership — and they do attract candidates with genuine strategic ability.

Strategy is valuable. But if no one on the team is in the tool daily — writing SQL queries, building data extensions, testing trigger logic, debugging API payloads, QAing every send before it goes — the strategy remains a slide deck.

The mistake isn't hiring strategic thinkers. It's hiring strategic thinkers for roles where the immediate bottleneck is execution, and then discovering — six months later, when the programme hasn't moved — that the strategy had no builder behind it.

Before any hire, the question of who is doing the daily build work needs a clear answer. If the candidate in front of you is a strategic hire, there should already be someone in the team doing the execution work. If there isn't, the strategic hire is the wrong next hire.

Why Time in Role Is the Wrong Measure

The second gap in most marketing automation evaluation processes is using time in role as a proxy for technical depth.

Five years in marketing automation sounds senior. On paper, two candidates with five-year histories in the space can look identical. In practice, they may not be in the same category.

Candidate A spent five years in a stable environment managing an inherited programme — cloning existing journeys, updating copy, running standard batch sends, escalating technical issues to an agency or internal developer. The platform worked. Nothing broke badly. Five years passed.

Candidate B spent five years in environments where they owned the build end-to-end — designing data structures, writing custom scripts, integrating external data sources, solving production issues when a journey misfired. Five years also passed.

The first candidate has five years of platform familiarity. The second has five years of technical depth. The CV doesn't distinguish them. Years of experience doesn't either. The only thing that reliably surfaces the difference is asking about specific, technical, first-person work — and listening carefully to how the candidate describes it.

Hiring for Sends vs Hiring for Architecture

There is a version of this problem that plays out at the programme level rather than the candidate level.

Organisations under pressure to show immediate results from a platform investment will sometimes frame the hire around near-term output: "we need someone who can get emails out the door." They hire for that requirement and find a candidate who can deliver it.

Six months later, when the business wants to move toward CDP integration, real-time trigger logic, dynamic personalisation, or AI-driven journey orchestration, the person in the role isn't set up to build any of it. The programme is running. It is also stuck.

The foundation was built for batch sends. Rebuilding it for a more sophisticated architecture — while the programme is live — is expensive, disruptive, and entirely avoidable.

The right question at the start of any hiring process isn't only "what do we need this person to do right now?" It's also: "where does this programme need to be in two years, and does this candidate have the depth to get us there?"

What Good Evaluation Actually Looks Like

The hiring processes that consistently produce the right marketing automation candidates share a few common characteristics.

They ask about technical work in specific, first-person terms. Not "are you familiar with SFMC?" but "describe a complex data integration you owned — what were the data sources, how did you structure the data extensions, what broke and how did you fix it?"

They ask candidates to demonstrate, not just describe. A short technical task — reviewing a journey architecture and identifying issues, writing a basic query, or explaining how they'd approach a data quality problem — surfaces execution capability that interviews alone can't verify.

They evaluate curiosity as deliberately as they evaluate experience. Marketing automation platforms evolve rapidly. A candidate who keeps up — who has explored the new AI features in their current platform, who has a view on how agentic automation changes the role — is a different hire than one who stops learning once the immediate job requirements are covered.

And they ask early, clearly, who is logging in every day to do the build work. Not as a trick question. As the most important structural question in the process.

FutureHero recruits marketing automation specialists across ANZ and Southeast Asia — placing candidates who can build, not just advise. If you're planning a marketing automation hire, talk to us first.