Devs should keep their team when changing jobs (blog.goelevator.com)
over 7 years ago from Mike Anderson
over 7 years ago from Mike Anderson
This is weird to me. It feels totally wrong for a lot of reasons.
Hey Jonathan, Did you see the examples in the article? They weren't negative at all—exactly the opposite. There are tons of reasons for a team to move on at once—for example in Seattle this week Porch.com is downsizing same thing happens at Microsoft and Amazon all the time. It would make a ton of sense for those folks to put themselves on the market together.
I did see the examples, and by no means do I think this is a bad ideal. I just don't think many people (other than large companies) will want to hire these kinds of teams - it's too risky. You lose one and you lose them all? I guess retention could see positive gains, but as a person looking to hire in the agency world, at least, this is never feasible for us. Too much investment up front, too much risk.
But, this is ultimately what you do when you hire a consulting firm. The difference is, you aren't bringing a consulting firm on full time - you are setting a contractual limit (and contractual requirement) to the engagement.
Designer News
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Have feedback?
Login to Comment
You'll need to log in before you can leave a comment.
LoginRegister Today
New accounts can leave comments immediately, and gain full permissions after one week.
Register now