Software Engineer • Current Employee
Pros: These are the blissful few days where I don't have to deal with DevOps.
Cons: Some of the other negative reviews might mention how the pay isn't as competitive for the amount of work done, or how the in-office requirements are annoying. Both of these things are true, but this is not why I'm writing this review.
The DevOps team at this company is comprised of some of the most inconsistent, obstinate, and inattentive people I've ever had the displeasure of working for. If you need ANYTHING done deployment-wise, it becomes a hellish slog of:
1. Submitting a ticket
2. Waiting on them to assign the ticket to someone
3. Pinging a VP to get them to assign the ticket
4. Pinging the person who's been assigned the ticket
5. Watching as the person who's assigned the ticket go OOO before getting it done
6. Pinging someone else on the DevOps team to get it done
7. Waiting for them to ultimately pass the buck to someone else on the DevOps team
8. Debating with the other people on the DevOps team as to why they simply can't or won't do it
9. Ultimately doing half of their job for them, with the only reason that you can't do the other half yourself being that you don't have the authorization to do it
10. Waiting until something breaks and repeating from step 1
To be fair, I am exaggerating a bit, and you don't have to go through *each* step, *each* time. But I have encountered each of these issues at least once in my dealings with DevOps, and I can guarantee you that evil tenth step is a requirement each and every time.
Every time I realize one of my changes requires some kind of config or IAM change in AWS deployment, my heart sinks to the floor as I come to the sobering realization that I have to deal with these people. Add at least 2 or 3 sprint rollovers before I can finally rid my mortal soul of this pestering project. It's gotten to the point where other people on my team are advising me to *factor in* obscene response times from DevOps when planning out my work. We are actively expecting breakdowns in communications with DevOps when scoping out our tasks!
This isn't even considering the times where you *don't* expect to work with DevOps and they rear their intrusive heads, regardless, when they make some change that breaks your ability to communicate with services and wouldn't have changed anything for the positive had it even worked in the first place.
There is a bitter, metallic taste that engulfs your mouth and throat when a project you've been diligently working on screeches to a halt, and it's not because of anything in your code, but because the pipes are leaking and the drywood is warping in the endless labyrinth that lies between your lines of code and running executables on prod.