A list of puns related to "Sre"
Background: About to be out of a job I've only been at for five months. Just changed my LinkedIn to be visible to recruiters as open to work on Monday. Been getting 10 recruiter emails/calls per day or so and not even exaggerating. Already almost reached the offer stage at one place where deadlines and sprints aren't a thing (medium/large-ish consulting business that primarily does resales) and should have something by Friday if I want it. I'm not trying to brag or anything, I only have 5 years or so of experience and no college degree, and my most recent gig is a total shitshow, but this is absolutely wild. Are companies really that desperate for SRE's right now?
you still have to work just know its another option if you like coding but hate the leetcode grind. also it makes applying slightly less competitive. if you like leetcode stick to it, I'm not arguing against it if you're fine with it. Also some companies(i.e. Google) pay security engineers more than swes. On average the salary will be the same though.
personally the issue i have with leetcode is it doesn't resemble the work or concepts used during the internship and interviewers prefer when i give memorized answers rather than my own solutions. also it is time consuming to learn something tangential to work at the company and then forget it to have to review it again every time you want to change companies.
source: this is how i got many offers.
I've been working in tech for almost 20 years, I'm 37. I'm self taught and did not go to college.
I started as a minimum wage tech support rep, became sr. tech support, been an I.T. admin, linux sysadmin, SRE and Sr. SRE and now working at one of the biggest tech companies making 250k in total comp.
I'm very fortunate in having gainful employment at a high compensation level (relatively speaking), considering my lack of formal education and meandering path I've made through life (I had terrible drinking problem until age 25, sober 12 years now, and I was an aspiring semi-pro musician throughout my 20s, not always working).
Right now though, I'm extremely discouraged and frankly kind of annoyed.
I've just done several full-length job interviews for SRE roles at companies that I think are cool (well funded startups), and keep getting told the same thing, which is essentially:
"What we really need is an SWE who has the title of SRE".
I feel like I've shot myself in the foot a few times mentioning that I consider myself to be a Devops/SRE professional and not a SWE in these interviews (after all, that IS the job I am applying for right?) to one person that then raises this as a red flag during the interview debrief or something.
I do write code. It's just not the main thing I do, and my SWE colleagues are admittedly much better at it than I am, because that is what they spend all their work time doing. But I am much better at pulling everything together (IaC, pipelines, observability) and making sure it's running in a sane , scalable, and repeatable way.
Perhaps my experience is not representative of the overall market. I feel like there is or was a time not long ago when SRE was fetching more $ than SWE because the breadth of knowledge required. I'm just not finding this to be the case, if you want to be an SRE it doesn't matter if you have years and years of UNIX/Linux, networking, ops etc, background, maybe you are better off just having a CS degree and 1 year of experience, and "knowing" kubernetes.
/rant
I came across this article and I wanted to get a feeling on whether or not people agree with this statement, made by Itiel Shwartz of Komodor. I'm fairly new in my Devops journey so I would appreciate some discussion to learn from.
Source: https://vmblog.com/archive/2021/12/13/komodor-2022-predictions-sre-tools-will-start-speaking-the-language-of-developers.aspx#.YdxWBBNBz0q
Something like Ico or Shadow of the Colossus is a good example, but also stuff like Alba or A Short Hike.
EDIT: both minimal mechanics or minimal input are fine.
Questions for the various SRE Managers and directors how do you measure your team? What are some of the KPIs you are using to measure the team against? (not specifically SLOs) But rather, what are some of the team KPIs, like MTTA or MTTR.
I'm a mid-level dude who landed my first "real" site reliability engineer job last year. Before that I've been working at couple of small companies. I feel quite competent with my technical skills (definitely not at English). However, I don't feel comfortable at all at my new job or at least how to handle it. I feel like I'm definitely missing out something in my career. Overall, everything just doesn't feel right. I believe I definitely need mentorship at this point in my career. Not a complete noob, but not enough experienced to move to the senior level. I have a few questions for you.
Do you have a mentor? How did you find your mentor?
Does anyone have experience with online paid mentorship sites? I'm seriously considering this path if all else fails. Names like mentorcruise, codementor showed up in the results. How was it?
And lastly if anyone is interested to have a mentee, please DM me.
If you made it this far, thank you and have a nice day.
I have somewhat recently started a new job where many of the developers refer to me as an "ops" person. I'm not entirely sure why, but this has started to bug me since the term "engineer" always refers to the developers, and I have a clearly separate distinction as "ops". I think what bugs me about it is the fact that in order to be an SRE, I need to have software engineering skills, as well as infrastructure knowledge to be successful in the role. So I'm not sure why there's a distinction?
Do any of you have this experience? Does the "engineer" in SRE mean something more than "ops" person to you?
I've become a junior SRE to a mid level SRE over the last year with no experience - mature career changer. To be honest, I've been in a testing team under the umbrella of SRE. I have a great team of people but I'm unfulfilled in my role and left on my own to do more analysis than technical work. I've been learning, practicing and working with java abit. However I have been given minimal work to be fulfilled.
I am deciding whether to move from my current team to anothe rSRE team in the department to have more exposure to SRE fundamentals.
However, I have been given the opportunity to develop my skills of a developer in java in another deparment where I am given the opportunity to pair programme and work more in an agile way. Also, exposure to other agile roles. I'm hoping to do a degree at some point in the year in Software Engineering, offered by the company.
Part of me is to take this opportunity in the new department but I heard to.be promoted its hard to achiev in the new department. I don't want to be stagnant. Secondly, I'm questioning if I gave SRE a chance and its more pay in this arena.- a lot of people are wanting to come in this area. Also, I do loads of work in my current department outside my role and built a good reputation. I feel like I'm going to start over a again. But I am acting too loyal.
Anyway, I was admant on leaving for the dev role as it can open more doors. Now I'm having second thoughts as I'm a career changer, have a family and need to think through my decisions. Any advice would be appreciated.
Recently interviewed and received an offer for an Site Reliability Engineer position for a global retailer. Overall the position pays very well, offers WFH, and is a well-rated place to work. However, after the two interviews I had didnβt give me a clear idea of what the role actually entails. Even after direct questions to the hiring manager over on-call, team composition, any big goals or expectations for success, he couldnβt articulate what exactly any of it was. The best I could get was We will work together initially to define what it meansβ.
I can partly chalk this up to the fact that this is one of the first SRE roles they would have for this area of the business (Front of House operations for brick-and-mortar retail stores ), but part of me wonders if they even know what an SRE should do.
My general impression is that SRE has been one of those buzzwords to really gain traction over the last few years that has little to do with the intended purpose as laid out by the Googles and Netflixs of the world and instead becomes a catch-all for an βadvanced generalistβ who can, well I donβt know, make things more βreliableβ. Thatβs not to demean SREs or the practice, just that business leaders give very little regard to what it actually means and have started their own Iβll-conceived SRE programs in short order. This could mean rebranding current ops as SREs, bringing in new folks with SRE experience,
Should I run for cover or take it anyway? From a pay and benefits perspective itβs fantastic but I literally have no idea what is expected. Itβs either a chance to build something from the ground up or spin tires until I leave.
I start my new job as a Sr Cloud Ops Engineer next month. Right now I am a SRE with 5 years of experience in AWS, IAC, serverless, Jenkins, etc. To my understanding the new job will be working with app teams on diagnosing their cloud environments and CI/CD pipelines. Feeling under prepared for the new job and am quite frankly nervous as this is a big jump in my career. Does anyone have any tips for somebody transitioning to a senior operations role?
So I am currently a Go backend engineer at a consultancy which I'm not finding interesting or in any way challenging, was originally looking into moving into trading at a private market making firm, but a friend who's also a recruiter at this firm signposted me to SRE as a role that I may be more interested in, this is the first I'd ever really heard of SRE or considered it.
Just trying to learn more about what SREs do, how challenging and interesting the work is, and where to do some homework on it and get taste of what the role is like + whether it would suit my skills.
Thanks for any help guys :)
Hi everyone,
Iβm sure this gets asked a fair bit however I have found a few posts related to this but wanted to get some advice on how to proceed.
I currently work as a DevOps (Mainly Ops) engineer and donβt have much experience programming.
My aim is to become more proficient in:
My aim is to switch to a more SRE focused role however having spoken to some companies and bombed some interviews, itβs clear I need to work in this area.
I also would like to aim for top organisations, So if anyone could recommend Go courses for data structures/algorithms/Leetcode that would be appreciated.
I have a weird style of learning, where I benefit best from doing tutorials and then doing it so, more hands on recommendations would be appreciated.
I am wanting to learn this over the next 6-9 months with around 10 hours dedication a week. Is that suitable? Or am I being unrealistic.
figured iβd mix it up a bit with this one. sre has been hot for a few years now, and while it only continues to grow hotter still, iβve come across a few of us that are trying to retire early or find new disciplines to work within.
the 2 biggest, most obvious choices are:
but i wanted to poll and see (a) if those make sense, and (b) what others might be available for a transition from sre.
TL;DR: I'm sick if not being around people who think like me. I'd like to meet you, folks.
Anyone attending conferences (in-person or online) in 2022?
I'm interested in attending SREcon put on by USENIX.
Welcome to this weekβs Feedback Thread!
Hi guys,
Long story short, I had intially started learning linux and had made a whole plan on getting into cloud (see previous posts). But recently was offered a free js fullstack bootcamp with an awesome community & network opportunities.
Should I abondon the goal of being an SRE and go towards full stack? What would you do?
This person oversees projects and delegates work to the members of DevOps/SRE/AppSupport (sometimes SysAdmin) while also having their own projects and system responsibilities. This person is the direct contact for any technical information and mentors new hires. This person deals with developers directly as well as the developer managers depending on the context. This person also gets involved with uncommon faults where troubleshooting requires a specific reach and knowledge. This person owns incidents and is the lead DR contact. There are multiple other responsibilities across the mentioned disciplines.
My company has this person, but we are unsure what this person's role is called. Titles are not something we get stuck on, however, no-one wants 'this person' on their email signatures. We're interested in finding a descriptive title for this role and I thought I'd ask around.
I'm not talking about technical skills or what you need to know to be a DevOps Engineer. I mean what other traits and characteristics make someone a good DevOps Engineer?
For example you have two people that are both exactly the same technical level. What are some soft skills or character traits etc. that might make one better than the other?
Hi, time flies. 10 years ago, I worked on Solaris, Linux Red-Hat, VMWare ESX systems, NetApp WORMS Disk Arrays, Sun Arrays... so many systems in different companies. When I started my company 2 years ago, I was impressed by the emergence of the cloud. I was old-fashioned and thought that the cloud was just a new "toy". Things changed, and I believe in the power of the cloud. Being able to think at a higher level of abstraction is super convenient and help to build new kind of applications. With Qovery, we create a higher level of abstraction that turns AWS a breeze to build on top for anyone - even non-experienced developers. For instance, here is what you can do with Terraform and our provider to deploy an app and a Postgres database:
resource "qovery_project" "my project" {
cluster = "prod-cluster"
environments {
"prod-env" = {
name = "prod"
mode = "production"
applications = {
"my-backend-app" = {
name = "backend"
git_url = "https://github.com/evoxmusic/ShortMe-URL-Shortener"
branch = "master"
build_mode = "dockerfile"
dockerfile_path = "/Dockerfile"
cpu = 1
ram_in_gb = 0.25
min_instances = 1
max_instances = 1
ports = {
"http" = {
protocol = "web-api"
local_port = 5555
exposed_port = 443
}
}
environment_variables = {
"key" = "value"
}
}
}
databases = {
"my-psql-db" = {
name = "psql"
type = "postgresql"
version = "13"
mode = "managed"
cpu = 1
ram_in_gb = 1
}
}
}
}
}
My team and I believe have open-sourced our deployment engine written in Rust (such a lovely language that I encourage you to take a look).
I have one question for you. As an SRE in 2022, what are you looking for today? What are the tools you are using and excited about?
Hi there!
I recently started as an intern for the SRE position and I've been learning about kubernetes, kustomize, argocd, yaml, etc. I had used kubernetes in some personal projects before and that previous knowledge has been useful.
I now have to propose a project that I intent to work on for the next 5 months. But, in all honesty, I cannot think of anything. They are a pretty huge company, and I want to be able to add as much value as possible through my project.
So, with these things in mind, if you had to propose a project, what would it be?
Thanks!
Weβve had some threads about interviewing challenges, and some threads about general SRE day-to-day stressors, I wanted to combine the two and bring up a topic I donβt think gets brought up enough: when to walk away from an interview, for reasons beyond salary.
Salary is the easy one to walk away from, assuming youβre in the financial position to do so. So this thread assumes an ideal state.
I have a few things that make me say βthanks, no thanksβ, one interview this summer went really well, the people I talked to were very polite and sharp in terms of what they were working on, but the environment was pure chaos and disorder, when the manager admitted βweβre basically ticket takersβ I politely bowed out.
Lately Iβve been thinking of asking βhas anyone in your Engineering leadership or SRE leadership teams read the Google SRE book?β early on in the interview as a way of maybe raising an orange flag (escalate to red depending on other conditions) to start asking them slightly harder questions.
Anyone else want to share experiences when they chose to depart an interview/reject a company?
I recently moved jobs to a place where I do SRE, 50% spent writing code and embedding into multiples the rest is writing integrations and capacity planning.
After a 10 months, I realized that I hate coding professionally. Trying to maintain other people's code and writing tests to cover edge cases is just draining. I used to just write tools and utilities with a specific purpose to automate a tedious task which I found very enjoyable, it clearly didn't translate to coding.
I'm just eyeing returning to do infrastructure work and automation by changing jobs yet again, does anyone else feel the same way?
For those that went SRE to Dev why did you guys switch, I recently started coding more for personal projects and slowly am falling in love with software development, particularly building web APIs. How are you guys like the dev life now after doing SRE for a few years. I think SRE pays more than development, but I could be wrong
Hi guys,
I'm about to join the SRE team that has just been created in my company. There's the CTO, 1 guy who did it for 3 months for 50% of his work time and me. Basically, me and the guy are going to build the team, procedures and all of that.
I'd like to use my programming skills (university+my own time) to develop monitoring tools that could help us.
We're using Linux servers and the system is in Java. Are there any Python frameworks that you guys recommend to do some monitoring, gather data?I also am pretty fluent with React and I thought of Python gathering the data and React app showing the graphs using d3.js
Or is it like too much effort building this whole environment and it would be better to reconsider some 3rd party tools like datadog? What's your opinion on that?
Any recommendations on how to approach the SRE role? I got promoted from being a 2nd line Support Eng and I'm so excited about the new path!
Does it depend on the company's budget as few companies tend to raise the budget after a security incident as compared to steady role for an SRE (handling production reliability)? What is scope of cloud/app security growth?
Hi people,
Just popping in hoping to get some feedback from people in the devops/SRE field. I'm considering transitioning into SRE or devops.
I'm a 42 years old guy, been into IT since my mid 20's and almost all of my career is in ops (virtualization, networking, linux).
Can't say I have done any extensive development but I'm quite comfortable scripting automation with bash and python. I have pieced together automation and CLI tools (integrations with APIs and so on) that made my life easier. Got a few projects on my github account.
Fast forward until 2-3 years ago. I work for a pretty small company (50 employees). I started, on my own initiative, getting into Azure as I didn't see how we would be able to keep hosting our own hardware and continue to scale. Slowly but surely I adopted IaC using Terraform. I started implementing config management using Ansible, for some 200+ linux hosts. I have set up and learned Kubernetes for running micro services loads. I have developed a couple of micro services myself for executing automation tasks (kind of like my own Ansible Tower) and simple stuff like Slack integration for alerts. I'm running Prometheus for gathering metrics on everything we run in K8s. The CI/CD pipeline I have set up is based on Bitbucket pipelines to automate tests/validation and trigger image build. FluxCD running in our K8s cluster to automatically deploy new versions. I love git and I kind of like the concept of gitops.
Now, I feel I have outgrown my company. Actually I have felt that way for several years but stayed because of loyalty (which I realize now was pretty stupid considering the management have changed, and now they don't really care about tech). The concepts of devops just doesn't make that much sense within the company, and the other ops people don't seem too keen on learning new skills. The only driving force to learn has come from myself.
Anyway, I see there are a tonne of jobs out there, mainly devops and SRE type roles. I feel what I'm lacking to move on is experience working in a team, working within that discipline framework, and considering I'm self taught I might not adhere to best practices. And finally I'll admit that I lack some confidence. Like, I know a bunch of these tools, but perhaps not on the level I need to.
What do you guys think? Would I be a reasonable fit for devops or SRE? Sorry for the rambling, I'm just looking for some feedback! Many thanks!
Hey all,
I am an SRE at a big company, but I'm narrowly focused on some stuff that isn't necessarily directly relevant to the greater market for SRE/DevOps.
I'd like to write a blog/tutorial series showcasing how to use modern devops practices, CI/CD, infrastructure as code, and some "bleeding edge" cloud services. This is mostly to sharpen up my own skills, perhaps benefit others, and something to show potential employers in the future so I can stay relevant.
I'm less concerned with what the application actually does at this point (a simple "voting" app, or perhaps a mastodon social network or even a wordpress blog), this is more about the tooling and showing how to deploy a multi-region, highly available and fault-tolerant, cloud-native system.
I'm fairly certain I want to include the following technologies:
Looking for suggestions on what you all think are the most "relevant to the industry" services and technologies, preferably which have a reasonable "free tier" or pay-as-you-go so I can minimize the cost of this project.
"Buzzword bingo" is a bit of what I am going for, I want something to show in github (I can't share anything I do at my actual job).
Thanks in advance for any ideas. What would you include if you were (or have) done something like this? What are the must-haves for experience to be hired as a DevOps/SRE on your team?
I'll start with saying that I'm am absolutely terrible at LC. Even the easy problems are quite tough, I almost always have to look up the solutions to them (and sometimes I can't even understand what other people have done). LC, quite literally, seems like a massive wall between me and a job.
I do not want to be a Software engineer. I originally wanted to be a Systemadmin, but with the cloud booming right now, I'm trying to upskill myself with cloud tech. I can do scripting (Python, bash), write templates, and am comfortable with the concepts and technologies used in the cloud (and am learning every day!) - I assumed that the devops/SRE role would be the best fit for me.
But then I browsed this sub for a while, and it looks close to impossible for me. I can't even solve easy problems, there's very little chance of me being able to solve a medium problem on a whiteboard. I'm still in university, but there's not much time left, and I don't want to sit idle.
I'm sorry if this came off as a rant, but I'm really scared. I'm planning to move to the USA after I graduate (not a native), and LC seems like the one thing holding me back. Does everyone in the USA have to grind Leetcode for these roles? I don't understand why a company would want to hire devs to make them work as cloud admins, but I'm not going to question them, I need a job.
Thank you for your time, it is not looking good for me.
Vasco Cruzeiro GrΓͺmio Bahia Chapecoense NΓ‘utico Sport Ponte preta Guarani CSA
I'm a seasoned DevOps/SREngineer/Team Manager, that's looking to find a company/non-profit that's serious about improving <domain/focus area> that help humans/animals/the world/does more good than harm. I realize this is highly idealistic, but I'm really tired of spending my precious time on this planet enriching millionaires that couldn't care less about the waste and sustainability of their companies produce.
Any good resources for finding these types of employers? Google results are very lack luster for sourcing these companies, and obviously many of them do not traditionally need cloud/ops/site engineers.
*No Agencies / Individual Applicants Only - US only*
Company Name: GRIN Technologies Inc.
Location: 100% Remote - Corporate Office in Sacramento, CA
Technologies: AWS, New Relic, Terraform, MongoDB Atlas, and Kubernetes
Position Details:
We are currently looking for a SRE Manager to provide hands-on technical leadership to our team developing and building core platform products. The SRE Manager will be responsible for building out a team of database and cloud engineers to ensure our cloud infrastructure is well positioned to support our companyβs growth. As a manager at GRIN, you will be leading projects for for disaster recovery, automated failure recovery, capacity planning, high availability, and scaling. Experience with the latest technologies in AWS, New Relic, Terraform, MongoDB Atlas, and Kubernetes is needed.
A Few Highlights & Perks!:
*We are not currently able to offer sponsorship for employment visa status but are working toward this in the near future!*
If interested, please email your resume to nyra.johnson@grin.co
Hello everyone, i am a senior SRE engineer and i am visiting Dubai for holidays. On the way back to hotel i saw Microsoft, oracle and other big tech building and i wanted to ask how is the working condition in terms of work life balance; salary and opportunity for people who do the same job as i do.
Thank you in advance!
Welcome to this weekβs Feedback Thread!
Welcome to this weekβs Feedback Thread!
I've become a junior SRE to a mid level SRE over the last year with no experience - mature career changer. To be honest, I've been in a testing team under the umbrella of SRE. I have a great team of people but I'm unfulfilled in my role and left on my own to do more analysis than technical work. I've been learning, practicing and working with java abit. However I have been given minimal work to be fulfilled.
I am deciding whether to move from my current team to anothe rSRE team in the department to have more exposure to SRE fundamentals.
However, I have been given the opportunity to develop my skills of a developer in java in another deparment where I am given the opportunity to pair programme and work more in an agile way. Also, exposure to other agile roles. I'm hoping to do a degree at some point in the year in Software Engineering, offered by the company.
Part of me is to take this opportunity in the new department but I heard to.be promoted its hard to achiev in the new department. I don't want to be stagnant. Secondly, I'm questioning if I gave SRE a chance and its more pay in this arena.- a lot of people are wanting to come in this area. Also, I do loads of work in my current department outside my role and built a good reputation. I feel like I'm going to start over a again. But I am acting too loyal.
Anyway, I was admant on leaving for the dev role as it can open more doors. Now I'm having second thoughts as I'm a career changer, have a family and need to think through my decisions. Any advice would be appreciated.
Welcome to this weekβs Feedback Thread!
Please note that this site uses cookies to personalise content and adverts, to provide social media features, and to analyse web traffic. Click here for more information.