Full-Time

Software Engineer

Network Platforms

Cloudflare

Cloudflare

5,001-10,000 employees

CDN, cybersecurity, and serverless computing platform

No salary listed

Company Historically Provides H1B Sponsorship

Austin, TX, USA

Hybrid

Hybrid role; some on-site days in Austin, Texas required.

Category
Software Engineering (1)
Required Skills
Rust
Python
Go
C/C++
Linux/Unix

Get referred to Cloudflare

See people who can refer or advise you

Requirements
  • Systems-level programming experience in Go, Python, Rust, C, or C++
  • A solid grasp of BGP and internet routing
  • Relish opportunities to dive into new technologies, and a demonstrated ability to do so
  • Experience in implementing, deploying, and debugging mission-critical distributed systems
  • Strong collaboration and communication skills
  • Willingness to adopt and integrate AI tools and systems into your engineering workflow
Responsibilities
  • Build and extend various software systems that carry traffic on critical paths of Cloudflare's network: from the host server linux kernel, to the network hardware dataplane, to the physical interconnect at an adjacent network
  • Participate in all stages of the software development lifecycle, from designing and documenting systems, to writing code and automated tests, to planning, managing, and monitoring production software deployments
  • Collaborate with engineers across the company, from operations teams to the teams building customer-facing products, ensuring these capabilities match business needs
  • Operate under a Run What You Build model and participate in the on-call rotation as part of operational duties
Desired Qualifications
  • Familiarity vendor switching SDKs
  • Familiarity with SR-MPLS and sFlow, BGP-LS & PCE protocols
  • Experience writing packet-processing software (eg, eBPF at TC or XDP, DPDK)
  • Experience using AI-assisted development tools (e.g., code completion, codebase analysis, log/data exploration) in a professional setting
  • Experience participating in an on-call rotation

Preparing a concise company summary based on the provided Cloudflare description.

Company Size

5,001-10,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

  • August 6, 2026 revenue reached $696.1 million, up 36%, and guidance rose to $2.87 billion.
  • Cloudflare's August 2026 pay-per-crawl and pay-per-use tests can monetize publisher scarcity immediately.
  • August 20, 2026 optional OAuth scopes strengthen MCP and AI-agent security, selling into enterprise Zero Trust.

What critics are saying

  • AWS, Google, and Fastly bundle CDN and security, compressing Cloudflare's 2026 pricing power.
  • Blocking AI crawlers invites publisher backlash and retaliatory traffic shaping from Google and OpenAI by 2027.
  • Workers AI depends on NVIDIA GPUs and model partners; supply shocks or partner pullbacks hit margins.

What makes Cloudflare unique

  • Cloudflare's 330-city edge network and 20% website reach create unmatched traffic visibility.
  • August 14, 2026 MCP detection turns network telemetry into enforceable AI-agent governance.
  • Workers AI's August 14, 2026 1M-token context and managed GPU network deepen developer lock-in.

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

3%

1 year growth

2%

2 year growth

3%
4sysops
Aug 20th, 2026
Cloudflare OAuth now lets users reject unnecessary app permissions.

Cloudflare OAuth now lets users reject unnecessary app permissions. By IT News AI / Thu, Aug 20 2026 / Cloudflare has introduced optional OAuth scopes, allowing users to approve only the permissions an application needs for a specific task instead of accepting or rejecting the entire request. The change is especially useful for MCP servers and other AI agents that may request broad access but do not need every capability in each session. More control without a permission checklist. OAuth client owners can now mark configured scopes as required or optional. During authorization, users can deselect optional scopes, while required scopes remain part of the grant; applications that do not opt into the feature keep the existing consent behavior. Cloudflare is limiting the choice to scopes requested in the current authorization flow, rather than displaying every permission configured for the client. That keeps the consent screen focused on the operation the user is about to authorize. Permissions follow the current request. For example, a client configured with user-details.read, workers-scripts.write, workers-kv-storage.write, and zone.read could make the last two scopes optional. If all four are requested, users can decline the storage and zone permissions while still granting the required scopes. If a later flow requests only workers-scripts.write and zone.read, only those scopes are evaluated and displayed. Permissions omitted from that request are neither granted nor enforced, even if they remain configured on the OAuth client. Client configuration adds optional scopes. Developers specify optional permissions through the OAuth client configuration by adding an optional_scopes list alongside the normal scopes list. This lets a single client support broad integrations while still allowing users to narrow access at authorization time. The model is particularly relevant to MCP servers, which may advertise many operations to an AI assistant even though an individual user or workflow requires only a subset of them. Applications must handle partial grants. Access tokens now reflect the scopes the user actually approved. After exchanging an authorization code, applications must inspect the granted scope set instead of assuming that every requested permission was included. Agents and integrations that continue working with reduced permissions will provide a safer authorization experience. Cloudflare recommends requesting only task-relevant permissions and marking additional capabilities optional where appropriate. Broader role coverage is planned. Cloudflare says it will expand account- and zone-level roles across nearly all of its products in the coming weeks. The effort is intended to provide more granular API token roles, account membership controls, and OAuth scopes for securing workloads.

Byteiota
Aug 18th, 2026
DeepSeek V4 on Cloudflare Workers AI: 1M context window is live.

DeepSeek V4 on Cloudflare Workers AI: 1M context window is live. 2 hours ago 0 DeepSeek V4 Flash and Pro arrive on Workers AI with the first 1M-token context window on the platform On August 14, Cloudflare added DeepSeek V4 Pro and DeepSeek V4 Flash to Workers AI - both with a 1,048,576-token context window. That is the first time any model on Workers AI has shipped with a 1 million token context. If you have been routing long-context inference tasks out of your Workers to external APIs because the old ceiling broke your architecture, you no longer need to. What shipped. Two model IDs are live: @cf/deepseek-ai/deepseek-v4-pro-0813 and @cf/deepseek-ai/deepseek-v4-flash-0731. Both run on Cloudflare's managed GPU network and support the same three access paths: the Workers AI binding (env.AI.run, the REST API, and the OpenAI-compatible chat completions endpoint. Both also support thinking mode and function calling. Workers AI's previous context ceiling was 128K tokens on the best available models. V4 Flash and Pro represent an 8x jump minimum - and the official Cloudflare changelog confirms these are the first models on the platform to cross the 1M mark. That is not an incremental upgrade. It changes what you can fit into a single inference call. Flash vs Pro: pick Flash first. The two models are not equals, but the gap is narrower than the naming implies. Flash (284B total parameters, 13B active) outputs at 103.2 tokens per second and scores 47 on the Artificial Analysis Intelligence Index. Pro (1.6T total, 49B active) scores 52 - a 5-point gap. Pro also costs roughly 3.1x more per output token. In most production workloads, that 5-point intelligence difference does not show up. Use Flash as your default. Reserve Pro for workflows with 10+ tool call chains, multi-agent planning where the coordinator needs to track complex state, or explicitly hallucination-sensitive pipelines where the quality gap actually matters. Paying 3x for the Pro label on a straightforward RAG pipeline is a waste. How to wire it up. The Workers binding requires two things: add [ai] binding = "AI" to your wrangler.toml, then call the model in your handler. The Workers Wrangler setup guide covers the full configuration. export default {async fetch(request: Request, env: { AI: Ai}): Promise<Response> {const messages = [ { role: "user", content: "Your prompt here..."}]; const response = await env.AI.run( "@cf/deepseek-ai/deepseek-v4-flash-0731", {messages}); return Response.json(response);}}; For streaming, add stream: true to the options object and pipe the resulting ReadableStream directly to the response. If you are already using the OpenAI SDK elsewhere, you can point its baseURL at Cloudflare's OpenAI-compatible endpoint - no code rewrite required. The 1M token context is for input plus output combined. The maximum generated output is 384,000 tokens, but that output must fit within the same 1M window alongside your prompt. Feed in 800K tokens of context and your maximum output drops to roughly 248K tokens. This is not a surprise gotcha - it is how transformer architectures work - but it is worth planning around before you design a workflow that assumes 384K output tokens regardless of input size. Also worth noting: thinking mode tokens count against your context and your billing even when they are not surfaced to the user. If you enable reasoning mode for a simple classification task, you are burning tokens you did not need to burn. Pricing and access. Both models require either the Workers Paid plan or prepaid AI Gateway credits. The free tier gets nothing here. Standard Workers Paid billing gives you a 20-request-per-minute rate limit. If you route through AI Gateway using Unified Billing - which launched August 7, a week before these models dropped - the rate limit jumps to 50 RPM. Cloudflare passes through inference pricing at cost with no markup. The Unified Billing credits carry a 5% fee on purchase, but the per-token rates are identical to calling DeepSeek directly. The architecture unlock. Before V4, building a long-context agentic workflow on Workers meant one of two things: artificially chunk your context and accept worse results, or break out to an external API and accept egress costs and latency spikes. Neither is a clean solution. With V4, the coordinator-worker pattern becomes practical entirely within Workers AI. A single V4 Pro coordinator holds the full task plan in its 1M context, delegates subtasks to multiple V4 Flash workers for high-speed execution, and reviews combined output - without a single external inference call. The entire loop stays on Cloudflare's network. This is the change that matters. The 1M token number is headline material, but the real value is removing the architectural compromise that forced developers off the platform for long-context workloads. Check the Flash model docs and the Pro model docs for the full parameter reference. Start with Flash, measure whether the Pro intelligence gap matters for your specific pipeline, and keep the inference on the edge where it belongs. I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

ASCII
Aug 17th, 2026
Cloudflare adds MCP traffic detection and Portal controls.

Cloudflare adds MCP traffic detection and Portal controls. 1h ago DevOps Tl;dr. Cloudflare One now detects Model Context Protocol traffic, identifies shadow MCP servers, and enforces approved-path access through new Gateway policies and dashboards. Key points. * MCP-Protocol-Version header detection identifies MCP traffic on TLS-inspected requests without maintaining domain allowlists * New MCP traffic dashboard shows which servers are accessed, which users access them, and whether requests bypass Portals * Gateway Traffic Source selectors distinguish Portal-proxied MCP requests from direct device connections for policy enforcement * Server-side controls (WriteGuard pattern) can block unauthorized tool calls before execution; network layer catches shadow MCP on managed paths Why it matters. AI agents can execute thousands of tool calls at inhuman speed with nondeterministic decisions, creating security risks traditional permission models weren't designed for. These controls let security teams detect unauthorized MCP servers (shadow MCP), prevent Portal bypasses, and block dangerous tool invocations before they execute - critical for organizations deploying Claude, Cursor, and other AI clients with MCP server access.

Yahoo Finance
Aug 17th, 2026
Atlassian and Cloudflare defy SaaSpocalypse fears with strong earnings and $4.8B backlog growth

Atlassian and Cloudflare delivered strong earnings results, pushing back against fears of a "SaaSpocalypse" in enterprise software. Atlassian beat Wall Street forecasts with adjusted earnings per share of $1.87 versus expected $1.50. The company's Remaining Performance Obligations surged 44% year-over-year to $4.8 billion. Atlassian's CEO plans to personally purchase up to $250 million in company stock. Cloudflare reported second-quarter revenue of $696.1 million, up 36% year-over-year, beating expectations of $666 million. Management raised its full-year 2026 revenue guidance to $2.864 billion–$2.870 billion from $2.805 billion–$2.813 billion. The results counter recent disappointing performances from companies like Datadog, Figma, and HubSpot that had sparked concerns about shrinking corporate IT budgets.

Press Gazette
Aug 17th, 2026
Cloudflare says bot blocking is fuelling publisher AI deals.

Cloudflare says bot blocking is fuelling publisher AI deals. Chief strategy officer on scarcity leading to licensing deals, and move to "pay-per-use". Creating "reliable scarcity" by blocking companies from scraping content for AI uses is leading to more licensing revenue, according to internet hosting giant Cloudflare. Last year Cloudflare, which is used by 20% of websites worldwide, began to block AI crawlers by default for its customers unless they choose to allow them, for example because they have a content licensing deal or a clear value exchange such as Google search. Cloudflare said its technology would allow a "pay-per-crawl" model which allowed website owners to charge a fee to the AI crawlers they let in. Pay-per-crawl remains in closed beta testing with publishers across a range of content types taking part and sharing feedback. Cloudflare said it will now shift its default position to "pay-per-use", which is still at a very early stage, so publishers receive compensation if their content is surfaced in AI answers or otherwise directly creates value. It has also just launched an AI visibility dashboard which it says allows publishers to track how often their content is appearing in answers from the likes of ChatGPT and Claude. People Inc chief executive Neil Vogel told investors this month that the publisher is seeing "real momentum" in AI licensing and cited its ability to block scrapers using Cloudflare. "People are understanding the value of our content because we are able to restrict almost everybody from using our content using our Cloudflare blocking," Vogel said. "And they have to pay for it. And when people have to pay for it, it seems they're really coming to the table." Vogel said previously that People Inc was blocking "almost all AI crawlers other than OpenAI, where we have a deal, and Google where we can't block them because they use one crawler for search and AI". Cloudflare chief strategy officer Stephanie Cohen told Press Gazette People Inc is "not alone". She added: "We've seen lots of our customers use our tools so that they can create reliable scarcity for their content, and then negotiate better deals. And so that part of the ecosystem really seems to be moving." Cloudflare has cited the Financial Times, The Atlantic, Ziff Davis, Conde Nast and Associated Press as other publishers working with it to do deals with AI companies. But Cohen said this is not only for large publishers and noted local or other niche titles in areas like healthcare have information that AI wants and no-one else has. She said there are local news sites on Cloudflare's network seeing a "path to having more licensing revenue than having ad revenue". She cited the information power of Park Record, which covers the ski destination of Park City in Utah and is owned by Cloudflare co-founder Matthew Prince. "If you want to know what restaurant to go to on Main Street in Park City, Utah, there's only so many places you can go for that information, for that information to be accurate, and so it's kind of the quintessential thing that if you block it, AI needs to pay for it to get it, because users will be going on vacation and will want to know where to go..." Pay-per-crawl versus pay-per-use. Cloudflare began testing the new pay-per-use model with Ceramic.ai, where publishers can get paid every time their content appears in search results if they opt in, and You.com, which is letting agents pay on demand for individual pieces of premium content to be delivered in AI answers for enterprise users. Cohen said Cloudflare started with pay-per-crawl because it was the "easiest thing to measure: you know it happens". But she added: "Pay-per-use is a better signal of quality. If you're scraping something, that doesn't necessarily mean you're using it, so using it is a better signal of quality. Over time, however, I would expect that crawling and use converge. The chances that you're going to keep crawling something that you don't use are probably unlikely..." This will have the added advantage of helping to cut down on unnecessary crawling, Cohen continued. "Our data shows us that more than half the time, an AI crawler is accessing information they've already accessed, and it has not been updated since they last accessed it. That's wasteful from their perspective. It's wasteful from the site owner's perspective. It's wasteful from the world's perspective." Cohen said this is why Cloudflare has launched a research project with OpenAI to explore how content from participating websites can "help AI search engines discover and index relevant content on the open web more effectively". She said Cloudflare would check "if a site has been updated to basically tell them when it makes sense to crawl and when it doesn't make sense to crawl so they're only accessing information if it's been updated, which we think will save lots of trees and energy and and money". 'There are not random bots getting through' There are concerns in the industry that blocking the "polite" (meaning clearly identified) AI bots is not enough as scrapers often hide as humans, route between different browsers or come via residential networks, for example. Tollbit's latest State of the Bots report said: "Bots are shockingly effective at evading cybersecurity protections and paywalls; we observed them impersonate Google and others, rotate IP addresses, and appear to use residential proxies, hammering publishers with bot traffic." People Inc chief innovation officer Dr Jonathan Roberts wrote in the report that the publisher is blocking "tens of thousands of unique bad bots every day". He said "the most aggressive actors" go through each of these stages and are blocked at each one: they send a named crawler, then an anonymous one, then a crawler that spoofs Googlebot which is allowed, and then a crawler that attempts to look human by scrolling the page and executing code but fails at a human challenge. Finally, Roberts said: "They send multiple crawlers through residential internet connections and mobile devices. Because these home proxy networks use legitimate IP addresses they are extremely difficult to identify as being compromised by bad actors and therefore block. We are able to block some of this activity, but not all." Cohen said "most" Cloudflare publisher customers have moved to blocking AI bots by default and allowing only those with whom they have deals. "In those cases, there are not random bots getting through." Asked how Cloudflare can guarantee it is blocking everything unwanted, Cohen said: "We strongly believe that when a customer blocks using our tools, that the block works. And in the few cases where we've had problems, we've publicly talked about it because it is very rare." She cited Cloudflare's criticism of Perplexity last year which alleged: "Although Perplexity initially crawls from their declared user agent, when they are presented with a network block, they appear to obscure their crawling identity in an attempt to circumvent the website's preferences." Cohen added that Cloudflare is "continuing to improve" bot management product Precursor, which became widely available last month. It runs inside web browsers so it can monitor user sessions and make it harder for bad actors to fake human behaviour, ultimately stopping evasive bots. She explained: "There are certain signals that we would have only gotten at certain intervals on a website, meaning if you tried to log in, if you tried to pay for something... but now we're going to be doing more constant monitoring, and it just makes the bot management product much smarter." Cohen also said that because Cloudflare works with so many websites, "there are so many things we see that it's very difficult for people to evade a block". She did, however, warn that publishers may have "leaky buckets" without realising: for example, from syndicating their content to other websites. "It's not that if you block, the block doesn't work. The block works, and when it doesn't, we write about it all the time and publicly shamed people not behaving on the internet. But there are other places where you just have to look to see, like, is my content showing up in these other places, and how do I stop that from happening?" Cloudflare has said that from 15 September, mixed-purpose AI crawlers that combine search and training will be blocked by default on pages with adverts. This would include Googlebot, which indexes content for search as well as its AI products like AI Overviews, unless the tech company separates its crawlers before then as it has pledged to do so. Cohen said the reason for blocking mixed crawlers is that "we want to make sure that sites have the ability to be discoverable without giving their content away for free... when a company has three crawlers, for example, one for training, one for search, and one for agent or user, the site owner has more transparency around the intent, like why is the crawler coming to me, and has the ability to block or allow them at the network levels". The two-and-a-half month gap between announcing Cloudflare's intentions and implementing them, Cohen said, was because "the goal is not to block. The goal is to actually get to a place where a sustainable ecosystem can emerge." Email [email protected] to point out mistakes, provide story tips or send in a letter for publication on its "Letters Page" blog