How Much Time to Spend on Hiring: Lessons From Cloudflare

Public companies rarely share hiring details in the open. Cloudflare’s leadership is an exception. Co-founder Matthew Prince laid out detailed numbers about how his company hires in a public Twitter thread. That includes how much time to spend on hiring at every level. Those numbers offer a rare, concrete benchmark for any hiring team. Most executives never publish numbers like these. Exposing the real time and cost behind hiring at their own company is an uncomfortable disclosure for most. How to Build a Hiring Process That Works for Senior and Specialized Roles covers that framework. Cloudflare’s numbers show what it looks like in practice, at scale.

How Much Time Should Managers Actually Spend on Hiring?

Cloudflare has more than 2,000 employees and a market cap in the tens of billions. Prince says he still personally sends every job offer the company makes. He also speaks with a quarter of all job candidates before they are hired. He claims to spend a third of his own time on hiring.

That expectation carries down through the company. Managers at Cloudflare are expected to spend 20 percent of their time on hiring. Individual contributors spend roughly 10 percent. Most companies treat hiring as a task squeezed between other priorities. Cloudflare treats it as a standing part of the job, at every level, not just HR’s.

The number itself matters less than what it signals. A manager who blocks off a fifth of their week for hiring sends a signal before a single interview happens. It tells the team something real about priorities. A manager who treats hiring as an interruption sends the opposite signal, whether or not that is the intent.

Why Do Curiosity and Empathy Beat Traditional Screening Criteria?

Cloudflare’s two most-valued candidate traits are curiosity and empathy. Prince has said the company weighs both above education, experience, GPA, and IQ. That is a notable ranking for a technical infrastructure company operating at that scale.

The logic behind it is straightforward. Curiosity predicts how someone handles a problem nobody has solved before. That is most of the job in a fast-moving technical company. Empathy predicts how well someone works with the people around them once they are hired. That shapes retention long after the interview is over. Using Skills-Based Assessments in Your Hiring Process covers how to build criteria like these into a structured interview. That beats leaving them to gut feel.

The Funnel Behind 1,455 Offers

Cloudflare received more than 200,000 job applications in 2021. That funnel narrowed down to 1,455 offers, with a 92 percent acceptance rate. Getting there took 23,919 hours of interviewing, or roughly 16 interview hours for every offer that was eventually made.

Those numbers say something most companies never measure about their own funnel. A 92 percent acceptance rate is unusually high. It suggests candidates already have a clear, accurate picture of the role and the company before an offer arrives. Sixteen hours per successful hire is not a small investment, but it is a deliberate one. How Do You Improve Your Offer Acceptance Rates? covers what typically drives a number that high. It also covers what happens when a funnel or an offer stage is weaker.

Most companies do not see 200,000 applications for a single hiring cycle, and that scale is not the point. What generalizes is the ratio, not the raw numbers. A smaller company can track the same shape of funnel: applications in, real interviews conducted, offers extended, and offers accepted. Watching how that ratio shifts over time reveals the same signal Cloudflare’s numbers reveal. It just shows up at a size that fits the company doing the hiring.

Why Does Cloudflare Deliberately Hire Slow?

RecruitAbility covered recently how speed in hiring becomes a real competitive advantage when clarity drives it. Cloudflare’s approach looks like the opposite on the surface. Prince describes the company’s process as intentionally slow. He also says he stays somewhat inflexible on a new hire’s starting compensation.

The two positions are not actually in conflict. Prince’s reasoning is straightforward. A company knows the least about a person on the day it hires them. So Cloudflare holds the line on starting pay. It rewards performance quickly instead, once real evidence exists. That is deliberate rigor, not indecision. The speed problem that costs companies strong candidates comes from unclear ownership and unresolved internal debate. It does not come from a company that has clear standards and simply refuses to skip them.

This approach carries a real trade-off. A company that holds firm on starting pay will lose some candidates. Those candidates go to a competitor willing to negotiate higher on day one. Cloudflare’s data suggests that trade-off is worth making deliberately, not by accident. A 92 percent acceptance rate is hard to reach if inflexibility were driving candidates away in large numbers. The candidates who stay are choosing the company’s overall proposition, not just the number on the offer letter.

What Other Hiring Teams Can Take From This

Cloudflare’s specific numbers will not fit every company, and they are not meant to be copied exactly. The pattern underneath them is what generalizes. Decide, in advance, how much time hiring actually deserves at every level of the company. Name the one or two traits that matter more than a resume line, and hold to them. Track the funnel closely enough to know what a healthy acceptance rate actually looks like. Decide, too, whether speed or rigor matters more for the role at hand. The right answer is not always the same one.

Curious how a very different kind of company approaches the same problem from the benefits side? Lessons From Goldman Sachs’ Employee Benefits Strategy looks at a different angle on retention. It comes from a much larger, more traditional employer. The question there is what keeps someone once they have already said yes.