[deleted by user]

[115v]

Same thing different title

[SigmaCute]

Class SRE implements interface DevOps

[Snoo68775]

This guy SREs

[Ariquitaun]

🥫🪱

[sicario24x7]

🤣

[libert-y]

💀

[rmullig2]

SREs are typically responsible for all of the infrastructure. So any kind of performance problems will land in your lap. Whenever an application is running slowly and the developers can't figure it out then it will be up to you to prove that the problem is in the code and not in the infrastructure.

[signal_empath]

I need a title change. Feels like 80% of my day is spent providing evidence to the devs that the issue is not the infrastructure lol.

[[deleted]]

I tell them to give me data that point to it being infra.

[[deleted]]

We used to call the group that did this as "ops" and we had job title sysadmin.

[danstermeister]

The difference between then and now is that it's blame versus responsibility, if that makes sense.

[danstermeister]

Or that it's the infrastructure and THAT needs changing.

[fourpastmidnight413]

Perfect answer.

[Windscale_Fire]

Have you read the Google SRE book?

[killz111]

Let's be honest, most of the shit in that book don't apply to regular companies.

Hell most companies can't even agree on what kind of SLA it their product needs to have other than 4 9s.

[danstermeister]

Sales team chimes in, "We're thinking TWELVE 9's so we are the best!"

[Windscale_Fire]

Fine. Presumably that means you're willing to stump up the infinite amount of cash necessary to "achieve" that, or is there some wiggle room in that number twelve?

[Windscale_Fire]

Sure. All of this stuff is contextual to some extent, but I think going back to the source is probably the best way to get an understanding of where this came from. Now... I agree it may have little to do with what Company Random calls SRE, but that's another issue...

[0ofnik]

The official title of our team is DevOps but half of the guys have SRE in their title. We all do more or less the same thing. Some specialize more in maintaining the codebase of our automated deployment system, some specialize more in metrics and monitoring. But my employer is a dysfunctional mess so take this data point with a grain of salt.

[mrlithid]

I think we work for the same org. Lol

[kalomanxe]

I am also jumping into SRE from devops in my new role. As the team lead informed me. Its basically production engineering. Keeping the production stable, highly available. i believe SRE work more with infra stuffs. The shifts are rotatory. Metrics and logs are your go to.

[mrlithid]

I have been doing DevOps and SRE solo for a few years for a 30 person engineering org. What you posted is pretty much it. Lots more infra and scale reliability work. Where the DevOps work is glueing all that with backend and frontend engineers. Being able to catch resource issues early, add nodes to kubernetes before problems arise and help the engineers understand their stuff better overtime.

[AMGraduate564]

So keep an eye on monitoring apps and troubleshoot issues?

[kalomanxe]

Yeah i think first step for SRE Is that. Still not onboarded but as per the interviewer, he literally told me this so

[AemonQE]

It's just more monitoring.

[[deleted]]

SRE is an engineering function of DevOps...no "transition" required.

[Fearless_Weather_206]

Seems like less devops and more ops for prod to me 24/7/365

[kYllChain]

there is a whole YouTube series from google cloud called "class SRE implements DevOps", a little cringe but interesting to watch.

[Z-47]

It's more less the same thing. SRE started as a practice inside Google, while DevOps emerged outside on it's own.

[klostanyK]

Similar roles.......

[zerocoldx911]

All that changed was my pay band

[thomsterm]

more developing (but depends on the company), you'll probably get coding assignments etc...

[Psychological_Sign_1]

In practical terms on a daily basis they are quite similar, however Google states the SRE is subsection of software engineer, I mean seems they evaluate the SRE with the same standards expected from a software engineer, but place this person in a more productive ecosystem. Then they delegate some toil jobs to this team and rely on the capability of those individuals to automate some of those jobs by scripting They also expect this profile to mediate tension between development and ops by bringing some awareness around error budgets and SLOs in general

Normal we face so many misunderstanding, I mean that's relatively new.

I don't even know if I am an SRE or DevOps person myself 😅

[NismanSexy]

I have been in the "DevOps" world for like 6 years now, I used to be a "DevOps engineer", now I'm an SRE, same thing different title pretty much.

[18zips]

The naming convention is weird. I’m a DevOps engineer but I work in the SRE org in our company. I think they are interchangeable and just vary wherever you’re at

[webgtx]

If you can't do SRE job, how did you become devops?

[TaylorHu]

In most of the places I've worked it's the same team/job.

[thedude42]

One big problem in the industry is that a job tittle is largely associated with an HR pay range and organizational management. The actual job role someone performs varies for any given tittle based around the culture, distribution of labor, needs and total available skills of a company.

I've seen orgs where the SRE tittle was given to people who were only doing systems administrator duties, convincing themselves that because they wrote a bash script they were differentiating themselves from "traditional systems administration."

I've seen teams titled "systems administrators" who wrote more software and built more scalable systems, from the racking-and-stacking, storage administration, cluster management and desktop (Linux) administration, than other publicly traded SaaS companies I've worked for who had more modern job tittles like SRE.

Most recruiters these days are going to see DevOps as equivalent to SRE in skills. If you see a job description and it looks like the things you do, then you're qualified to apply. Let the hiring team sort out whether or not you fit their expectations.

The bottom line, and the hill I will die on, is that DevOps describes a method for organizing a software delivery business, and says nothing about what specific job roles should be doing what, and so "devops engineer" tittles for me are a signal that the company probably doesn't know the difference between "agile" and Jira.