Own the egress path that routes Cloudflare's network traffic to any destination on the Internet

Cloudflare's Egress team builds the network software that lets products like WARP and the iCloud Private Relay proxy connect out from Cloudflare's edge to any destination. This interview probes Go/Rust systems programming, L3/L4 networking depth, and comfort operating a Run-What-You-Build service with on-call responsibility at Internet scale.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Go and/or Rust systems programming
L3/L4 networking (TCP/IP, routing)
HTTP, TLS, and CDN network behavior
Secure, highly-available distributed systems design
Production debugging and on-call ownership (Run What You Build)
AI-assisted engineering workflow

Common question themes

Design a secure, highly-available egress/proxy path for traffic leaving an edge network

Debug a production issue in a distributed network service under your team's on-call rotation

Go vs Rust tradeoffs for systems-level networking code

How TLS/HTTP behave differently across CDN-fronted connections

Handling an escalated customer issue with an ambiguous root cause

How you'd use AI tools to analyze a codebase or production dataset

How candidates describe it

Real Senior Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Bloomberg · Senior Software EngineerOffer

Bloomberg Senior Software Engineer Interview: Five Rounds, Offer

A Senior Software Engineer candidate applied to Bloomberg's London office through the company's careers site and, after an initial screen, went through five separate on-site conversations covering coding, system design, a recruiter chat, and a hiring-manager round, ultimately accepting an offer.

Interviewed October 2022 · London, United Kingdom

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

View the original posting

All Cloudflare Senior Software Engineer interviews

All Cloudflare interviews