C

Cloudflare

Secures websites and runs apps on its network

Network Deployment Engineer

Full-TimeDeadline 11/1/26
$114k - $173k/yr+ Equity plan
Senior
Bachelor's
Austin, TX, USA+3 moreMore locations: New York, NY, USA | Denver, CO, USA | Atlanta, GA, USA
HybridHybrid work arrangement; limited travel required.
IT OperationsNetwork Engineering & Administration
Company Historically Provides H1B Sponsorship

About the job

Requirements
  • At least 5 years of hands-on experience in Data Center Operations, Network Engineering, Linux System Administration, Site Reliability Engineering, or DevOps.
  • In-depth knowledge of physical power and cooling, optics including CWDM/DWDM, cable standards, and remote lights-out management using IPMI/BMC.
  • Strong understanding of network protocols, topologies, and design, with experience troubleshooting physical and logical network connectivity.
  • Proficiency in writing Python or Bash scripts to automate operational tasks, and experience using or building agentic AI tools for workflow efficiency.
  • Hands-on experience with configuration management tools such as SaltStack, Ansible, Puppet, or Chef.
  • Proven capability to manage global vendors, anticipate blockers before execution, identify failure patterns, and write precise MOPs/SOPs.
  • Experience working in a 24/7/365 mission-critical service environment with an on-call rotation is required.
  • Knowledge of the OSI model and experience isolating network, hardware, and software issues.
Responsibilities
  • Provision, configure, monitor, and maintain physical hardware, networking devices, and software for greenfield deployments and brownfield migrations.
  • Perform remote server administration using IPMI/BMC out-of-band management tools for server provisioning, troubleshooting, and firmware updates.
  • Build scripts using Python and other tools to eliminate repetitive work, and leverage and develop agentic AI tools to reduce administrative overhead.
  • Direct remote hands and field contractors on rack-and-stack installations, optical cross-connects, cable management, and power and cooling requirements.
  • Provide technical leadership to remote contractors and junior team members during on-site deployments, guiding configurations and quality control.
  • Create and maintain standardized SOPs, MOPs, runbooks, and visibility metrics for operational consistency across global regions.
  • Partner with Infrastructure Planning, Site Reliability Engineering, and Network Engineering teams on global expansion projects.
Desired Qualifications
  • Bachelor’s degree in Computer Science, Engineering, or MIS, or equivalent practical experience.
  • Familiarity with network operating system platforms including Juniper Junos, Cisco IOS/NX-OS, Arista EOS, SONiC, Ciena, or Nokia/Infinera.
  • Knowledge of core internet routing, including BGP and Anycast, and load-balancing concepts such as Nginx and HAProxy.
  • Basic program-management experience using JIRA, Excel, or Google Sheets to track multi-region rollouts.
  • Multilingual capabilities and experience managing infrastructure across diverse international regions.
  • Linux certifications such as RHCSA/RHCE or programming experience in Go.
  • Professional-level network certifications such as JNCIP or CCNP, or higher.
  • Experience with continuous or rapid deployment.

About the company

Cloudflare operates a network that protects websites, delivers online content and runs applications closer to their users. Businesses connect websites and internal systems to its services to filter malicious traffic, control access and improve performance, with security and computing running on shared infrastructure. Developers combine application code, object storage and databases with the network used for content delivery and traffic protection. Cloudflare earns revenue from subscriptions and usage charges, with free plans for basic features and negotiated contracts for larger organizations. Cloudflare was founded in 2009 and is headquartered in San Francisco, California.

Company Size

1,001-5,000

Company Stage

IPO

Headquarters

San Francisco, California

Founded

2009

Get referred to Cloudflare

See people who can refer or advise you

Simplify Jobs

Simplify's Take

What believers are saying

  • Demand is growing: Cloudflare reported $696 million revenue, up 36%, for the June 2026 quarter.
  • New parents get paid bonding time: qualifying Cloudflare employees receive up to sixteen paid weeks globally.
  • Attack protection has predictable billing: Cloudflare provides unmetered DDoS mitigation across all plans, including its free tier.

What critics are saying

  • Employees faced a major workforce reduction: Cloudflare announced more than 1,100 global job cuts in May 2026.
  • One software fault spread widely: Cloudflare's bot-management configuration broke core network traffic in November 2025.
  • Free users still incur costs: most Cloudflare customers pay nothing, while the company bears incremental network expenses.

What makes Cloudflare unique

  • Services share network locations: Cloudflare runs its security and delivery stack in every data center.
  • R2 makes outbound bandwidth free: Cloudflare charges for storage and requests, without fees for direct Internet data transfers.
  • Workers handles deployment and scaling: developers publish apps across Cloudflare's global network without managing servers.

Help us improve and share your feedback! Did you find this helpful?

Benefits

  • Competitive salaries
  • Take-what-you-need paid vacation policy
  • Comprehensive health plans and benefits
  • Paid maternity and paternity leave
  • Commuter and ride share options
  • Returnships

Growth & Insights and Company News

Headcount

6 month growth

0%

1 year growth

0%

2 year growth

0%
MarketScreener
Oct 16th, 2026
Klaviyo: 85% of Klaviyo code is AI-generated. Here's what changes.

Klaviyo: 85% of Klaviyo code is AI-generated. Here's what changes. Published on 10/16/2026 at 11:33 am EDT On September 23, I joined Stephanie Cohen, Cloudflare's chief strategy officer, and Owen Jennings, Block's head of business, on a panel at The Information's AI Agenda Live in San Francisco. [...] Attachments * Original document * Permalink Disclaimer Klaviyo Inc. published this content on October 16, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on October 16, 2026 at 15:32 UTC. (C) Publicnow - 2026

OVFILE
Oct 16th, 2026
Cloudflare introduces evaluation system to hold verified bots accountable for website preferences.

Cloudflare introduces evaluation system to hold verified bots accountable for website preferences. 4 hrs ago - 16 October 2026 Lina Irawan OvFile Reporter Just as possessing a valid driver's license proves a person's identity and confirms they have passed a driving test, it does not guarantee they will operate a vehicle responsibly in the future. The same principle increasingly applies to the millions of automated software agents and bots navigating the modern internet. While verifying who operates a bot establishes fundamental accountability, true trust depends entirely on how that automated agent behaves once it gains access to digital infrastructure. A known, authenticated bot can still ignore explicitly stated website preferences, overwhelm origin servers, or attempt to evade traffic controls. Often, these infractions are not driven by malicious intent, but rather stem from misconfigurations, coding bugs, or poorly managed scraping parameters. To address these challenges, internet infrastructure and security giant Cloudflare has rolled out a new evaluation framework designed to measure and report when verified bot behavior deviates from acceptable operational standards. The initiative is intended to ensure that the fundamental question of whether an automated crawler can be trusted continues to receive a definitive affirmative answer. In the evolving landscape of web traffic, Cloudflare has long emphasized the importance of verifying two critical questions regarding automated agents: identity and trustworthiness. Through tools such as Web Bot Auth, bots sign requests to establish their verifiable identity, allowing systems like BotBase to catalogue them in an open, transparent format. However, once identification is firmly established, the security paradigm shifts toward a core operational rule for verified bots - the mandate to cause no harm to the digital properties they visit. The introduction of this evaluation system highlights the crucial distinction between baseline risk and earned trust. A prominent example of this distinction occurred when Cloudflare de-listed Perplexity's bot from its Verified Bot Directory after the crawler attempted to access resources on websites that had explicitly opted out of data scraping. Furthermore, when those initial requests were blocked, the bot attempted to circumvent the established website controls, prompting immediate administrative action. Do not engage in abusive behavior. While the requirement for automated crawlers to avoid abusive behavior may sound straightforward, managing it in practice involves a high degree of nuance. When automated agents fail to respect site preferences, they undermine the foundation of trust between content publishers and platform operators. If a website explicitly requests that a crawler refrain from indexing its content or demands that it reduce its request frequency, ignoring those directives erodes confidence in the automated system. To combat this, Cloudflare has developed a specialized measurement system designed to quantify how consistently a crawler respects publishing preferences. Rather than issuing a permanent judgment about a specific bot or its operator, these observations translate into an explainable trust band. This designated range demonstrates how consistently a bot complies with site preferences over time, highlighting the specific observed behaviors that informed the assessment. The initial signals evaluated by the system focus on common-sense rules and digital courtesies extended toward the website operators who provide the valuable information bots seek. Cloudflare plans to make these trust scores publicly available on its Radar platform while expanding the metrics used for evaluation. This scoring mechanism provides responsible bot operators with a tangible way to demonstrate that trust is being continuously upheld, reinforcing the security philosophy of verifying identity while continuously re-verifying behavior. When in rome, do as the romans do. For decades, the standard method for website owners to communicate their crawling preferences has been the robots.txt file. Cloudflare's new system carefully evaluates whether a bot's observed traffic patterns remain consistent with these published preferences over an extended period. A standard robots.txt file instructs all or specific bots on which sections of a website they are permitted to crawl. Because isolated violations or rare one-off anomalies might not reflect systemic issues, Cloudflare's system looks instead for repeated patterns of behavior that systematically disregard site preferences. The fundamental expectation is straightforward: responsible bots must consult and honor the preferences published by websites, aligning with established internet standards such as RFC 9309. Cloudflare notes that a robots.txt file establishes the baseline minimum rules for what automated agents should avoid, but it does not imply that any unmentioned activity is automatically permitted. For instance, a robots.txt file is not required to state explicitly that a bot must halt operations when a website communicates through other technical signals that continued access is unwelcome. What you do not wish for yourself, do not impose on others. Even when bots remain strictly within allowed URL paths, they can still place substantial computational loads on the websites they visit. One of the most common ways website operators push back against excessive traffic is by returning an HTTP 429 status code, which signals "Too Many Requests." This response serves as a direct instruction for the visitor to reduce its request rate, occasionally accompanied by guidance on how long to wait before attempting another connection. Cloudflare's evaluation system actively monitors whether a bot's traffic adapts appropriately after receiving this signal. The system assesses whether the crawler slows down or pauses its requests, or if it continues transmitting data at the same aggressive pace. This adaptive behavior is systematically incorporated into the bot's trust band over time. Consistently slowing down or pausing operations in response to rate-limiting signals increases the bot's trust score, whereas repeatedly ignoring the warnings lowers it. Building trust over time. Observing these behavioral signals represents an essential first step toward making automated traffic genuinely accountable. By pairing bot identity with verifiable evidence of ongoing behavior, Cloudflare aims to provide website owners with greater confidence that permitted bots are respecting their preferences. At the same time, it offers bot operators a reliable method to prove they deserve trust while supplying broader context regarding the automated traffic reaching digital properties. This evaluation infrastructure operates alongside existing tools such as Bot Preference Sync and Bot Management to form a comprehensive accountability loop for automated traffic. Bot Preference Sync assists website owners in publishing their preferences clearly, while traffic observation mechanisms verify whether trusted bots consistently honor those guidelines. Meanwhile, Bot Management empowers website administrators to decide how incoming automated traffic should be handled based on these evaluations. Cloudflare is already utilizing this system internally to assess how consistently verified bots honor website preferences. Because true trust is built gradually, the system evaluates sustained behavioral patterns rather than reacting to isolated incidents. This initial operational phase is being used to build historical data and refine how raw observations are translated into actionable guidance. Building upon this technological foundation, Cloudflare plans to extend the system to all customers, enabling them to customize the trust thresholds used to determine how verified bot traffic is handled on their networks. The overarching goal remains clear: to preserve the integrity of website preferences and ensure that trust is continuously earned through transparent and responsible behavior online. Related topics.

Tech Coffee House
Oct 15th, 2026
GoDaddy, Google and Cloudflare unveil AI agent trust system.

GoDaddy, Google and Cloudflare unveil AI agent trust system. techcoffeehouse GoDaddy, Infoblox, Google and Cloudflare have unveiled a system for verifying the identity of AI agents as they move through a transaction, developed in partnership with Singapore's Infocomm Media Development Authority (IMDA). Called the Chain of Trust, the open reference architecture was demonstrated at GovWare 2026 during Singapore International Cyber Week, and is built on principles from IMDA's Model AI Governance Framework for Agentic AI (v1.5). It lets organisations discover, identify and authenticate AI agents at every step of a transaction, even when the agents involved have never interacted before and run on different platforms. Agent-led commerce is growing fast. AI agents are already being used to search for products, compare prices and make purchases on behalf of people and businesses. McKinsey & Co estimates AI agents could facilitate between US$3 trillion and US$5 trillion in global consumer purchases by 2030. The problem, according to the companies behind the project, is that most platforms today verify agents through closed systems, leaving businesses with little visibility into how an agent's identity was checked or whether it can be trusted. The Chain of Trust addresses this by building on existing, open internet standards, including DNS, OAuth and the Model Context Protocol, so trust can be verified independently across clouds and platforms rather than inside a single vendor's walled garden. Live demo simulated a flight purchase between strangers. At GovWare, the four companies demonstrated a complete agentic purchase of a flight from Madrid to Singapore between agents that had never interacted before and ran on different platforms. The buyer agent ran on Amazon Web Services, the seller agent on Cloudflare Workers, and the mandate authority and verifier agent on Google. A person approved the purchase with a passkey, which triggered a signed Agent Payments Protocol (AP2) mandate setting what the buyer agent could purchase, from whom and up to what amount. The buyer agent found the seller through DNS-based discovery, checked its identity against a public log, and verified its trust score before completing the purchase. The demo also included attempts by a look-alike seller using forged credentials, which the system stopped before any transaction occurred. "Realising the potential of agentic AI will require trusted and interoperable foundations that can support responsible deployment at scale," said Lee Wan Sie, cluster director for AI governance and safety at IMDA. "Robust agent identity will be a key part of that." "We don't need to rebuild the internet for AI agents. By extending the open standards that have connected the internet for decades, we can give agents a verifiable identity that works across platforms," said Jared Sine, chief strategy and legal officer at GoDaddy. Wei Chen, executive vice president of regulatory strategy at Infoblox, said the project extends DNS and other established internet standards to agent discovery and identity verification, "helping create a system where businesses can independently verify who they're dealing with, without relying on a single platform to decide who can be trusted." Rao Surapaneni, vice president for Gemini Enterprise and Agent Governance Platform at Google Cloud AI, and Stephanie Cohen, chief strategy officer at Cloudflare, also took part in the demonstration. The companies have published a technical case study and invited domain registrars, identity providers, payment networks and cloud and AI platforms to adopt and extend the architecture. Share with your friends:

Avenews
Oct 15th, 2026
Cloudflare says Gateway Forward enters public beta.

Cloudflare says Gateway Forward enters public beta. Cloudflare says the beta lets customer-written code change web requests and responses, while separate data loss prevention checks launch to validate detections before enforcement. Cloudflare says it has opened a public beta of Gateway Forward, which sends selected web traffic to customer-written code, and launched separate custom validation functions for data loss prevention (DLP). In its October 15 announcement, the company describes two ways for security teams to add their own logic: changing requests and responses, or checking sensitive-data detections before deciding whether to enforce a policy.[1] Cloudflare Gateway already evaluates and enforces security rules on user traffic. Cloudflare Workers already runs customer-written code on the company's network. The integration connects those services, allowing teams to add traffic-processing logic without hosting a separate proxy - a server that handles web traffic on a user's behalf - Cloudflare says.[1] How Forward handles traffic. According to Cloudflare, Forward rules are evaluated only for traffic that HTTP policies have already allowed. HTTP is the protocol used for web requests and responses. The first matching Forward rule sends the request to its assigned Worker; subsequent Forward rules do not also process that request.[1] The Worker receives the request's full headers and body, Cloudflare says. Customer code can change either, send the request to the destination server, receive and change the response, and return it to the user. Gateway continues to manage connections, certificates and encryption, while the Worker handles the customer's processing logic.[1] Cloudflare proposes access-justification pages as one possible use: a Worker could pause a request to a sensitive destination, ask the user for a written reason and record that response. This is an example of what customers could build, not a reported deployment result.[1] Checking a detection before enforcement. Cloudflare says its DLP custom validation functions are available now, separately from the forthcoming Gateway Custom Functions. DLP tools look for sensitive data using patterns and other checks. A pattern match alone does not establish whether that particular data indicates theft or misuse, the company explains.[1] The new validation step runs after a DLP detection matches but before a policy-enforcement decision. Cloudflare says customers can use a Worker to check the detected data against their own authoritative records, then use the result to decide whether the DLP profile should match the traffic.[1] Charges, live-traffic risks and the next release. Traffic sent to Workers is billed as standard Worker requests, Cloudflare says. The integration supports Workers Free, Paid and Enterprise, but the free plan has execution-time and daily-request limits. Those limits matter as teams send more Gateway traffic to their code.[1] Cloudflare cautions that Forward code changes users' live requests and responses. The company says teams must target and design these Workers carefully to avoid harming the user's experience.[1] Cloudflare expects Gateway Custom Functions before the end of 2026. Unlike Forward's proxy processing, these functions will return a text, number or true-or-false value that Gateway can use in network or HTTP rule conditions. Cloudflare says each function will require default values and configurable fallback behavior for failures, timeouts or unexpected results, giving teams a defined response when their custom check cannot complete.[1] Sources. Follow AveNews on X Join the list for future editions.

Halla
Oct 15th, 2026
Block, Amazon, Synopsys and Cloudflare are rethinking how work gets done with AI.

Block, Amazon, Synopsys and Cloudflare are rethinking how work gets done with AI. 2 hours ago 21 Good morning. Block's leaders didn't want to sprinkle AI on top of existing work. "We thought about fundamentally refactoring how we operate as a company," Amrita Ahuja, Block's CFO and COO, said during a panel I moderated at the Fortune Most Powerful Women Summit on Tuesday in Santa Barbara, where she was joined by leaders from Synopsys, Cloudflare, and Amazon. Over the past few years, the fintech company has been consolidating and simplifying its processes and using AI in the business since early 2024. Earlier this year, Block, the parent company of Square and Cash App, cut its workforce by 40% and removed layers of management. "We fundamentally believe that in a world of AI, you absolutely need the human at the center," Ahuja said. You still need people in every function who are builders, goal-setters, and strategy deciders, she said. But you no longer need a person whose job is to pass information along or check work before it reaches the actual reviewer, she added. At Block, engineers improved their code review changes by 150% between the start of the year and midyear, and "even non-engineers have a 60% improvement," Ahuja said, adding that 15% of code changes are now almost fully automated - meaning "there's only a human in the loop at the end for the final decision," she said. Measuring the return is still evolving, though. Much of the industry is still weighing AI costs against personnel savings, she said. Block is working to refine a metric it calls "timed customer value," which would trace a code change to a feature, then to a customer interaction, and finally to value. For Synopsys, a company that develops software for designing and verifying semiconductors, CFO Shelagh Glaser said the cost side got real fast. AI spending "was pretty reasonable until it wasn't," she said, comparing employees' usage habits to snacks in the break room. Synopsys had to decide who gets premium tiers and who uses internal models. It also built its own metering system when some providers didn't offer one. The goal is to be "super intentional about where that investment is," with returns measured in customer outcomes, not just product releases. Cloudflare co-founder and President Michelle Zatlyn, whose company provides web infrastructure and cybersecurity services, said the company now hires "both employees and agents" and wants all of its roughly 5,000 people to be builders across the business. One standout was a finance director who made extensive use of agents and whom the CFO tapped to lead AI transformation for the finance team, Zatlyn said. Cloudflare also committed to hiring more than 1,000 interns in 2026, and they've helped teams become more AI-native, she said. "The important thing as a leader right now is to make sure that you're giving time and space and permission for your teams to learn," Heather Zorn, Amazon's VP of customer experience, products, and services said. The company is able to measure returns on investment in how employees use AI through measuring adoption first, then engagement, and then efficiency through outcomes like time saved, Zorn said. "You want to create something that wins for the customer, and then you have to find a way that it wins for the business as well," she said. Leaders also have to figure out how long they're willing to invest before seeing both wins, she added. Ahuja said she expects more companies to integrate AI agents into their organizational charts, with workers responsible for both training and deploying these agents. "Where things are headed - and I've already heard about a couple of companies doing this, so we're on the frontier - is you look at your work chart that your company publishes, and it will have not only humans, but agents," she said. "Those agents, not too dissimilar to humans, need to be developed over time." Leaderboard. Andrew Hodson was named CFO of PharmaCorp, effective Oct. 27. Hodson takes over from Terri Tatchell, who retires that day. She will stay on as a consultant for three months to help with the handover. Hodson was most recently head of finance at Marshall Land Systems. Before that, he was VP of finance at Vendasta Technologies, where he led the finance work on strategic acquisitions. He also spent six years at Deloitte Canada. Nathan Iles was appointed SVP of finance at Dauch Corporation, a supplier of driveline and metal-forming parts to the auto industry, effective Nov. 2. He will become CFO on Dec. 1, succeeding Christopher May. That same day, May will become EVP and chief administrative officer, keeping the IT organization and taking on executive oversight of HR. Iles brings more than 25 years of finance leadership, most recently as CFO of Standard Motor Products, an auto parts supplier. Before that, he was VP and CFO of UCI International Holdings. Big deal. Many finance teams are adopting AI faster than they can trust what it produces, according to OneStream's first Forward Finance Index, a survey of 1,300 CFOs and other senior finance leaders at mid-market and enterprise companies in the U.S., U.K. and France. Nearly three-quarters (74%) say AI is already cutting manual work in the close, reporting and reconciliation. Yet just 14% say their AI investments have delivered "enterprise value and decision impact." Data is a major obstacle: while 71% are confident their teams provide trusted data for decisions, only 40% describe their financial reporting data as fully transparent, meaning it can be traced, explained and validated. Four in 10 respondents say data quality problems regularly block or delay AI projects. Workforce readiness is another gap: just 15% have a fully embedded AI skills program, even though two-thirds believe failing to prepare their workforce will make their organization irrelevant within five years. Overall, only 6% of finance organizations qualify as leaders across all five areas measured by the index: AI strategy, data, workforce, operations and IT collaboration. More than half (52%) rank as "Followers." OneStream, which sells finance software, argues that leaders treat AI as a change in operating model rather than a series of pilots, grounded in trusted data and a workforce ready for AI. Going deeper. Nvidia CEO Jensen Huang says the AI industry shouldn't accept any cybersecurity incidents caused by the technology, Fortune's Jeremy Kahn and Beatrice Nolan report. "I'm willing to accept no incidents of cybersecurity. We should not accept any of them," Huang told Fortune in an interview in London. Huang argued that the incidents so far could all have been avoided with stronger containment and monitoring of AI agents. You can read more here. Overheard. "As business leaders, we're wired to chase speed, scale and efficiency. However, in our pursuit of bigger, better and faster, we shouldn't lose sight of a key element of lasting success: trust." - Kate Barton, CEO of Dentons law firm, writes in a Fortune opinion piece. * homepage * Fortune magazine * Block, Amazon, Synopsys and Cloudflare are rethinking how work gets done with AI.