4 ms·

This reminds me of that bell curve meme. Yeah, if you are a hotshot / rockstar / high performer / whatever, yes you're going to job hop if you end up in mediocr

by pc86 2y ago

This reminds me of that bell curve meme. Yeah, if you are a hotshot / rockstar / high performer / whatever, yes you're going to job hop if you end up in mediocre environments. But you'll end up job hopping from the exact same companies if you're just not a good developer and you can't keep up in even mediocre companies. There's also a few reasons you might appear to be job hopping that have nothing to do with your skills. Using length of previous employments as a metric in ascertaining someone's skills isn't worth it. There's too many variables and the possible reasons are too varied. Maybe they're absolutely amazing and all those companies aren't. Maybe they're really bad and they can't keep up. Maybe they had family issues and they were demanding jobs. Maybe they had health issues and they care more about money now than they did before. Maybe they exited on a side project and they don't care about money nearly as much as they did before.

lotsofpulp 2y ago
> Using length of previous employments as a metric in ascertaining someone's skills isn't worth it. It depends on the nature of the type of labor needed. If an employer needs a warm body, then evaluating length of previous employments might be worth it. If an employer needs a high performer, then it might not be worth it.
kayodelycaon 2y ago
In the places I've worked, skill wasn't the primary metric. You had to be good enough but working well in the team was more important. As long as you met the minimum skill requirements for the position, we prefer people who increase overall team efficiency. We tend to avoid "rockstar developers" in my current company because many wouldn't be happy here. I happened to be a "rockstar" right now because my skills and culture are an ideal match. My team is small and does a lot, so we really can't afford to hire the wrong person. Better to leave the position open.

by pc86 2y ago

lotsofpulp 2y ago

> Using length of previous employments as a metric in ascertaining someone's skills isn't worth it. It depends on the nature of the type of labor needed. If an employer needs a warm body, then evaluating length of previous employments might be worth it. If an employer needs a high performer, then it might not be worth it.

kayodelycaon 2y ago

In the places I've worked, skill wasn't the primary metric. You had to be good enough but working well in the team was more important. As long as you met the minimum skill requirements for the position, we prefer people who increase overall team efficiency. We tend to avoid "rockstar developers" in my current company because many wouldn't be happy here. I happened to be a "rockstar" right now because my skills and culture are an ideal match. My team is small and does a lot, so we really can't afford to hire the wrong person. Better to leave the position open.