It's clear that Site Reliability Engineering has taken over the industry. We've gone well past the point where SRE is "that thing Google does", and now we have SRE principles being practiced in all corners of the industry, from the big enterprises to the small startups.

However, the Network Engineering discipline tends to view movements like SRE and DevOps as something that is not intended for them; they view them as something that is limited to the application space. There is a tremendous opportunity for this discipline to learn from the SRE movement, and use the principles that are proven in adjacent industries to make today's networks more reliable, and more responsive to the needs of developers.

A few organizations have begun adopting the title "Network Reliability Engineer" as a way of getting the core SRE tenets and principles into the world of network engineering. In this talk, we'll cover:

- Why network engineers in 2019 have a pretty tough job
- Why NRE exists (and why I think it's useful)
- How the SRE movement can help bring network engineers along for the ride