4 ms·
It depends on how big the things you're building are. If you have an influence in direction-setting, policy, procedures, norms, even company culture, if you're
by mancerayder 5y ago
It depends on how big the things you're building are. If you have an influence in direction-setting, policy, procedures, norms, even company culture, if you're involved in large projects that take time, then 1-2 years might not be enough. Certainly not 1 year. If you're in a large organization, it takes many months to just build the relationships enough to accomplish bigger things.
Jumping around every 1-2 years is fine if you're junior or mid. After that you're suspect. We had a guy who left after 1.5 years. It was sudden and disruptive, and the guy burned bridges. We were not surprised since his past jobs were like that (short stints, and anger by the end of the last one). However, now, everyone we interview who's senior, we look at a different light with regards to job hopping.
Lesson learned with regards to that. Beware of senior engineers who job hop.
- sf_sugar_daddy 5y ago
- sbarre 5y ago> Beware of senior engineers who job hop. I think this is a bit too much of a generalization. I would caveat this with "understand what you're hiring for". In some cases, you need a specialist to come in and laser-focus on a problem, and then maybe someone who won't be with you for long, but will tackle those problems, is just fine - and even what you really want: no seat-warming, just get it done and get out. But if you're hiring someone to lead a long-lived team working on big projects, then your point stands.