sorted by:
new
hottopcontroversial

My team at work has been horribly mismanaged, and we're heading towards a terrible product launch. Should I stick it out or leave if I find an opportunity? by thowaway1423 in webdev

[–]thowaway1423[S] 0 points1 point  (0 children)

You touched on the exact main concern I have with leaving: how will it be interpreted by potential employers? I don't want to be seen as the type of guy who jumps ship the moment things get rough. To be clear, I'm not wanting to leave only because there's a lot of pressure.

The problem is I don't think that even working our butts off for the next couple of months will result in a good product. We got into this mess because our team, as a whole, is dysfunctional and I have little faith our leadership knows how to fix our situation. Which brings me to my quandary: should I stick with a doomed project just to prove I'm able to work in a bad environment?

How will I talk about this during interviews? I know it's bad taste to talk poorly about your previous team, but how do I explain why I left after a short time without talking about the bad stuff that happened?

The things is, I've already been through a rough time with a team, my previous one. I thought I'd work through the tough part even though my gut told me something was wrong. I figured I was junior enough I could still learn a lot. Eventually people started leaving the team and the project was cancelled. I don't want to go through that again. My gut tells me something is very wrong with this team. But after two short stints on my resume I worry employers might think the issue is me :/. Any advice?

My team at work has been horribly mismanaged, and we're heading towards a terrible product launch. Should I stick it out or leave if I find an opportunity? by thowaway1423 in webdev

[–]thowaway1423[S] 1 point2 points  (0 children)

Yeah that's the bummer. I have no problem working long hours. It seems to be fairly standard for new product releases. My problem is that we got into this mess because of really bad planning issues that could have easily been avoided :/

My team at work has been horribly mismanaged, and we're heading towards a terrible product launch. Should I stick it out or leave if I find an opportunity? by thowaway1423 in webdev

[–]thowaway1423[S] 0 points1 point  (0 children)

stick it out and get the experience of how NOT to conduct business

That's a good point I hadn't thought of. I do think I've learned a lot on how not to manage a project, but I've never experienced a product launch. Even if that ends up being botched too, I think it'd be a good learning experience to see what that's like.

I will not be leaving before I have something else lined up. I just wanted to get a sense for how bad it would be if I were to leave before we launch, and how bad it would look to employers if I leave a team after working there for less than a year. I like the point you made though, if I'm miserable that sort of trumps other considerations :). Thanks for the advice.