Reminds me of when I was hired as an SRE, then told you can't log on to any of the customer systems until you've committed code to the main infrastructure codeb

Reminds me of when I was hired as an SRE, then told you can't log on to any of the customer systems until you've committed code to the main infrastructure codebase and you're "trusted". This was the only thing the other members of the SRE team actually did though - the job itself was basically "figure out why things go weird sometimes in the customer systems and then fix underlying automation issues". But there was an actual developer team as well, including all the original founders - who knew the system perfectly. So things would get posted and you'd be like "oh, that's a good starter task..." and instead a "core" developer would pick it, do the one line fix, and then just push it straight to the master branch (or PR it but it would get approved within minutes in their timezone) while I was still trying to get my bearings in the code and tests. Within a month or two the manager who hired me had "resigned", and then I was let go near the end of my probationary period. The whole time I never had any solid work assigned beyond "oh figure out where you can be useful".