Mis-hires rarely fail on capability, they fail on context

If you’ve hired in AdTech long enough, you’ve seen it.

A strong CV.
Relevant logos.
Impressive numbers.

And then… 6–9 months later you’re wondering how someone with “the perfect background” didn’t land.

Our proprietary takeaway from patterns across AdTech hiring mandates:
Most “failed hires” don’t fail because they can’t do the job.
They fail because they were hired into the wrong context.

AdTech is particularly unforgiving here because the surface-level job titles look similar — but the environment behind them can be completely different.

A “Sales Director” at a DSP isn’t living the same reality as one at an SSP.
A “Commercial Lead” selling measurement doesn’t operate like one selling a managed service.
A “Partnerships” hire who thrived in cookies-era identity might struggle in a privacy-first go-to-market.

So when hiring goes wrong, it’s rarely a talent problem.

It’s a context definition problem.

The real gap: employers write job specs, candidates accept “games”

Most companies brief a role like a job description: responsibilities, targets, “must have” bullets.

Most candidates evaluate it like a game they can win: where the demand comes from, who buys, what slows deals, who owns the narrative, what “good” looks like internally.

When those two interpretations don’t match, you get an expensive outcome:

  • High activity, low conversion

  • Great relationships, no revenue

  • Early pipeline, late-stage stalls

  • “Smart operator” who can’t get traction

Across mandates, three context gaps show up again and again.


Context Gap #1: Motion mismatch (the most common AdTech mis-hire driver)

In AdTech, “enterprise sales” can mean at least four distinct motions:

  1. Agency-led buying (holding companies, trader desks, multi-layer stakeholders)

  2. Direct brand buying (marketing, commerce, data teams, shifting priorities)

  3. Publisher/supply-side sales (inventory strategy, yield, monetisation trade-offs)

  4. Platform/technical sale (integration cycles, security, data governance, product maturity)

On paper, it’s all “enterprise.” In reality, the motion determines everything:

  • Sales cycle length

  • Stakeholder count

  • How political the deal becomes

  • Whether ROI is provable quickly

  • How procurement behaves

  • How much technical depth is required

  • The role of relationships vs product proof

Pattern we see:
Companies hire someone who wins via one motion (e.g., brand-led velocity with strong inbound demand)… into a business that requires another (e.g., agency politics + long-cycle + procurement + complex activation).

The result is predictable:
You get activity, not outcomes.

Fix: define the motion in the brief as clearly as you define the role.
Not “sell to agencies,” but:

  • Who is the economic buyer?

  • Who blocks the deal?

  • What triggers urgency?

  • What’s the typical first “yes”?

  • What’s the typical last objection?

In AdTech, motion clarity reduces mis-hire risk more than almost anything else.


Context Gap #2: Proof without conditions (the CV tells you what happened — not why)

AdTech CVs are full of “proof”:

  • “Closed $X”

  • “Built $XM pipeline”

  • “Scaled a new market”

  • “Top performer 3 years running”

Useful… but incomplete.

Because outcomes in AdTech are heavily shaped by conditions.

Same revenue number can be achieved in wildly different environments:

  • Inbound vs outbound reality

  • Brand pull vs challenger selling

  • Established category vs “explain what we do”

  • Founder-led close vs process-led close

  • Pricing power vs discount-dependent

  • Clear attribution vs messy measurement

  • Strong integrations vs scrappy workarounds

Pattern we see:
Hiring teams over-index on outcome proof and under-index on the conditions that made those outcomes possible.

So they hire a “proven winner”… and put them into a totally different set of conditions.

Fix: In interviews, pressure-test with condition questions:

  • “Where did demand actually come from?”

  • “What did you do when you didn’t have a narrative the market understood?”

  • “How did you create urgency when budgets were already allocated?”

  • “How much of the win was relationships vs product/ROI proof?”

  • “What broke most often late-stage — and how did you unblock it?”

In AdTech, the best predictor isn’t the number.
It’s whether the candidate has won under similar constraints.


Context Gap #3: Metrics that aren’t agreed (and the hire becomes the compromise)

AdTech roles often carry multiple expectations at once:

  • Pipeline creation

  • Revenue delivery

  • Strategic positioning

  • Partnerships

  • Product feedback loops

  • Sometimes… team building too

That can work — but only when leadership agrees on what’s prioritised.

Pattern we see:
Stakeholders want different things, don’t resolve it upfront, and the new hire absorbs the ambiguity.

Examples that show up repeatedly:

  • Commercial wants a hunter; Product wants an “advisory seller”

  • Founder wants logos; Finance wants margin discipline

  • RevOps wants process; Market needs creativity

  • Partnerships wants long-term ecosystem; Sales wants this quarter’s revenue

The candidate gets hired as the “solution”… and then gets judged against shifting scorecards.

Fix: force alignment before you go to market:

  • What does “good” look like in 90 days?

  • What is the one leading indicator we care about most?

  • If two priorities conflict, which wins?

  • What will we de-prioritise to make this role achievable?

When you don’t decide, you don’t “stay flexible.”
You just outsource the decision to the person you hired.


The AdTech hiring reframe: define the environment, not just the role

A simple, repeatable way to reduce mis-hire risk is to write the brief in three layers:

1) The Motion

  • Who buys? (agency, brand, publisher, platform)

  • How do they buy? (RFP, relationship-led, performance proof, partner route)

  • What blocks deals? (privacy, measurement, integration, procurement, internal politics)

2) The Conditions

  • Is demand already present or do we create it?

  • How strong is our narrative today?

  • What’s our proof: case studies, benchmarks, logos, performance data?

  • What’s the implementation reality: fast activation or long technical cycle?

3) The Metrics

  • What are the leading indicators? (e.g., qualified agency relationships, live campaigns, integration milestones, win rate)

  • What are the lagging indicators? (revenue, retention, expansion)

  • What’s the time horizon for meaningful impact in this category?

If you can define those three, you can hire more accurately — and onboard more realistically.


What strong AdTech operators ask (and average ones don’t)

One of the clearest signals we see in process:
Top candidates ask context questions early — because they’re evaluating whether they can win.

They ask things like:

  • “Where are deals stalling today — and why?”

  • “Is measurement a strength or a debate in our sales cycle?”

  • “How much is relationships vs performance proof?”

  • “What’s the typical first use case that lands?”

  • “What does implementation actually look like?”

  • “Who internally makes the final call when stakeholders disagree?”

If candidates aren’t asking these questions, it’s not necessarily a red flag — but it is a reminder that you must define the context clearly yourself.


The bottom line

In AdTech, capability is table stakes.
Context fit is the differentiator.

If you want fewer mis-hires, don’t just hire for experience.
Hire for the ability to win in your environment — with your constraints — in this market.

Because the best hires aren’t asking, “Can I do the job?”
They’re asking, “Can I win in this context?

If you’re hiring right now, pressure-test your brief against the three gaps above before you go to market. It’s one of the simplest ways to protect your reputation, your runway, and your momentum.

Trusted by the worlds

most ambitious technology platforms.

SUBMIT YOUR JOB