The way I see it is that SRE is closer to business logic and consulted in feature development concerns whereas devops is closer to the metal, and underlying operations.
SRE implements DevOps as part of our work. SRE also tends to imply a very Googlish approach to service reliability (a focus on SLI/SLOs, for example). You will often find us embedded in development teams.
DevOps as initially defined is a practice, not a role. Most companies who have "DevOps" engineer roles aren't actually practicing DevOps and have siloed off "operations" as a separate concern. DevOps in that context usually equates to "sysadmin + cloud" with little to no shift in culture or process.
The way I see it is that SRE is closer to business logic and consulted in feature development concerns whereas devops is closer to the metal, and underlying operations.
SRE implements DevOps as part of our work. SRE also tends to imply a very Googlish approach to service reliability (a focus on SLI/SLOs, for example). You will often find us embedded in development teams.
DevOps as initially defined is a practice, not a role. Most companies who have "DevOps" engineer roles aren't actually practicing DevOps and have siloed off "operations" as a separate concern. DevOps in that context usually equates to "sysadmin + cloud" with little to no shift in culture or process.
That is so true. DevOps is firstly culture, only then processes and tools π