Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

Cloudflare interview research

Candidate accounts · 1 scoped account · 3 reported questions/topics

Snapshot: 1 October 2026 · Software/backend focus · No live fetching

Self-reported accounts, not employer-confirmed. Preserve the stated role, team and location; this sample does not establish company-wide patterns or question frequency.

Questions people reported

Named problems, reported variants and broad topics are different kinds of evidence. Related practice links are not proof that the exact problem was asked. Some prompts were withheld; we do not invent their details.

Topics in these accounts: Coding · System design · Behavioral

SWE; level/location unknown

Interview and publication dates not confirmed

Read the original candidate account

Scope and source limitations

Author mentions an August–September timeline without a year in the body. Search-indexed report belongs to October 2025; leave exact interview date unresolved. Preparation topics mentioned before the loop are not automatically asked questions.

  • Unnamed DSA exercise

    Coding · Reported topic

  • Map-oriented service and log ingestion

    System design · Reported topic

  • Product discussion and working culture

    Behavioral · Reported topic

Additional independent, matching role/level/region reports are needed before claiming recurring patterns.

A suggested 14-day preparation plan

Authored practice, not the company’s syllabus. This general track is an editorial starting point, not a pattern inferred from all these reports. Confirm the format with your recruiter and adapt it to your actual level.

Systems and infrastructure

Keep general DSA; add memory, scheduling, synchronization, I/O, networking and operational debugging based on the actual job description.

  • Days 1–2: language fundamentals and memory/object-lifetime exercises.
  • Days 3–4: BFS/DFS, heaps and bounded-memory data processing.
  • Days 5–6: threads, synchronization, deadlocks and failure tests.
  • Days 7–8: networking/I/O and a practical debugging exercise.
  • Days 9–10: design a queue or ingestion service with backpressure.
  • Days 11–14: production project deep dive and coding/design mocks.
Practise an original design exercise

Design a rate-limiting service at a request gateway.

This exercise is written for practice, not reported by a candidate. Define requirements, implement the smallest useful version, then test concurrency, retries and failure recovery where relevant.

Customize a timed role/level prep brief

The timed brief uses a narrower, date/level-filtered dataset. Broader accounts on this page are deliberately not substituted into those filters.

How this research was collected

Public candidate accounts, official guides and original editorial practice are kept separate. We did not copy paid question banks or scrape all of the internet. Cross-posts are not independent evidence; one source can describe more than one company. Unknown or index-only dates are not used to claim recency. Future expansion needs permitted fetching, deduplication and metadata review; this version remains a static snapshot.