News for hackers. Stuff that matters.
Re:How to write a developer resume that will get you hired by kasey_junk on Monday November 10, 2014 @08:35AM (#8583385)
As someone who has done a ton of hiring, switching jobs a lot is definitely a red flag. Not an automatic reject, but I frequently have to make choices like "It will take this person N months to become useful here, they switch jobs on average every M months. M-N seems like a pretty short time..."
Re:How to write a developer resume that will get you hired by raverbashing on Monday November 10, 2014 @08:49AM (#8583433)
So, would you advise towards a competence based CV?

In case a frequent switching happened, what would you like to see in a resume?

Re:How to write a developer resume that will get you hired by kasey_junk on Monday November 10, 2014 @08:59AM (#8583494)
The things that would really make up for the switching would be either A) experience which is very close to what I am currently hiring for B) a reason for the frequent switching.

At least for me, the CV is the least important part of the hiring pipeline. I have found them to have virtually zero correlation with good hires. So if I get a CV with frequent switching on it, and the candidate is great in all the other pipeline, it probably won't matter at all. If on the other hand, there are other questions about the candidate, a frequent switcher will get some questions about what they want in a job and a little bit of skepticism if we think there will be a big ramp up cost.

Re:How to write a developer resume that will get you hired by peteretep on Monday November 10, 2014 @09:17AM (#8583574)

    > In case a frequent switching happened, what would you
    > like to see in a resume?
It wouldn't be insane to put a leading paragraph explaining why you'd moved around so much.