Own the full lifecycle of threat-intelligence and abuse-disruption systems on Cloudflare's Cloudforce One team

Cloudflare is hiring a Software Engineer for Cloudforce One, its threat operations and research team, to design, build, and run distributed data pipelines that expose threat intelligence (TTPs, IOCs) to analysts and customers while supporting legal/Trust & Safety response efforts. The role spans Go/TypeScript (with Rust, Kafka, Redis, Kubernetes, Terraform, Temporal, PostgreSQL) and expects 5+ years building large-scale distributed systems, plus comfort translating legal/security requirements into production software. Austin, US, hybrid, with on-call.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Full SDLC ownership of a distributed threat-intelligence or abuse-detection system
Data pipeline design for large-scale threat signal ingestion and analysis (TTPs, IOCs)
Go/TypeScript production experience; familiarity with Rust, Kafka, Kubernetes, Temporal, PostgreSQL
Translating legal/Trust & Safety requirements into technical design
On-call ownership and production monitoring/maintenance
Mentoring teammates and promoting well-tested, modular code practices

Common question themes

Walk through a distributed system or data pipeline you owned end to end

How would you design a pipeline to surface IOCs/TTPs to both analysts and customers

Describe translating an ambiguous legal or compliance requirement into a technical solution

Tell me about an on-call incident you resolved in a production service

How have you used AI-assisted development or agentic workflows in your engineering

How candidates describe it

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

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

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Cloudflare interviews