Deliverability just got a director
This month a large receivables operation — roughly 1,100 people, in one of the most regulated corners of email — posted a director-level role. Not a marketing manager who also watches deliverability. A director whose stated mandate is sender reputation, domain health, and inbox placement.
TL;DR A 1,100-person receivables operation posted a director whose mandate is sender reputation and inbox placement. That is still rare: across our scan of 117 companies hiring for this work, only 2 gave the role a deliverability title. The work is everywhere; the title almost nowhere.
What does a director-level deliverability role signal?
Read the org chart implication, because that's where the signal is. Whether this company's email arrives is now important enough to belong to someone senior, full-time, with a title. A year ago the same responsibility would have been a bullet buried in a marketing-ops job description, squeezed between the campaign calendar and the reporting deck. Now it's the job.
Why did it happen in receivables first?
It makes sense that it happened here first. In receivables, email isn't marketing — it's the operation. If the notice doesn't land, the account doesn't get worked, and the payment doesn't come in. Layer on the compliance stakes, where every message is regulated and auditable, and "did it arrive, to the right person, on time" becomes a revenue question and an audit question at once. That's exactly the kind of pressure that promotes a background task into a named function. When email is load-bearing, someone has to be accountable for whether it holds.
Why is deliverability a posture rather than a setting?
And "hold" is the right word, because deliverability isn't a setting you configure once — it's a posture you have to maintain. Authentication that stays aligned as records drift and vendors change. Domains you can afford to put at risk, kept separate from the ones you can't. Reputation you actively defend as volume and content shift underneath you. Holding that posture is genuinely a job, and the companies where email drives the P&L are the first to admit it by writing it on an org chart.
Most companies aren't the receivables firm — but they have the same exposure and no one who owns it. The invoices, the password resets, the renewal notices all have to arrive, and responsibility for whether they do is assumed to live with the ESP, or with whoever set up the DNS records two years ago and moved on. The failure is silent by design: nothing emails you when your SPF breaks or your reputation slips. You find out from the revenue, weeks later, working backward.
And the mandate is about to get wider. The first reader of that notice — or invoice, or renewal — is increasingly not a person but an AI agent that summarizes, triages, and sometimes acts before a human ever sees it. "Did it land" is becoming table stakes; the new frontier this director will own is "did the agent on the other side read it the way we meant" — whether the urgency survived, whether the ask came through, whether a machine acted on the right thing. Almost no one is measuring that yet. When whether-your-email-lands becomes a director's job, it tells you where every email-dependent business is headed. Most will get there the way this one did — by hiring a human to hold the posture full-time. Increasingly, they'll get there by automating it.
The title has kept moving since. Two employers in our hiring scan have now put deliverability in the job title outright instead of burying it in the responsibilities, and the same scan found domain and IP warm-up specified in specialist-level briefs rather than only in leadership ones — the responsibility is travelling down the seniority ladder as well as across the org chart: are companies really going to hand DNS administration to marketers?
How rare is a deliverability title, really?
Two in 117. Per our scan, in our scan of 117 companies hiring for this work, we classified how each company titled the role. In that dataset, deliverability appears constantly in the responsibilities and almost never in the title:
| How the role is titled | Companies | Share |
|---|---|---|
| Lifecycle | 46 | 39% |
| Email-titled | 26 | 22% |
| Other / Growth | 21 | 18% |
| Marketing Ops / Automation | 20 | 17% |
| CRM | 2 | 2% |
| Deliverability-titled | 2 | 2% |
That is the gap this director role closes. The work is already distributed across all 117 companies in the sample; what is missing almost everywhere is a name on it. Two out of 117 is not a category yet — it is the leading edge of one.
Does company size predict whether the posture is any good?
Strongly, and the curve is steeper than you would guess. Our scan audited every one of those 117 sending domains against live DNS. Clean authentication tracks almost linearly with headcount:
| Company size | n | Zero outbound gaps | DMARC enforced |
|---|---|---|---|
| Under 200 | 34 | 38% | 50% |
| 200–1,000 | 55 | 67% | 80% |
| Over 1,000 | 28 | 79% | 89% |
A 1,100-person company sits in the top band of that scan, where roughly four in five already have clean authentication. Which is the point: at that size the basics are usually done, so hiring a director is not about fixing SPF. It is about the part that authentication does not cover — reputation, placement, and whether the posture holds as vendors and volume change underneath it. You can check the basic half yourself with an authentication audit in a few seconds.
Three things change once the mandate is senior and named:
- It gets a budget, so tooling and seed-inbox testing stop being someone’s side project.
- It gets a baseline, because you cannot report on a posture you never measured.
- It gets escalation rights — the ability to stop a send, which no marketing manager has.
What does the mandate actually contain?
Strip the title and a deliverability mandate decomposes into four things, only three of which are measurable from outside:
- Authentication that stays aligned as records drift and vendors change. Binary, cheap, and automatable in CI — but our scan found 97% publishing DMARC and only 74% enforcing it.
- Sender reputation, including blocklist status. A listing is silent and immediate; the blocklist checker finds the real sending IPs from the SPF record first.
- Domain separation — keeping the domains you can afford to risk apart from the ones you cannot, which is why a replatform is dangerous and why a new platform inherits none of your good name.
- Inbox placement — and this is the one no DNS check reaches. It needs seed inboxes or provider feedback, and a director who claims otherwise is guessing.
The recurring failure is treating the first as the whole job. It is the visible quarter, so it gets done; the rest waits for someone whose explicit mandate it is. Continuous posture monitoring covers the drift half automatically, which is what frees a senior hire to work on the part that actually needs judgement.
Key takeaways
- In our 117-company scan, only 2 gave the role a deliverability title — 39% called it Lifecycle, 22% Email, 17% Marketing Ops.
- In the same scan, clean authentication tracks with headcount: 38% under 200 people, 67% at 200–1,000, 79% over 1,000.
- DMARC enforcement in that dataset follows the same curve — 50%, 80%, 89% by size band.
- At 1,100 people the scan says the basics are usually already done, so a director-level hire is about reputation and placement, not about fixing SPF.
- Inbox placement is the one part no DNS check can measure. It needs seed inboxes or provider feedback data.
FAQ
How common is a dedicated deliverability title?
Rare. In our scan of 117 companies actively hiring for deliverability responsibilities between May and August 2026, only 2 gave the role a deliverability title. Lifecycle accounted for 39%, email-titled roles 22%, marketing operations 17%. The work is nearly universal among senders at scale; the title is not.
Does company size predict email authentication quality?
Yes, and steeply. Among the 117 companies we audited, 38% of those under 200 people had zero outbound authentication gaps, rising to 67% at 200-1,000 and 79% above 1,000. DMARC enforcement followed the same curve at 50%, 80% and 89%. Larger senders have usually cleared the basic bar, which changes what a senior hire is actually for.
What does a deliverability director own that a marketing manager doesn't?
The parts that are continuous rather than binary. Authentication is a one-time fix that can be automated in CI. Reputation, domain separation and inbox placement require ongoing judgement as volume, content and vendors change. The distinguishing responsibility is holding a posture over time, not configuring one correctly once.
Can inbox placement be measured from DNS?
No. DNS shows what you have published and public blocklists show reputation signals, but neither reveals whether a message reached the inbox or the spam folder. That requires seed inboxes across the major mailbox providers or provider-supplied feedback such as Google Postmaster Tools. Any tool claiming to predict placement from DNS alone is inferring, not measuring.
Sources
- Kucherawy, M. and Zwicky, E. RFC 7489, DMARC — policy semantics behind the enforcement figures.
- HireAmino. What 117 companies hiring for deliverability actually publish in DNS — the scan behind the figures here, audited against live DNS.
- Google. Email sender guidelines — bulk-sender authentication requirements and the 0.30% spam-complaint ceiling, in force since February 2024.
- Yahoo. Sender best practices — the second half of the 2024 bulk-sender requirements.