CrackingWalnuts
Checked 3 August 2026. Cloudflare does not publish its interview structure. Everything on this page is commonly reported by candidates, so treat it as a guide rather than a specification.
| Round | Duration | What it tests |
|---|---|---|
| Recruiter Screen | 30 min | Background, target team. |
| Hiring Manager Screen | 30 to 45 min | Team fit, ownership, resume. |
| Technical Phone Screen | 60 min | Medium to hard DSA or practical task. |
| Code Pair | 60 min | Live coding, often extending a take-home. |
| System Design | 60 min | Distributed system at edge scale with deep dive. |
| Domain Deep (Networking or Distributed Systems) | 60 min | Deep questions on team's tech (TCP internals, TLS, edge consistency). |
| Behavioral | 45 min | Ownership, curiosity, cross-team work. |
Targeted guidance per round in this loop. Each section links to the matching track on the site. There is no shortcut list, the bar moves loop to loop, so build the pattern recognition and the stories from real practice.
Work the pattern templates until the recognition is instant. Trace one mock problem per pattern. Practice stating time and space complexity out loud before you write code.
Cloudflare SDE III (Senior Software Engineer) has 2 design rounds: System Design (60 min): Distributed system at edge scale with deep dive.; Domain Deep (Networking or Distributed Systems) (60 min): Deep questions on team's tech (TCP internals, TLS, edge consistency).. Bar is owning a non-trivial design end to end, with capacity numbers, a clear data model, and one deep dive you can defend under push-back. Pick problems from the track at the scale this loop tests and rehearse the structure: requirements, numbers, high-level design, data model, API, deep dive on one part, trade-offs.
Senior bar. The rubric shifts from execution to ownership at scope, judgment, cross-functional impact, and being calibrated on what is hard. Every story needs alternatives considered and what you would do differently.