Do you have a reliable way to distinguish good teams from bad ones, before you sign the paperwork and put in your notice?
I’ve stayed in jobs I wanted to leave a couple of times now, because my team was a reasonably good team and I was afraid that elsewhere I would end up with Dilbert’s boss.
More importantly, the overall software dev market is such that you can change 3-4 times in one year without really limiting your prospects, as long as you can explain what you’re looking for and why you think the next one is it. You probably can’t do that two years in a row, but trying a new job isn’t a life sentence, it’s an exploration.
Do you have a reliable way to distinguish good teams from bad ones, before you sign the paperwork and put in your notice?
I’ve stayed in jobs I wanted to leave a couple of times now, because my team was a reasonably good team and I was afraid that elsewhere I would end up with Dilbert’s boss.
Not terribly reliable, but you can get a start by asking Joel’s questions (https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/) and Kate Mats ones (http://katemats.com/questions-for-candidates-to-ask-in-an-interview/).
More importantly, the overall software dev market is such that you can change 3-4 times in one year without really limiting your prospects, as long as you can explain what you’re looking for and why you think the next one is it. You probably can’t do that two years in a row, but trying a new job isn’t a life sentence, it’s an exploration.