Programming

Every engineering job I've left has been because of bad leadership.

The first, they hired a lead with no business being a lead. Not only was I much stronger from a technical perspective even though I had only been doing it professionally for about 3 years, but I was a better leader to the rest of the team as well. I had been sort of filling in in the interim before they were hired. They were let go not too long after I left.

The second, they hired an EM. I had been asked to work on setting up the code base for replatforming our web app and begin migrating pieces of it over. I was basically doing this on my own and working with timelines that I had given to leadership and providing weekly updates. This EM started micro-managing everything. This not only slowed my progress to a crawl, it was demotivating and stressful. They were let go not too long after I left.

My current position, I was moved to a new team during a company reorganization. The EM on this team is completely psychotic. Micro-managing to a degree that I've never seen before. They're convinced that what we do Agile SCRUM, but we take in large projects each quarter, plan and scope them at the beginning, and then spend the rest of the quarter executing on them. When I or the team make suggestions that align better with agile, we're gaslit and told our ideas "are waterfall not agile".

We usually don't take on projects that go longer than a quarter. The project that I'm on currently is bleeding into Q4. I warned about this from the very beginning, but the result was just more gaslighting, that I took too long on planning. I would have left, but the job market isn't as friendly to hopping around as it was previously. Thankfully, I'll be switching teams once this project is over.

Overall, all of these places had their problems beyond leadership. These are things that I can tolerate however, and with good leadership, can work towards improving. Once leadership turns to shit, it's time to gtfo.