Jobs · Information Technology · Texas

Senior Machine Learning Engineer

Cloudflare · Austin, TX · 1 mo ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Desirable Skills, Knowledge, And Experience (maybe "Qualifications" or "Skills"), Benefits? There's no explicit benefits, pay, schedule. There's "Available Locations: Austin, TX or London, UK (Hybrid)" - that's location info, maybe we can include as a short paragraph under About the role? The instruction: do not repeat job title as heading, do not put Job ID/requisition numbers as headings. We can include location info in a

. Also "What Makes Cloudflare Special?" is not a required section heading; we could include as a section maybe "About Cloudflare" but not required. The instruction: include a section ONLY when the posting has real, specific content for it. So we can have sections: About the role (we have that), Responsibilities, Desirable Skills, Knowledge, And Experience (maybe "Qualifications" or "Skills"), and maybe "About Cloudflare" (the "What Makes Cloudflare Special?" part). However the instruction says prefer a few substantive sections over many thin ones. The "What Makes Cloudflare Special?" is substantive but could be merged into About the role? Probably better to have a section "About Cloudflare" with that content. But the heading list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About Cloudflare. But we can still use other headings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings if appropriate, but better to stick to those. We have About the role, Responsibilities, and maybe Skills (Desirable Skills, Knowledge, And Experience). Could also include Qualifications (same as Skills). We'll make sections: About the role, Responsibilities, Skills. Also maybe "Location" as a paragraph. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO paragraph, the accommodation request, the export control note? That's maybe considered legal? It's about export control laws; might be considered boilerplate but it's substantive? It's a condition of employment. Might be considered legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The export control note is legal; likely remove. Also the "Please note that applicants who progress to the offer stage..." is application instructions? Might be considered boilerplate; remove. Also the "We’d love to hear from you!" etc is promotional; maybe keep? It's part of "What Makes Cloudflare Special?" but it's a call to action; could be considered application instruction? Might be okay to keep as part of About Cloudflare. But safer to keep the descriptive parts about projects (Galileo, Athenian, 1.1.1.1) and remove the "We’d love to hear from you!" and following sentences. We must preserve all substantive information: the mission, description of network, etc. The "About Us" paragraph includes mission, network description, etc. That's substantive; we should keep it. But where to put? Could be part of "About Cloudflare" section. However we don't have a heading for About Cloudflare in the list, but we could use "About the role" for role specifics, and maybe a preceding paragraph about company. The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can have a leading

for About Us description. Then headings for sections. Thus output:

About Us ...

then

About the role

... role description ...

then

Responsibilities

  • ... each responsibility ...
then

Skills

  • ... each desirable skill ...
maybe also include location as a

after About the role? Could embed location in About the role paragraph. We must not include sections like Benefits, Pay, Schedule because not present. We must not include filler like "commensurate with experience". Not present. We must not repeat job title. Let's extract content. About Us paragraph: "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. Available Locations: "Austin, TX or London, UK (Hybrid)" - we can include as a short

maybe after About Us. About The Role paragraph: "You’ll help define how machine learning models run across Cloudflare’s global network, from frontier open LLMs and real-time voice models to customer-deployed models served on heterogeneous GPUs and next-generation accelerators. You’ll work with systems engineers, product teams, hardware partners, and AI/ML engineers to bring models into production with low latency, strong reliability, and efficient resource use. This role combines applied ML, inference optimization, evaluation, and production engineering, with a focus on benchmarking models, improving serving performance, validating quality, and building tooling that helps Cloudflare and its customers ship AI applications at Internet scale." Responsibilities list: bullet points each starting with a verb. Desirable Skills, Knowledge, And Experience list: bullet points. Bonus Points: "Experience contributing to open source ML tooling, model serving frameworks, or inference runtimes." This is also desirable; we can include as part of Skills list. What Makes Cloudflare Special? includes several paragraphs about Galileo, Athenian Project, 1.1.1.1, privacy commitment. Also "We’d love to hear from you!" etc. We'll keep the descriptive parts about projects and privacy commitment, remove the call to action and maybe the "Please note that applicants..." etc. Thus we could add a section "About Cloudflare" with that content. But heading not in list; maybe we can incorporate into About Us? Actually About Us already describes mission etc. The "What Makes Cloudflare Special?" is more about specific projects; could be added as a separate section "About Cloudflare" or appended to About Us. Since we already have About Us describing mission, we could add a paragraph after About Us about these projects. That would be substantive. Thus final HTML:

About Us ...

Available Locations: Austin, TX or London, UK (Hybrid)

About the role

You’ll help define how machine learning models run across Cloudflare’s global network, ...

Responsibilities

  • Develop, optimize, and productionize machine learning models for Cloudflare’s serverless inference platform, with a focus on performance, reliability, and model quality.
  • Build benchmarking and evaluation frameworks to measure latency, throughput, cost efficiency, and model behavior across LLMs, speech, vision, and other model families.
  • Improve inference performance through quantization, batching, caching, model compilation, runtime tuning, and accelerator-aware optimization.
  • Partner with systems engineers to integrate models into Cloudflare’s distributed inference infrastructure across a heterogeneous fleet of GPUs and next-generation accelerators.
  • Drive improvements to model deployment workflows, including validation, rollout safety, observability, regression testing, and operational readiness.
  • Collaborate with product and engineering teams to translate customer requirements into scalable ML capabilities for Workers AI.
  • Mentor engineers, contribute to technical direction, and raise the quality bar for production ML engineering practices across the team.

Skills

  • Experience building, optimizing, and operating machine learning models in production environments.
  • Strong proficiency with Python and modern ML frameworks such as PyTorch, TensorFlow, JAX, or equivalent.
  • Hands-on experience with inference optimization techniques for large-scale models, including quantization, batching, caching, compilation, and serving runtime tuning.
  • Experience with large-scale inference serving frameworks or runtimes such as SGLang, vLLM, TensorRT-LLM, ONNX Runtime, Triton, llama.cpp, or similar.
  • Familiarity with LLMs, speech models, vision models, embeddings, multimodal models, retrieval-augmented generation, or other modern deep learning architectures.
  • Experience optimizing models for GPUs or specialized accelerators.
  • Strong understanding of production ML concerns, including evaluation, monitoring, model regressions, rollout safety, and reliability.
  • Ability to work across ML and systems boundaries, including familiarity with distributed systems, networking, or serverless platforms.
  • Track record of leading complex technical projects and mentoring other engineers.
  • Experience contributing to open source ML tooling, model serving frameworks, or inference runtimes.

What makes Cloudflare special: ...

We need to include the special projects description: "We’re not just a highly ambitious, large-scale technology company. We’re a highly ambitious, large-scale technology company with a soul. Fundamental to our mission to help build a better Internet is protecting the free and open Internet. Project Galileo: Since 2014, we've equipped more than 2,400 journalism and civil society organizations in 111 countries with powerful tools to defend themselves against attacks that would otherwise censor their work, technology already used by Cloudflare’s enterprise customers--at no cost. Athenian Project: In 2017, we created the Athenian Project to ensure that state and local governments have the highest level of protection and reliability for free, so that their constituents have access to election information and voter registration. Since the project, we've provided services to more than 425 local government election websites in 33 states. 1.1.1.1: We released 1.1.1.1 to help fix the foundation of the Internet by building a faster, more secure and privacy-centric public DNS resolver. This is available publicly for everyone to use - it is the first consumer-focused service Cloudflare has ever released. Here’s the deal - we don’t store client IP addresses never, ever. We will continue to abide by our privacy commitment and ensure that no user data is sold to advertisers or used to target consumers." We should keep that as a paragraph maybe under a heading "About Cloudflare" but we can just put as a

after Skills. We

Similar jobs