Description du poste
Question for those looking to be #FediHire'd.
How do you deal with the distinction between "my employer wanted things $this_way, so I wasn't able to do things in $correct_way"? I've found this to be especially challenging as my last employer stopped caring about keeping up with the industry trends in about 2010, so I missed the boat on Platform Engineering, SRE, Agile, etc. They were still rocking separated QA, Ops, and Dev teams, still running Waterfall but calling it Agile, and refused to touch anything related to containerization or K8s. Even more importantly, though, we weren't tracking metrics or meta-metrics, nor did they want us to. It was very micro-managed by the co-founders, so there was never any ability to advocate for change – those that did were either forced out or left voluntarily after burning out. They were so singularly focused on "get the feature out the door now" that there was never any room or appetite for "hey, we have an idea for how to move faster, but it'll take time to implement". Any growth we did on the ops side almost had to be done surreptitiously, and I'm sure many of the other engineering teams would say the same.
So, how you handle that situation in your resume and cover letter? I'm finding that, because I don't already have experience with modern SDLC practices, I'm missing out on jobs. Any advice welcome!
#sysadmin #DevOps #getfedihired