Threat Intelligence Software Engineer, Cloudforce One
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract substantive content.
From posting:
- About Us: paragraph about Cloudflare mission, network, etc. Keep.
- About The Role: description of Cloudforce One, responsibilities, etc. Might be split: we have "About The Role" then later "Responsibilities". The "About The Role" includes description of team and role. Then "Responsibilities" bullet list.
- Responsibilities: list of duties (design, build, run, scale distributed tools; develop data pipelines; collaborate; improve system design; analyze, communicate, prioritize; ongoing monitoring; mentor). Also includes note about flexibility to be on-call.
- Desirable Skills, Knowledge, And Experience: list of skills/experience.
- Benefits: description of benefits (health & welfare, financial, time off, etc). Also "Equity" mention: "This role is eligible to participate in Cloudflare’s equity plan." Could be part of Benefits or separate? The rules: include Benefits section if posting actually states them. It does. So we can include Benefits with subpoints.
- Pay: Compensation N/A -> we should NOT create Pay section because it's N/A (placeholder). So omit.
- Schedule: Not specified; omit.
- Location: "Hybrid - Hybrid Work from anywhere" maybe we can include as a short paragraph? The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short
maybe under a heading? But we shouldn't create a heading for location unless it's a section like "Location". Not in allowed headings list. Probably we should drop it or include as a short paragraph at top? The instruction: "fold minor metadata into a short
or drop it." So we can include a
with location info.
- Technologies: list Kubernetes Terraform SQL etc. Might be considered minor metadata; could be included in a short
or maybe under Skills? But we already have Skills section; we could incorporate those technologies there. However the posting includes "Technologies KubernetesTerraformSQL" as a line. We could treat that as part of Skills or maybe as a short
. Since we already have a Skills section with list, we can incorporate those.
- Equity: mention "This role is eligible to participate in Cloudflare’s equity plan." Could be part of Benefits or separate. Since Benefits section already exists, we could add equity as a bullet under Benefits.
We must not include boilerplate like EEO, equal opportunity, accommodation, etc. Also remove duplicated lines, application instructions like "Ready to apply? Review the details above and continue to the employer's site to start your application." Also remove "← Back to job listings Full Time Remote friendly ..." etc.
We need to output only HTML fragment, no /, no markdown fences.
Structure:
Location: Hybrid - Hybrid Work from anywhere
maybe.
Then About Us
...
About The Role
...
Responsibilities
- ...
...
Skills
- ...
...
Benefits
- ...
...
We need to ensure we preserve all substantive information.
Let's extract About Us text:
"At Cloudflare, we are on a mission to help build a better Internet. Today the company runs one of the world’s largest networks that powers millions of websites and other Internet properties for customers ranging from individual bloggers to SMBs to Fortune 500 companies. Cloudflare protects and accelerates any Internet application online without adding hardware, installing software, or changing a line of code. Internet properties powered by Cloudflare all have web traffic routed through its intelligent global network, which gets smarter with every request. As a result, they see significant improvement in performance and a decrease in spam and other attacks. Cloudflare was named to Entrepreneur Magazine’s Top Company Cultures list and ranked among the World’s Most Innovative Companies by Fast Company. At Cloudflare, we’re not looking for people who wait for a polished roadmap; we’re looking for the builders who see the cracks in the Internet that everyone else has simply learned to live with. We value candidates who have the instinct to spot a "normalized" problem and the AI-native curiosity to create a solution using the latest tools. Our culture is built on iteration, leveraging AI to ship faster today to make it better tomorrow, while ensuring that every improvement, no matter how small, is shared across the team to lift everyone up. If you’re the type of person who values curiosity over bureaucracy, and that AI is a partner in solving tough problems to keep the Internet moving forward, you’ll fit right in."
That's substantive.
About The Role:
"Cloudforce One is Cloudflare’s threat operations and research team, responsible for identifying and disrupting cyber threats ranging from sophisticated cyber criminal activity to nation-state sponsored advanced persistent threats (APTs). Cloudforce One works in close partnership with external organizations and internal Cloudflare teams, continuously developing operational tradecraft and expanding ever-growing sources of threat intelligence to enable expedited threat hunting and remediation. Members of Cloudforce One are at the helm of leveraging an incredibly vast and varied set of data points that only one of the world’s largest global networks can provide. The team is able to analyze these unique data points, at massive scale and efficiency, synthesizing findings into actionable threat intelligence to better protect our customers. As a Software Engineer on this team, you will own the entire software development lifecycle—from design and architecture to deployment and monitoring—for systems that serve both threat disruption and legal response efforts. You will be responsible for translating complex legal and security requirements into robust, scalable, and high-performance applications that have a direct impact on making the internet better, safer, and more powerful every day."
That's substantive.
Responsibilities bullet list:
From posting:
"While the majority of our services are now written in Golang and TypeScript, you will also work with technologies such as Rust, Kafka, Redis, Kubernetes, Terraform, Temporal and PostgresSQL. We also pride ourselves in dogfooding our own products and services so you will be extensively working with Cloudflare’s developer platform as well. We are looking for great engineers regardless of experience with any of these specific technologies.This role may require flexibility to be on-call outside of standard working hours to address technical issues as needed.Design, build, run, and scale distributed tools and services that support both cyber threat disruption and platform abuse efforts.Develop critical data pipelines and services to collect, analyze, and expose threat intelligence data for Cloudforce One analysts and Cloudflare customers, helping to identify Tactics, Techniques, and Procedures (TTPs) and Indicators of Compromise (IOCs).Collaborate closely with Threat Intelligence, Trust & Safety, Legal, and Product teams to understand goals and translate complex technical requirements into elegant, scalable solutions.Improve system design and architecture to ensure stability, performance, and maintainability of both internal and customer-facing compliance and security services.Analyze, communicate, and help prioritize complex technical concepts across teams.Ongoing monitoring and maintenance of production services, including participation in on-call rotations.Mentor and guide other developers in the team, helping to build collective technical expertise and promote best practices for writing well-tested, modular, and reusable code."
We need to split into list items. Each sentence after the initial fluff could be a bullet. However we need to preserve all substantive info. We can create bullets for each responsibility:
- Design, build, run, and scale distributed tools and services that support both cyber threat disruption and platform abuse efforts.
- Develop critical data pipelines and services to collect, analyze, and expose threat intelligence data for Cloudforce One analysts and Cloudflare customers, helping to identify Tactics, Techniques, and Procedures (TTPs) and Indicators of Compromise (IOCs).
- Collaborate closely with Threat Intelligence, Trust & Safety, Legal, and Product teams to understand goals and translate complex technical requirements into elegant, scalable solutions.
- Improve system design and architecture to ensure stability, performance, and maintainability of both internal and customer-facing compliance and security services.
- Analyze, communicate, and help prioritize complex technical concepts across teams.
- Ongoing monitoring and maintenance of production services, including participation in on-call rotations.
- Mentor and guide other developers in the team, helping to build collective technical expertise and promote best practices for writing well-tested, modular, and reusable code.
- While the majority of our services are now written in Golang and TypeScript, you will also work with technologies such as Rust, Kafka, Redis, Kubernetes, Terraform, Temporal and PostgresSQL. We also pride ourselves in dogfooding our own products and services so you will be extensively working with Cloudflare’s developer platform as well. We are looking for great engineers regardless of experience with any of these specific technologies.
- This role may require flexibility to be on-call outside of standard working hours to address technical issues as needed.
We could combine the tech stack bullet and on-call note.
Now Skills section: "Desirable Skills, Knowledge, And Experience" list:
- Experience with AI-assisted development and agentic AI workflows
- At least 5 years of experience building large-scale software applications, preferably distributed systems
- At least 3 years of experience working with Threat Intelligence or in support of a Threat Intelligence platform
- Experience designing and integrating RESTful APIs and/or gRPC services
- Knowledge of SQL and common relational database systems such as PostgreSQL
- Prior experience writing production ready code in Go and/or Typescript
- Familiarity with Rust
- Excellent debugging and optimization skills
- Expertise in writing well tested code
- Interest in opportunities to be a technical mentor for teammates
- Bonus Points: Deep understanding of DNS, TLS/SSL and HTTP
- Expertise in web security issues and industry standards for access control
- Experience with Kafka
- Experience building web applications using React
- Experience with Kubernetes
- Experience with Redis
We need to preserve all. Could combine bonus points as regular bullets.
Now Benefits: The posting includes a long description:
"Benefits Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S. Health & Welfare Benefits Medical/Rx Insurance Dental Insurance Vision Insurance Flexible Spending Accounts Commuter Spending Accounts Fertility & Family Forming Benefits On-demand mental health support and Employee Assistance Program Global Travel Medical Insurance Financial Benefits Short and Long Term Disability Insurance Life & Accident Insurance 401(k) Retirement Savings Plan Employee Stock Participation Plan Time Off Flexible paid time off covering vacation and sick leave Leave programs, including parental, pregnancy health, medical, and bereavement leave"
Also "Equity This role is
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content. From posting: - About Us: paragraph about Cloudflare mission, network, etc. Keep. - About The Role: description of Cloudforce One, responsibilities, etc. Might be split: we have "About The Role" then later "Responsibilities". The "About The Role" includes description of team and role. Then "Responsibilities" bullet list. - Responsibilities: list of duties (design, build, run, scale distributed tools; develop data pipelines; collaborate; improve system design; analyze, communicate, prioritize; ongoing monitoring; mentor). Also includes note about flexibility to be on-call. - Desirable Skills, Knowledge, And Experience: list of skills/experience. - Benefits: description of benefits (health & welfare, financial, time off, etc). Also "Equity" mention: "This role is eligible to participate in Cloudflare’s equity plan." Could be part of Benefits or separate? The rules: include Benefits section if posting actually states them. It does. So we can include Benefits with subpoints. - Pay: Compensation N/A -> we should NOT create Pay section because it's N/A (placeholder). So omit. - Schedule: Not specified; omit. - Location: "Hybrid - Hybrid Work from anywhere" maybe we can include as a short paragraph? The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short
maybe under a heading? But we shouldn't create a heading for location unless it's a section like "Location". Not in allowed headings list. Probably we should drop it or include as a short paragraph at top? The instruction: "fold minor metadata into a short
or drop it." So we can include a
with location info. - Technologies: list Kubernetes Terraform SQL etc. Might be considered minor metadata; could be included in a short
or maybe under Skills? But we already have Skills section; we could incorporate those technologies there. However the posting includes "Technologies KubernetesTerraformSQL" as a line. We could treat that as part of Skills or maybe as a short
. Since we already have a Skills section with list, we can incorporate those. - Equity: mention "This role is eligible to participate in Cloudflare’s equity plan." Could be part of Benefits or separate. Since Benefits section already exists, we could add equity as a bullet under Benefits. We must not include boilerplate like EEO, equal opportunity, accommodation, etc. Also remove duplicated lines, application instructions like "Ready to apply? Review the details above and continue to the employer's site to start your application." Also remove "← Back to job listings Full Time Remote friendly ..." etc. We need to output only HTML fragment, no /, no markdown fences. Structure:
Location: Hybrid - Hybrid Work from anywhere
maybe. ThenAbout Us
...
About The Role
...
Responsibilities
- ... ...
Skills
- ... ...
Benefits
- ... ...