Of course I probably wouldn't know if a place passed on me because of that.
I wonder what the probability distribution for how much hirers weight "loyalty" or "stick-around-ness" looks like.
Of course I probably wouldn't know if a place passed on me because of that.
I wonder what the probability distribution for how much hirers weight "loyalty" or "stick-around-ness" looks like.
On the flip side, it's my responsibility to make sure that my engineers are happy in their position and weren't sold on a lie.
There is a huge difference between being able to fix bugs and being able to fix architecture problems. I needed at least a year before I was capable of the latter in SunOS, probably more than a year.
But maybe the people jumping every year are doing more grunt stuff and the ramp up doesn't take as long? I dunno, I'm mostly retired and sort of a dinosaur.
I work for one of the big 5 and thus use a lot of the tools I use are developed in house (also, there are lots of special technological requirements that I have to understand and work with).
I've been here a few years and am still learning loads about unique company specific things that save me time when I have to do similar things in the future. 1 year stints would definitely not look good to me.