First off, I want to express that, barring malicious intent, you have done ABSOLUTELY NOTHING WRONG. Processes should exist that no one, from the cleaner to the

First off, I want to express that, barring malicious intent, you have done ABSOLUTELY NOTHING WRONG. Processes should exist that no one, from the cleaner to the senior architect, should be able to push back a production release by a month. That aside, to put that on a junior engineer is at best negligent and at worst down right vindictive (possibly seniors covering their tracks because deep down, they know it's ultimately their responsibility). Stories like this frustrate the heck out of me. As someone who progressed from junior to senior in a little over 2 years at a pretty major company (pretty much any American would know the name), the quality of mentors early in your career is PARAMOUNT to efficient progression. A seniors top priority should be the progression and happiness of their junior engineers (one of my best tech leads used to say "The less code I have to write, the better a job i'm doing"). Sure, they could bash out a production ready service once a month - or, they could nurture the people they're meant to be guiding, and at the end produce several senior engineers of equal quality. My advice? Have some frank conversations with your team, and if it comes to it escalate higher. Ask concretely what the expectations of a junior are there and why that is the case. Also ask what they see the role of a senior to be as well. Express that you're coming from a place of wanting to better yourself not only for your own sanity, but the benefit of the company at large. If things don't change, move on swiftly.