Drimva

Cloudflare

Senior Customer Reliability Engineer

Hybrid +1 · Senior · Full-time · Posted Jun 24, 2026

Location
Hybrid
Austin, TX, United States
Experience
Minimum 5 years; at least 2 years in customer-facing environments.
Visa sponsorship
Any offer may be conditioned on authorization to receive software or technology controlled under U.S. export laws without sponsorship for an export license.

About the job

Own high-severity customer reliability incidents and build proactive diagnostics, monitoring, and automation with Product Engineering to prevent recurrence across Cloudflare’s services.

What you'll do

  • Lead complex customer incidents from diagnosis through confirmed resolution, including on-call shifts in a global rotation that includes weekends.
  • Build reliability monitoring, detection, diagnostic tooling, and automation to identify customer issues early and reduce incident response toil.
  • Partner with Product Engineering and customers on fixes, technical escalations, documentation, and reliability improvements.

What they ask for

  • At least 5 years of hands-on experience in SRE, escalation engineering, systems engineering, or comparable technical support/operations, including at least 2 years in customer-facing environments.
  • Strong networking and security foundation, including TCP/IP, DNS, HTTP/S, BGP, routing, firewalls, VPNs, and Zero Trust.
  • Proficiency in observability and diagnostic tools, scripting and automation with Bash or Python, and incident management and SLO/SLI practices.
  • Excellent technical communication and ability to own ambiguous, cross-layer problems and engage directly with enterprise customer engineering teams.

Nice to have

  • Experience applying AI/ML to production engineering or operational workflows.
  • Cloudflare platform experience, cloud networking, developer platform services, or chaos engineering.

Tools

Wireshark, tcpdump, Kibana, Elasticsearch, Grafana, Bash, Python, Kubernetes

AI focus

Build and use AI agents and tooling to pre-diagnose incidents, retrieve relevant logs and configuration, and propose root causes with cited evidence; measure and improve their impact on engineering speed.

Model-written summary · the original posting is authoritative

First seen Oct 23, 2026 · Last verified Nov 4, 2026 (UTC)