Replit's first lifecycle hire is a deliverability story

What is a founding lifecycle hire actually for?

This week Replit posted for its first Lead/Senior Lifecycle Marketing Manager — a founding role, $165–215K, owning email, push, and in-app messaging — the pattern behind outbound that scaled sending but not landing across both its consumer and B2B motions. Most of the listing reads like standard growth marketing. Two lines don't: a requirement for "expert-level knowledge of email marketing… including deliverability," and a mandate to "build lifecycle marketing infrastructure from scratch."

That's a tell.

When does email stop being a marketing activity?

For most of a company's early life, email just works — right up until it doesn't. At Replit's scale (millions of users), transactional and lifecycle email stops being "a thing marketing does" and becomes a system. And the moment it's a system, deliverability — whether your mail lands in the inbox or quietly dies in spam and promotions — becomes its own discipline. This role isn't really "send more campaigns." It's "stand up the function that keeps email landing." Deliverability just crossed, at Replit, from invisible to named, owned, and budgeted.

Why is this expertise expensive?

Here's why that's hard enough to justify the comp band. Deliverability expertise is scarce and expensive — it spans sender reputation, authentication (SPF/DKIM/DMARC), IP warming, list hygiene, and inbox-placement monitoring, across whatever sending providers you happen to run. And it's invisible until it isn't: reply and activation rates slide for weeks before anyone connects the dip to a reputation problem. A founding hire inherits a greenfield — no instrumentation, no baseline, no playbook — and has to build the early-warning system while the plane is flying.

There's a predictable moment in every product-led or consumer company's life — call it the founding-deliverability hire — when email graduates from a marketing activity into infrastructure someone owns. Replit reaching it now, proactively, is the smart version; most companies hire this role reactively, after a deliverability incident has already cost them a quarter of pipeline.

The broader signal is bigger than one company. As send volume scales — and as AI accelerates how much email every company generates — "did it actually reach the inbox?" is becoming a first-class operational question. Right now, companies are answering it by hiring. Increasingly, they'll answer it by automating.

Why is the role almost never called deliverability?

Because the title follows the org chart, not the work. In our scan of 117 companies hiring for this work, we classified how each company named it. Per that scan, only 2 of 117 used a deliverability title; 39% said Lifecycle, 22% said Email, 17% said Marketing Ops. Replit’s posting is typical: a lifecycle title carrying an explicit deliverability requirement inside it. If you are searching job boards for “deliverability” you are seeing about 2% of the actual demand.

That mismatch matters for the person hired, because the title sets expectations with everyone else. A lifecycle manager is assumed to own campaigns; the job actually contains an infrastructure mandate that fails silently when neglected. The first thing a founding hire should do is establish what exists, since nobody has owned it before them — an authentication audit takes seconds and produces the baseline the role never had.

The comp band follows from how many disciplines the role spans at once:

• Authentication — SPF, DKIM, DMARC and alignment, across every sending vendor.
• Reputation — IP and domain warming, complaint rates, blocklist exposure.
• List discipline — bounces, engagement segmentation, suppression state.
• Measurement — building the early-warning system while sends continue daily.

What does a greenfield actually look like?

“Build from scratch” usually means these five things are absent, in roughly this order of urgency:

1. No baseline — nobody knows what today’s pass rate is, so no change can be evaluated.
2. No sender inventory — nobody can list every service that sends as the domain, which is the first thing DMARC reports reveal.
3. No early warning — records drift silently, so nobody emails you when SPF breaks.
4. No list discipline — bounces and complaints accumulate before anyone segments by engagement.
5. No separation — transactional and marketing mail share a domain, so a bad campaign takes password resets down with it.

Only the first three are measurable from outside, which is why they are the sensible opening move. Continuous monitoring covers the drift problem without headcount, and it turns the fifth item into something you can argue for with evidence rather than instinct.

Two signals a founding hire should establish before inheriting open rate:

• Reply quality — did a human respond with something a model would not have?
• Intended action taken — did the thing the email asked for actually happen?

What is different about doing this now?

The recipient is increasingly not a person reading in order. Assistants triage, summarise and act on mail before a human sees it, which changes what “good lifecycle email” means. A message optimised for a skimming human can lose its ask entirely when compressed by a model — and at Replit’s scale, with a developer audience, that share is higher than average.

It also degrades the metric the function is judged on. Open rate already survived one shock from Apple’s Mail Privacy Protection; agent pre-reads are the next. A founding hire who inherits open rate as the scoreboard inherits a number that is quietly becoming unreliable, which is a good argument for establishing reply quality and intended-action-taken early — and for checking what an agent actually extracts from the templates before they ship.

Key takeaways

• In our 117-company scan, only 2 used a deliverability title — 39% said Lifecycle, 22% Email, 17% Marketing Ops.
• Per that scan, searching job boards for “deliverability” surfaces roughly 2% of the real demand.
• A founding hire inherits no baseline in any of the postings we sampled, so the first move is measuring what exists rather than shipping campaigns.
• Only three of the five greenfield gaps are visible from outside: baseline, sender inventory and drift detection.
• Open rate is degrading as assistants pre-read mail, following Apple’s Mail Privacy Protection,, so a founding hire should establish better signals before inheriting a bad one.

FAQ

What is a founding deliverability hire?

The point at which email stops being a marketing activity and becomes infrastructure someone owns. It typically arrives when transactional and lifecycle volume reach a scale where a reputation problem costs real revenue, and it is characterised by a greenfield: no baseline, no sender inventory, and no early-warning system for authentication drift.

Why don't these roles carry a deliverability title?

Because titles follow the org chart rather than the work. In our scan of 117 companies hiring for deliverability responsibilities, only 2 used a deliverability title, while 39% used Lifecycle, 22% Email and 17% Marketing Operations. The responsibility is common; the title is rare, which makes the demand hard to see from job boards.

What should a first lifecycle hire do in week one?

Establish a baseline before changing anything. Confirm SPF, DKIM and DMARC and whether the policy is enforced or merely published; enumerate every service sending as the domain, which DMARC aggregate reports reveal; and set up drift detection, because authentication fails silently and nothing notifies the sender when it does.

How do AI assistants change lifecycle email?

They insert a reader between your message and the human. Assistants triage, summarise and increasingly act on mail, so a message that loses its ask under compression fails before a person is involved. They also degrade open rate further as a metric, following Apple's Mail Privacy Protection, which argues for establishing reply quality and intended-action-taken as signals early.

Sources

• HireAmino. What 117 companies hiring for deliverability actually publish in DNS — the scan behind the figures here, audited against live DNS.
• Apple. Mail Privacy Protection — the change that first broke open rate as a metric.
• 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.