Cloudflare interview, decoded.

Updated · Sources at the end

Cloudflare publishes the outline of its process on its careers page. You talk to a recruiter, then meet your prospective manager and peers in team panel interviews, then have executive calls with senior leadership. Those calls include what Cloudflare calls the Orange Cloud Interview, "focused on the behaviors we value." The page does not say what the Orange Cloud Interview asks, how long it is or how it is scored.

Candidates fill in the rest, and in 2026 their loops look alike. A London candidate in August 2026 sat a culture round, a PM interview, a 45-minute debugging round on an HTTP server with broken routing, a system design and an AI-assisted coding round where AI tools were allowed. An Austin candidate in April 2026 describes the same mix: an orange cloud behavioural interview, a debugging discussion, system design, a PM interview and an AI-assisted challenge fixing bugs in an unfamiliar project. Cloudflare cut more than 1,100 jobs in May 2026 and says its use of AI rose more than 600% in three months. It is still hiring: 470 roles were open on its board on 17 November 2026.

Free · 2 minutes · no account

The questions for your exact Cloudflare role and level.

01

Who Cloudflare hires

On 17 November 2026 Cloudflare had 470 open roles on its Greenhouse board. 112 had engineering titles, and 79 of those were software or systems engineers. The teams are the ones that run the network and the developer platform: Workers Runtime, Durable Objects, R2 storage, Queues, Hyperdrive, Quicksilver (the distributed key-value store), load balancing, DNS, SSL/TLS, WARP, Zero Trust, bots and fraud, network connectivity and egress. Newer teams build AI products: Workers AI, AI Gateway, MCP portals and agentic commerce. Austin is named on 61 of the 79 software and systems ads, then New York (34), London (33), San Francisco (27) and Lisbon (23). Most ads are hybrid (52) or in-office (23); only three are distributed. Rust appears in 52 ads, and on-call duty in 24. Interns are hired for 2027 in Austin, London and Lisbon. Cloudflare's 2026 intern announcement says it will fast-track interns who build an AI-powered application on Cloudflare.

Wondering whether your resume reads like someone Cloudflare hires? Get a free resume review.

02

What is the Cloudflare interview process?

The step names below are Cloudflare's own, from its careers page, read on 17 November 2026. The page gives no durations and no round list, so the formats come from candidate reports dated May 2025 to August 2026, and each row says which. The loop varies by team and level: some candidates sit four interviews after the hiring manager, others six.

6 roundsInitial conversation · Hiring manager interview · Technical screen · Team panel interviews · Executive calls, with the Orange Cloud Interview · OfferSee each roundHide
01
Initial conversation
A call with a recruiter

Cloudflare says you discuss your background, interests and the role. Ask which rounds your team runs, whether there is an AI-assisted round, and whether a take-home replaces the live screen.

02
Hiring manager interview
Reported as 30 minutes, by video

Candidates in 2025 and 2026 meet the hiring manager first, and one in Bangalore calls it an elimination round. A December 2025 candidate was asked why Cloudflare, which Cloudflare products they had used, about a recent project, production code, code review conflicts and how they debug when something goes wrong.

03
Technical screen
Live coding, reported in some loops

An April 2026 Austin candidate built a Battleship-style game live. A 2025 candidate solved a partition-packing problem. Other 2026 candidates went from the hiring manager straight to the panel.

04
Team panel interviews
Four to six interviews with your prospective manager and peers

Cloudflare says these focus on how you think and solve problems. Candidates report a debugging round (45 to 90 minutes), a system design (about an hour), a PM interview on working with product managers (45 minutes), an AI-assisted coding round (45 minutes) and a culture round (30 minutes).

05
Executive calls, with the Orange Cloud Interview
Senior leadership; reported as 15 to 45 minutes

Cloudflare's careers page puts the Orange Cloud Interview here. Several candidates sat their orange cloud or culture round inside the panel instead. A London candidate ended with a 15-minute call with a C-level executive. A Bangalore candidate's senior leadership round asked which AI coding tools they use and where those fall short.

06
Offer
Cloudflare's last step

Cloudflare says it moves quickly once it has found the right person. Every job ad says candidates who reach the offer stage may be asked to an in-person interview at a Cloudflare office or hub. One Austin candidate had an office tour; a London candidate had an office visit.

03

Cloudflare's debugging round and the other reported coding rounds

Reported problems and how to solve them

Cloudflare does not publish a coding test or a debugging round. Candidates report one in most 2026 loops. In London in August 2026 it was 45 minutes on an HTTP server with broken routing. In Bangalore in March 2026 it was 90 minutes of code review and debugging a slow distributed system. An Austin candidate in April 2026 calls it a debugging discussion, and a December 2025 candidate was told to expect an hour of pair coding on debugging and problem solving. Alongside it, 2026 loops add an AI-assisted coding round. Here are the reported exercises and how to approach each.

7 reported problemsSee them and how to solve themHide
  • Fix an HTTP server with broken routing: Run it and reproduce the failure with real requests before reading much code. Then read the router: check match order, trailing slashes, HTTP methods, path parameters and the fallback handler. Test one idea at a time, fix the smallest thing, and add a test for the broken route.
  • Review a code snippet and find the gaps: Read it as a reviewer would. Look for unchecked errors, missing timeouts, unbounded loops or memory, race conditions on shared state, and inputs that are trusted without checking. Say why each one matters in production and how you would fix it.
  • Debug a slow distributed system: Ask which requests are slow and since when. Check what changed. Follow one slow request through traces or logs to the hop that adds the time, then confirm the cause before you fix it.
  • Build features in an existing React and TypeScript app with AI: Learn the app's structure and API first. Give the assistant small tasks with context. Read every diff, run the app and test edge cases. The interviewer is watching how you check the AI's work as much as the result.
  • Fix bugs in an unfamiliar project with AI prompts: Reproduce each bug yourself first, then use the assistant to explain unfamiliar code and suggest fixes. Verify each suggestion by running it. Say out loud when you reject one and why.
  • Build a Battleship-style game: Agree the rules first: board size, ship placement, hits, misses, sinking and game over. Model the board and ships with simple classes, write the shot logic, then test a full game. Keep it readable and extendable, since follow-ups often add rules.
  • Find the minimum number of partitions for the used data: Add up the data used, sort the partition sizes from largest to smallest, and fill the largest first until all the data fits. It runs in O(n log n) time and O(1) extra space, which the 2025 candidate reached after a hint.

Practise debugging in a codebase you have never seen: clone a small open-source HTTP server, break something on purpose (or have a friend do it), and fix it against a 45-minute timer while talking. Then read Cloudflare's own postmortem of its 18 November 2025 outage. It starts with a wrong first guess, a large DDoS attack, and ends with a database permissions change. That is the shape of answer a debugging interviewer wants to hear.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Cloudflare.

Predict my Cloudflare questions →
04

Cloudflare system design interview: reported prompts

Reported prompts and how to take them

Every reported Cloudflare loop has a system design round of about an hour, and senior candidates may get two. The prompts lean toward Cloudflare's own world: edge data centres, logs, rate limits and HTTP. In the 2025 report the interviewer ruled out AWS and GCP and asked how each component would be hosted, and the candidate believes that round cost the offer. Plan to design on your own hardware.

4 reported promptsSee them and how to take themHide
  • Move logs from edge data centres to a core data centre and make them queryable: Buffer on disk at each edge site so an outage loses nothing. Batch, compress and send over TLS to a self-hosted queue such as Kafka in the core. Load into a columnar store such as ClickHouse, partitioned by time and encrypted at rest. Show how you hit a one-minute average and 15-minute maximum delay, and what happens when a site is cut off for an hour.
  • A distributed service that pings HTTP endpoints on a schedule: Store schedules in a database, sharded by job. Use a time-bucketed queue or a timing wheel so workers pick up jobs due in the next second. Make each ping idempotent, cap retries with backoff, spread load so thousands of jobs set for the top of the hour do not fire at once, and record results for users to see.
  • A batch pipeline that summarises support tickets with a third-party LLM: Ingest tickets into a queue, group them into batches, and call the LLM through a rate limiter that respects the provider's requests and tokens per minute. A token bucket shared across workers works well. Retry with backoff on 429s, store results with the ticket id so reruns are safe, and say how you would handle a provider outage.
  • An Instagram-like photo-sharing app for cats: Settle the core features: upload, feed, follow, like. Store images in object storage behind a CDN with resized versions, metadata in a database, and build feeds by fan-out on write for most users and on read for accounts with huge followings. At Cloudflare, expect questions on caching at the edge.

Revise the networking under every Cloudflare product before the round: DNS resolution, TLS handshakes, HTTP caching headers, anycast routing and what a CDN does on a cache miss. 52 of Cloudflare's 79 open software and systems ads name Rust, so if your design touches the proxy, it helps to know why a team would write it in a memory-safe systems language.

05

What Cloudflare screens for

Cloudflare names what the Orange Cloud Interview looks for only as "the behaviors we value." The same careers page lists three values (principled, curious, transparent) and six Capabilities. These are the six, in Cloudflare's words, and they are the best guide to the stories you should bring.

  • Be curious to learn and grow: approach every challenge with a desire to learn, ask questions and look for ways to improve
  • Communicate clearly and transparently: share information openly, give direct feedback and keep your team in the loop
  • Do the right thing: act with integrity, make principled decisions and hold yourself accountable
  • Embrace diversity: value different perspectives and experiences to make Cloudflare and its products better
  • Get your work across the finish line: take ownership, follow through on commitments and deliver results that matter
  • Lead with empathy: assume good intentions, support your teammates and create a welcoming environment
06

Cloudflare interview questions

Candidate-reported themes

The questions below come from candidate reports dated May 2025 to August 2026. No candidate has published the Orange Cloud questions word for word; a 2025 candidate calls them standard situational questions. The two Orange Cloud practice questions here are built from Cloudflare's own Capabilities, and each says so.

Rehearse these out loud for Cloudflare. Free to try.

See what's included →

Behavioural & motivation

  • Why do you want to work at Cloudflare?
    Cal

    I'm Cal, your AI coach. Say whatever comes to mind: I'll put your answer in order, show what's missing, then score it.

    Scored on Specificity · Connection · Research
    • Your answer is scored on
    • SpecificityNames at least two concrete things about this company or role that could not be copy-pasted to a competitor.
    • ConnectionTies those specifics to their own goals or experience, so it reads as fit rather than flattery.
    • ResearchShows they actually looked: a product, a technical choice, a public post. Generic praise for culture or mission does not count.
    See how a strong answer sounds

    Example · not your answer

    “You're the only team I've found that publishes incident reviews with the real timeline in them, and I've read four now. I've worked somewhere that treated postmortems as a ritual you get through, and I'd rather not do that again.”

    Strong. One row still open.

    • SpecificityOne, not twoThe incident reviews are the only specific here. The rest could be said to any company.
    • ConnectionJoined upTies the observation to how they want to work, not just to admiration.
    • ResearchLooked properlyRead four of them. That is looking, not skimming an About page.

    That comes back in about ten seconds, with what worked, what to fix, and what the question was really after.

    We never store your recording or your answer. How this is handled ↗

  • What experience do you have using Cloudflare's products?
  • How do you approach debugging when something goes wrong in production?
  • Have you done code reviews, and how do you resolve a conflict in review?
  • Tell me about a time you got your work across the finish line when it got hard.
  • Tell me about a time you had to share bad news or admit a mistake.
  • Tell me about working with a product manager when you disagreed.
  • Which AI coding tools do you use, and where do they fall short?

How to stop rambling in your answers

Technical

  • You are given a small HTTP server where some routes return the wrong handler or a 404. Find and fix the bug, talking through what you check.Debugging an HTTP server: A 45-minute round on a codebase for an HTTP server whose routing was broken; the candidate had to fix it and called it fairly easy (London, August 2026)Listening for: Reproduces first · Narrows with evidence · Fixes and proves it
  • A service in a distributed system has become slow for some requests. How do you find out why?Code review and distributed performance: A 90-minute round: review a code snippet to find gaps, then discuss how to debug performance issues in a distributed system (Bangalore, March 2026)Listening for: Measures first · Follows the request · Confirms the cause
  • You get an existing React and TypeScript app and an AI assistant. Add a feature in 15 minutes and show how you check what the AI wrote.AI-assisted coding: 45 minutes in a React and TypeScript app with an existing UI and API: build four features, with Google and AI tools allowed (London, August 2026); fixing bugs in an unfamiliar project using prompts (Austin, April 2026)Listening for: Reads the code · Directs the AI · Checks every change
  • Design a hit counter that returns the number of hits in the past five minutes.Live coding: Build a Battleship-style game (Austin, April 2026); design a hit counter, and find the minimum number of partitions that can hold the used data when data moves in chunks (2025)Listening for: A fitting structure · Edge cases · The follow-ups
  • Design a system that moves logs from edge data centres to a core data centre and lets users query them, without AWS or GCP.System design without the public cloud: Ship logs from edge data centres in NYC, LA and SEA to a core data centre and make them queryable, with an average delay of one minute, a maximum of 15, encryption at rest and in transit, and no AWS or GCP (2025); a distributed service that pings HTTP endpoints on a schedule (March 2026); an Instagram-like photo app for cats (August 2026)Listening for: The edge side · Self-hosted transport · Storage and query
Your Cloudflare interview

Don’t walk in hoping. Walk in rehearsed.

Calibrd predicts the questions Cloudflare is likely to ask for your role, interviews you out loud, and tells you what a hiring manager would hear.

Free · talk any answer through

Ready to go all in? for 90 days · or Unlimited graded answers and 45 mock interviews · no subscription ·
Built by Xiaochen Guo, 500+ interviews on the hiring side

How the questions are predicted

07

Pay

Software Engineer, San Francisco (posting)$157K–$216K base plus equity
Senior Software Engineer, Bay Area (postings)$194K–$266K base plus equity
Senior Software Engineer, New York or Washington (postings)$185K–$254K base plus equity
Staff/Principal Software Engineer, California or New York (posting)$220K–$303K base plus equity
Engineering Manager, New York or Washington DC (posting)$190K–$261K base plus equity
Senior Software Engineer, London (posting)£100K–£130K base plus equity
Senior Software Engineer, Portugal (postings)€66K–€91K base plus equity
Software engineer total pay, US median (Levels.fyi)$237,500

The posted figures are base salaries from Cloudflare's job ads on its Greenhouse board, read on 17 November 2026; every US ad says the role is eligible for Cloudflare's equity plan. Ranges change by city: a Software Engineer is $150K to $206K in New York or Washington DC, and a Principal Software Engineer on distributed systems is $230K to $288K in the Bay Area and $200K to $250K in Austin. Many Austin-only ads post no range. In Europe, a Senior Software Engineer in Germany posts €102K to €140K, software engineers in Portugal €54K to €75K, and a 2027 software engineering intern in Lisbon €2,450 a month. Levels.fyi's US figures include stock and bonus: medians run from $146,923 at L1 to $343,527 at L5 (updated 17 November 2026).

Applying to Cloudflare? Paste the posting and see whether they’d shortlist you →

Job alerts at Cloudflare. Not interviewing yet? Calibrd reads the open jobs at Cloudflare every morning and checks each new one against your resume the way a hiring manager would. Get job alerts at Cloudflare.

08

How to prepare for a Cloudflare interview

  1. Ask the recruiter which rounds your team runs. 2026 loops mix a debugging round, system design, a PM interview, an AI-assisted coding round and a culture round, and not every team runs all of them.
  2. Practise debugging code you did not write. Break a small open-source HTTP server on purpose and fix it in 45 minutes, reproducing the bug before you read the code.
  3. Prepare for an AI-assisted round. Practise adding a feature to an unfamiliar React and TypeScript app with an assistant, reading every diff before you accept it.
  4. Design without the public cloud. Be ready to say how you would host each part yourself, from the queue to the database, because a 2025 interviewer ruled out AWS and GCP.
  5. Write one story for each of Cloudflare's six Capabilities, and make sure at least one is about admitting a mistake. Transparency is one of its three values.
  6. Use a Cloudflare product before the hiring manager interview. A December 2025 candidate was asked which ones they had used, and the free tier of Workers or R2 is enough to have a real answer.
  7. Read two or three Cloudflare postmortems on its blog, starting with 18 November 2025. They show how Cloudflare engineers explain a wrong first guess, a root cause and a fix.
  8. Have a clear view on AI coding tools, including where they fail. A 2026 senior leadership round asked exactly that, and Cloudflare's ads ask for judgment on when to trust them.

This guide covers Cloudflare's engineering hiring: software and systems engineers, site reliability and security engineers, engineering managers and interns. Sales and solutions engineering roles run a different process. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Snowflake, G42 or Mercor? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Cloudflare mock: spoken answers, coached on the spot. Your first mock is free.

Run a Cloudflare mock →
09

FAQ & sources

What is Cloudflare's interview process?

The page gives no durations and no round list, so the formats come from candidate reports dated May 2025 to August 2026, and each row says which. The stages, in order: Initial conversation; Hiring manager interview; Technical screen; Team panel interviews; Executive calls, with the Orange Cloud Interview; Offer.

What does Cloudflare look for in candidates?

Cloudflare names what the Orange Cloud Interview looks for only as "the behaviors we value." The same careers page lists three values (principled, curious, transparent) and six Capabilities. Be curious to learn and grow; Communicate clearly and transparently; Do the right thing; Embrace diversity.

What questions does Cloudflare ask in interviews?

The questions below come from candidate reports dated May 2025 to August 2026. Technical themes: Debugging an HTTP server; Code review and distributed performance; AI-assisted coding; Live coding; System design without the public cloud.

What is the Cloudflare debugging interview?

Cloudflare does not publish a coding test or a debugging round. Candidates report one in most 2026 loops. Covered on this page: Fix an HTTP server with broken routing; Review a code snippet and find the gaps; Debug a slow distributed system; Build features in an existing React and TypeScript app with AI; Fix bugs in an unfamiliar project with AI prompts; Build a Battleship-style game; Find the minimum number of partitions for the used data.

What system design questions does Cloudflare ask?

Every reported Cloudflare loop has a system design round of about an hour, and senior candidates may get two. The prompts lean toward Cloudflare's own world: edge data centres, logs, rate limits and HTTP. Covered on this page: Move logs from edge data centres to a core data centre and make them queryable; A distributed service that pings HTTP endpoints on a schedule; A batch pipeline that summarises support tickets with a third-party LLM; An Instagram-like photo-sharing app for cats.

What is the Cloudflare Orange Cloud interview?

It is Cloudflare's values interview. The careers page says the executive calls include "our Orange Cloud Interview focused on the behaviors we value," and says no more. Candidates describe a behavioural round of about 30 minutes, and several sat it as part of the panel, before any executive call. Prepare stories for the six Capabilities on Cloudflare's careers page.

Does Cloudflare allow AI tools in interviews?

In the AI-assisted coding round, yes: an August 2026 London candidate says Google and AI tools were allowed, and an April 2026 Austin candidate used prompts to fix bugs. Cloudflare publishes no rule for its other rounds, so ask your recruiter before each one.

Is Cloudflare still hiring after the 2026 layoffs?

Yes. Cloudflare cut more than 1,100 jobs in May 2026, and its founders wrote that they don't want to do it again for the foreseeable future. On 17 November 2026 its job board listed 470 open roles, 79 of them software or systems engineers.

How much does Cloudflare pay?

Software Engineer, San Francisco (posting): $157K–$216K base plus equity; Senior Software Engineer, Bay Area (postings): $194K–$266K base plus equity; Senior Software Engineer, New York or Washington (postings): $185K–$254K base plus equity; Staff/Principal Software Engineer, California or New York (posting): $220K–$303K base plus equity. The posted figures are base salaries from Cloudflare's job ads on its Greenhouse board, read on 17 November 2026; every US ad says the role is eligible for Cloudflare's equity plan.

How do I get a job at Cloudflare?

On 17 November 2026 Cloudflare had 470 open roles on its Greenhouse board. 112 had engineering titles, and 79 of those were software or systems engineers. Hiring runs in 6 stages, starting with Initial conversation.

How do I get job alerts for Cloudflare jobs?

Calibrd reads the open jobs at Cloudflare every morning. Add Cloudflare to the companies you watch in Calibrd's Job search, with the role you're after, and each new job is checked against your CV: you see only the ones you could be shortlisted for. The first search runs as soon as you start it; after that a free account searches once a week, and with a pass the search runs every morning.

How do I prepare for a Cloudflare interview?

Ask the recruiter which rounds your team runs. 2026 loops mix a debugging round, system design, a PM interview, an AI-assisted coding round and a culture round, and not every team runs all of them. Practise debugging code you did not write. Break a small open-source HTTP server on purpose and fix it in 45 minutes, reproducing the bug before you read the code.

Prep for a real Cloudflare role

Practise your Cloudflare interview, out loud.

Paste a real Cloudflare posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your resume — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Cloudflare prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Cloudflare Interview: Orange Cloud, Debugging, Pay — Calibrd