I joined this company as a DevOps Engineer. Initially I felt I have lot of freedom to try out many things. Later it became a liability itself. There is just a basic DevOps pipeline exist and it’s responsibility of us to write our own features for the sprint and execute it. There is no architect in the team and we work independently. Until the last moment we don’t know what we are doing is correct or not. Senior / Lead developers can’t visualise it as they are not actual expert in devops but just spending part of their time building some pipeline stuffs. It’s quiet overwhelming to explore the required features , estimating the complexity and writing down the story + executing it every sprint. I feel like I am doing a work of a solution architect + Devops. I have 2 years of Cloud experience and sometimes I get burnt out when people question only about results and not about the complexity or lack of expert resources. When I get struck, I have no experts out there to help so I have to spend lot of time myself to handle the situation. It’s fun to do that but time constrain to complete the tasks spoiling all the fun. How to handle the situation? Is it same elsewhere as well !? 100k
Transition to SRE at some other company and get paid more
This is how a gold 🪙 is prepared. As a side hustle prepare for switch and pay bump and keep exploring as long as you are here.
Start by asking questions and measuring things. How long does it take to get code to prod? How often do releases happen? How often does a release break prod? How fast can you fix issues in prod? How confident do stakeholders feel during releases? What would dev teams like to do but feel like they cant? What don’t devs do that they know they should? What isn’t being done that you know should be done? How do devs spend their time? Do devs often face merge conflicts? Do teams keep breaking each other’s APIs? Figure out the biggest pain points, then think about how to fix them (hint it’s not always with code / pipelines), then pick the easiest high value things to do.
I was in the same situation 2 years ago. Either you step up and take initiatives to improve your job (ask for more engineering resources/re-organize workflow among the team so you feel less burnt out/etc.), or you leave for a place where you can grow. I did the latter.
I feel your situation. Look at the bright side which is you got a place to learn a lot and explore, build experience. You can always negotiate to get you a higher pay. Since there are no architects as such feel free to pitch new ideas. In my opinion, there’s never a perfect job description for devops. It always differ from company to company. So there’s no guarantee the next place will be better but if you get good stories together from your current place then next place will definitely pay you more.
Tech Industry
Yesterday
938
PM is irrelevant role and will die in next 2-3 years.
Health & Wellness
Yesterday
542
Loneliness poll
India
Yesterday
1081
Ideal indian parents
Software Engineering Career
Yesterday
560
If your team does daily standups, your manager is a micromanager
India
Yesterday
587
A list of ethnic slurs on Indians that should be banned on Blind
“Too many expectations” or “too high of expectations”
Right . Rephrased !