Steady. Hires across networking, security, edge compute (Workers), R2 (storage), AI Gateway, Zero Trust, and product teams.
Cash plus RSUs with annual refresh. Public since 2019. Total comp is generally below FAANG at the same level but competitive with mid-tier big tech. Check levels.fyi for current ranges.
> **How current is this?** Checked 3 August 2026. This company does not publish its interview structure, so everything here is what candidates consistently report. Loops change without announcement, so treat this as a guide rather than a specification.
Cloudflare runs a global edge network spanning 300+ cities. That scale shows up in the interview process. Most candidates report the loop emphasizes practical engineering judgment, distributed systems knowledge, and networking depth more than algorithmic puzzles.
The first distinctive element is when the Hiring Manager screen happens. Most companies put a hiring manager conversation at the end of the loop after the technical bar is cleared.
Cloudflare often puts it after the recruiter screen but before the deep technical rounds. The hiring manager is checking team fit and motivation early.
If you do not make it through this round, the rest of the loop does not happen.
The Code Pair round is the second distinctive element. You sometimes complete a take-home assignment before the onsite, and one of the onsite rounds is a paired review and extension of that take-home with an interviewer.
They watch how you read your own code, explain your decisions, and make changes under discussion.
Networking depth gets probed throughout. Even on generalist product loops, expect questions on how the internet works: TCP congestion control basics, what happens during a TLS handshake, how DNS resolution works, how HTTP/2 and HTTP/3 differ.
Generic systems engineers can pass without deep networking, but candidates with real knowledge stand out.
Culture is engineering-driven. Two of Cloudflare's stated values are Curious and Transparent. The behavioral round often probes for genuine technical curiosity (what are you reading, what was the last paper that surprised you, what side projects) more than for rehearsed ownership stories.