My work story can be summarized with the quote: "Gaze not into the abyss, lest you become recognized as an abyss domain expert, and they expect you keep gazing into the damn thing."
So the team I joined was just a teensy bit lacking when it came to rigor. The entirety of their testing consisted of one QA person who had a regression test suite that would hit endpoints on our staging environment. That was it. The whole thing. So I tentatively kept asking about 'Have you heard the good news about our lord and savior: Unit Tests' and they kept kinda brushing me off, saying that they didn't have any idea how to get django's test runner with Oracle, and even if they did who has the time to write unit tests, amirite?
Undeterred, I decided to both get the test runner working with Oracle, and then write extensive unit tests for the core models of our app when I was doing a major refactor. Yay, we have tests, everyone's happy! I mean, I don't particularly enjoy writing tests, and am far from an expert in the subject, but sure, great.
Then it devolves into some guy who's a pal of the team having a Jenkins instance that he was randomly running some security scans on our software images, and they ask if I can get the tests hooked up to there. Okay, sure, I've never used Jenkins before but I guess I can spend time doing that.
Fast forward to now and I'm somehow responsible for managing every aspect of our Jenkins instance and constantly trying to open cases with our IT department that actually owns the global configuration and can change fucking plugins that never seem to work right. I absolutely hate devops with every fiber of my being and somehow I've become our designated devops guy. Also, I'm still the only member of the team who even knows how to read tests much less write them, so I'm stuck with constantly letting people know when they'd break the goddamned build.