9 ms·
> The most common job title seemed to be SRE (Site Reliability Engineer), although there was a long tail, and they don’t care much about job titles. Oh I like
by h2odragon 7y ago
> The most common job title seemed to be SRE (Site Reliability Engineer), although there was a long tail, and they don’t care much about job titles.
Oh I like that one. "I kept the pile of shit running and put the fires out before they were noticed" is too long to put on a business card, anyway. "Site Reliability Engineer" sounds almost tame.
- chucky_z 7y agoI've had to convince some folks that indeed, someone with the title of "system administrator," if they put more than one programming language on their resume, is probably "SRE," or "DevOps." I have the job title of SRE currently and could care less what the actual title is. I've got work to do, and I'm going to accomplish it in the best way possible given whatever constraints exist at that time.
- _vertigo 7y agoIt does matter - in my experience, the future job prospects of "System Administrator" are much worse than "SRE"/"DevOps". Switching my title from "System Administrator" to "SRE" within my last company resulted in a job family change and a 10% raise (I had to show I could code as well as a software engineer in order to make the switch). When I left that role, having "SRE" on my resume instead of "sysadmin" was (probably, I don't have any strong evidence for this) instrumental in getting responses when I applied to "Software Engineer" roles at selective companies. I think there is a bias against roles that don't code, and especially roles that sound outdated. A lot of larger companies and managers in those companies don't understand what DevOps is, what SRE means or anything like that. They just know Ops and Dev, and your previous job title is probably the strongest hint they have to work off when they categorize you. Getting lumped in with Ops is (probably) a big hit to your earnings potential and limits your future options if/when you decide to move.
- weberc2 7y ago> Switching my title from "System Administrator" to "SRE" within my last company resulted in a job family change and a 10% raise (I had to show I could code as well as a software engineer in order to make the switch). Perhaps we're in agreement, but this is critically important. When my company hires for DevOps, CloudOps, etc positions, we are innundated with applications from Ops/SysAdmin personas. We don't want people who will put out the fire and keep the system limping along--we want people that can't stand putting out fires _and who have the skill set_ to build systems that (1) aren't likely to catch fire and (2) are easy to troubleshoot/extinguish when they do. One way we're addressing the problem is to change titles from "DevOps" and "CloudOps" to "Cloud Engineer"--not sure yet how big of an impact that will have (if any at all), but it's worth a shot.
- dev_dull 7y agoIn that case, isn’t an excellent DevOps/sre engineer indistinguishable from an excellent software engineer? Why hold any distinction at all?
- BossingAround 7y agoFrom my experience, SRE is a person with developer mindset (and skillset, or the desire to have a developer skillset) who doesn't mind touching the infra. A SWE typically won't want to touch infra. That's my experience of course, YMMV.
- williamDafoe 7y agoSWEs who don't touch infra show up because universities today pump out a lot of book-smart real-world-dumb graduates.
- limograf 7y agoI don't think so. I have my areas of expertise and of course in a pinch I will pitch in and try to help any way I can, but I've always found my best work is done in a team with fairly well defined roles, a healthy respect for each others' specialisms, and an enthusiasm for short bursts of collab/pair coding and longer stretches of solo(ish) work. I have fond memories of the team that worked across three time zones so I would get up to a set of well-described problems that I would solve in the morning (so satisfying), then a nice stretch of feature building after lunch, then a burst of pair coding with my newly arisen colleague, then maybe finishing with writing up any roadblocks or requests for the next person. I got very used to identifying blockers that were out of my area and would be better solved by the domain expert, and also a LOT better at ticket writing. It was a really, really productive and rewarding workflow and one of the key points was not getting bogged down in stuff outside my areas. We also all really appreciated each other because we all experienced each other as magical elves giving answers to hard problems in exchange for answers for easy problems! ;)
- williamDafoe 7y agoSREs make 5-10% more than SWEs at Google.
- _vertigo 7y agoThat’s good to know, thanks for bringing that to my attention. Is it true that SREs are more likely to have oncall rotations at Google than SWEs? That is the impression I got from reading the Google SRE book - it talks about bringing SWEs into the oncall rotation when the SREs are swamped (i.e. more than 50% of their time is devoted to operational work) as a kind of pressure release mechanism to prevent the SREs from burning out or getting mired in endless toil. It makes it sound like outside of situations like that, SREs are doing most of the oncall work. If this is the case, perhaps the pay discrepancy is explained by the greater oncall duties and morale issues for SREs? It’s also worth mentioning that based on my reading of the Google SRE book, very few organizations approach operations like Google does. I personally think that Google has an enlightened approach to operations, but not all companies do. Basically, I think SRE is a good title to have, but sysadmin is not, and I encourage anyone early in their career to rebrand themselves ASAP.
- ahartmetz 7y ago> I personally think that Google has an enlightened approach to operations, but not all companies do Perhaps because the founders were doing operations (well) in the beginning, so they know a few things about it and its importance. They famously built a reliable system with about the cheapest possible hardware.
- extra_rice 7y agoAre SWEs at Google expected to firefight especially outside of normal work hours? This is one thing I imagine SREs are expected to be doing that regular SWEs aren't. I think this is also why they require strong development background for the role.
- commandersaki 7y agoI worked in Amazon which has a similar view to on-call to Google. Usually one person is on-call for the team for a cycle of every week or fortnight. There is also a "follow the sun" model wherein another team in has your nights covered. I do recall that SWEs also had the responsibility of being on-call, since teams are usually a mix of SWEs and SREs. Naturally a team with a high ops load was shit and made your life hell. After my time there, I vowed never to do on-call unless it was after hours and specifically for emergency response. My opinion is - if there's an issue during work hours, the leads or the entire team should be on it - and collectively fix it. Anyway, Google has written a bit about this in their SRE book: https://landing.google.com/sre/sre-book/chapters/being-on-call/ https://landing.google.com/sre/sre-book/chapters/being-on-ca...
- avip 7y agoIt doesn't matter now. It'll matter next time. Change your title to DevOps, SRE, or team lead. I also don't like titles, I'm sharing my experience with you.
- binwiederhier 7y agoThis comment made my day. I laughed out loud. Well done.
- Conan_Kudo 7y agoIt's funny because it's true! The amount of insanity is frustrating...
- nurettin 7y agoHow do they keep a pile of shit afloat, though? Do they build log monitors and trigger restarts when shit dies?
- tuco86 7y agoBasically, yes. We use Kubernetes and it has that shit built in. If the software is too crappy you will be forced to switch it off and do it manually, tho. And when you are not doing anything else anymore you will have succesfully tansitioned from software engineer to SRE.
- prepend 7y agoThe trick is to eat the right stuff so shit floats by itself.
- StevePerkins 7y agoThe name and job title churn in this space over the past five years is breathtaking, almost JavaScript-ian. I've been at my current company for 6 years now. When I first started, those guys were "Operations", and the job title was "Admin". We used Google App Engine, and they mostly clicked buttons in the GCP web console. One year in, they re-branded as "DevOps". They were all "DevOps Engineers". They wrote a lot of hacky Python scripts, using the "gcloud" utility, to manage our new Docker-based services on Google VM's. A year or two later, they decided to become "Platform Services". They changed their titles to "Platform Engineers". They saw us developers using Jenkins for our CI/CD pipeline, and decided to re-implement all of their Python scripts as Jenkins jobs. Earlier this year, they became "The SRE Group". They are "Site Reliability Engineers" now. We eliminated their Python scripts, by migrating our microservices to Kubernetes and using managed databases. So now they're back to clicking buttons in the Google Cloud Platform web console again.
- sevagh 7y agoYou speak of them with such disdain. Is that a common attitude in your company?
- TurboHaskal 7y agoI can understand such disdain. I am a software engineer currently working in a DevOps team (yes, team, you’ve heard it right). I’d say that 90% of DevOps engineers I’ve met don’t even know what a linked list is, and they themselves talk with disdain about developers. So much for DevOps philosophy.
- Aeolun 7y agoI wouldn’t mind so much if they at least knew what terraform was.
- goatinaboat 7y agoif they at least knew what terraform was Any real, experienced DevOps engineer will reply “a steaming pile of shit”.
- DonHopkins 7y ago"Computer Janitor"
- mieseratte 7y agoBased on my last hotel stay, that would be Computer Sanitation Engineer.
- DonHopkins 7y agoMaybe some day Amazon will make a VR interface to AWS, like Viscera Cleanup Detail: In Viscera Cleanup Detail, players are given the role of "Space-Station Janitors", tasked with cleaning and repairing facilities that have been the scene of bloody battles during an alien invasion or other form of disaster. Tasks include gathering and disposing of debris, including, dismembered bodies of aliens and humans, spent shell casings and broken glass, restocking of wall-mounted first-aid kits, repairing bullet holes in walls, and cleaning of blood splatter and soot marks from floors, walls and ceilings, as well as secondary bonus tasks. These include stacking items like crates and barrels in a designated stacking area, and filing disaster reports on the events and deaths that took place in a corresponding level. https://en.wikipedia.org/wiki/Viscera_Cleanup_Detail https://en.wikipedia.org/wiki/Viscera_Cleanup_Detail Writing for The A.V. Club, Chaz Evans called it a commentary on first-person shooters that focuses on the consequences of violence. https://games.avclub.com/seeing-without-crosshairs-a-survey-of-the-first-person-1798275698 https://games.avclub.com/seeing-without-crosshairs-a-survey-...