News for hackers. Stuff that matters.
Re:How to write a developer resume that will get you hired by izolate on Monday November 10, 2014 @07:19AM (#8583124)
Why are you perpetuating the myth that frequent switching of jobs is somehow detrimental to your career? Maybe that's true for corporate megacorp, but in the startup world I feel it's par for the course. At least all the best engineers I've worked with never stuck around long.
Re:How to write a developer resume that will get you hired by Tyrannosaurs on Monday November 10, 2014 @08:40AM (#8583396)
It's not a myth, at least not in most cases.

If I take you on I want some indication that you're going to stay around long enough for the investment we're going to make in you to be worthwhile. We'll normally pay a recruitment fee and then we'll pay you while you're learning about our product, our industry, our processes and the specific technologies you haven't worked with that we use, and we'll be paying our existing staff to take time out from coding to do those things. That's not inconsiderable.

Obviously your experience may render some of that irrelevant. If that's the case then if you're massively better than the other candidates I may take the risk but if you're not, then I can take you or I can take the person who is as good but will stick around longer. That's not a tough decision.

I'm not looking for gold watch territory or even an indication that you might be around for 5 years, and I'm not looking for a guarantee, but if your CV shows a pattern of you moving every 15 months I need to work out why I think I won't be your next 15 month stint and if I think I think I am whether it'll be worth my while.

Re:How to write a developer resume that will get you hired by UK-AL on Monday November 10, 2014 @09:01AM (#8583501)
Most people jump when the company is not paying market price so they switch.

I move very fast from companies that don't keep up with pay. I stay at companies with regular pay rises. I've had both. So in my mind it means that companies concerned with job hopping, are really hoping to keep your pay down. It's an early warning .

Re:How to write a developer resume that will get you hired by Tyrannosaurs on Monday November 10, 2014 @09:34AM (#8583664)
I see where you're coming from but I disagree.

I accept people leave when their salary diverges more than a certain amount from the market rate but that would normally - even in a good market - take time.

Personally I wouldn't expect a major pay rise within the first 12 months of a job (if you do then you've probably not negotiated your starting salary properly). Add to that a couple of months after that to find another job and a month notice and the shortest stint relating to poor pay I'd expect is about 15 months. If you're staying 15 months or so in places which are bad payers and a few years in places which are good then your average is probably going to be 2-3 years. To me at least that's not a problematic amount of time (particularly not if you've shown you can stick at least place for 3 years or so because that says to me you're not inherently disloyal).

So short stints don't say anything, at least not much, about money when I read a CV.

Re:How to write a developer resume that will get you hired by UK-AL on Monday November 10, 2014 @09:43AM (#8583719)
It's simple logic, people move because they can better deal somewhere else otherwise there would be no point. So if people move, the benefits aren't keeping up with other jobs they can get.

Most employees are not loyal, because they know companies are not. If they think companies are loyal, they are probably new to the job market. Once a project ends, and there's nothing else to work on they will get rid of you. There's no reason why employees should not think the same way.

Re:How to write a developer resume that will get you hired by Tyrannosaurs on Monday November 10, 2014 @11:47AM (#8584578)
Obviously there is no one rule for everyone but personally in 20 years working in IT I've never left a job because of money (and I've left a few). I've left because of uncertainty, because the work was bad, because there were too many arseholes where I was, because my skills were rusting but never for money.

In the past five years a fair number of people have left the company I work for and I'd estimate about 25% were money related.

As I say there's no one rule but I've seen developers put up dreadful money for a job they liked and take a pay cut to get out of somewhere they hated and if I had to generalise I'd go with that over them following the pay cheque.

Re:How to write a developer resume that will get you hired by UK-AL on Monday November 10, 2014 @12:26PM (#8584838)
I never meant for money(one part of it), i said a better deal, or a better complete package if you will.
Re:How to write a developer resume that will get you hired by Guvante on Monday November 10, 2014 @02:43PM (#8585773)
You are completely ignoring being laid off, that is a major reason to look at job duration.
Re:How to write a developer resume that will get you hired by kasey_junk on Monday November 10, 2014 @09:53AM (#8583773)
"Most people jump when the company is not paying market price so they switch."

I've seen no data that suggests this is true, and from my own anecdotes I've found it to be untrue as well. The people I see that switch a lot seem to be simply unable to deal with colleagues or challenges that aren't going their way. Lots and lots of prima donna's in this industry that do not have the skill set to change things that are problems.

Even the money concern is a bit of a red herring. Being unable to justify pay increases at your current employer may be a sign of a bad employer, but it's just as likely the sign of someone who either cannot present their value proposition properly or someone who overestimates their value. Both are bad signs for the candidate.

Re:How to write a developer resume that will get you hired by UK-AL on Monday November 10, 2014 @09:59AM (#8583806)
Being able to justify or not justify has little to do with rises. Any smart person can justify just about anything, including justifying no pay rises.

Decent challenges, and decent colleagues are included in my definition of market price.

Re:How to write a developer resume that will get you hired by kasey_junk on Monday November 10, 2014 @10:16AM (#8583916)
"Any smart person can justify just about anything"

This turns out to not be true of lots of people. Being able to understand your value to your employer and to outline it in a compelling way is a skill that is very under developed in software tech candidates. It's also a skill that I've found correlates well with good hires.

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.
Re:How to write a developer resume that will get you hired by ryanackley on Monday November 10, 2014 @07:47AM (#8583217)
As someone who has done a lot of interviewing and hiring, I can say that frequent switching of jobs is a negative and a red flag in general.

If you had a business, would you want to hire someone who is probably going to jump to another job in a few months?

Re:How to write a developer resume that will get you hired by bshimmin on Monday November 10, 2014 @07:59AM (#8583264)
For permanent employees, I would definitely agree - anyone who is unable or unwilling to stay in a permanent position for more than a year, say, probably isn't going to be a good bet in the long-run.

For contractors, it's obviously somewhat different - but speaking from experience, many short contracts tend to get extended, so someone who has a raft of 1-2 month contracts and very few longer ones might be a bit of a risk. (Obviously some contracts are intentionally short - but I would definitely describe a very short contract on my CV as being more of a "project" than an actual contract.)

Re:How to write a developer resume that will get you hired by logfromblammo on Monday November 10, 2014 @01:56PM (#8585470)
If you hire me "at will" then I won't ever stop sending out resumes.

I have had my job eliminated, regardless of my personal job performance, a grand total of four times. I have been forced out via office politics once, and voluntarily left a job once.

If you had a family, would you want to work for someone who is probably going to sell or eliminate your job well before retirement?

The loyalty from employers is gone. If you don't want me to leave in a few months, offer me an actual contract, and one that binds you to the relationship as firmly as it binds me.

Re:How to write a developer resume that will get you hired by FLUX-YOU on Monday November 10, 2014 @08:24AM (#8583339)
So what's the threshold for 'frequent'? Less than 1 year?
Re:How to write a developer resume that will get you hired by peteretep on Monday November 10, 2014 @08:44AM (#8583417)
Rule of thumb is two years. You're allowed to have one or two where you've left after three months - not every role works out.

But more than anything: get comfortable talking about WHY it didn't work out, in a way that doesn't bad-mouth the company and still makes you look like a professional.

An advantage of applying through a recruiter is that they can have this chat with you first, and then make your case to the employer (who they will have a relationship with). As a Hiring Manager, I've said no to candidates, only to have a recruiter persuade me (rightly) that actually I should talk to them, even though there were things that spooked me about their CV.

Re:How to write a developer resume that will get you hired by outworlder on Monday November 10, 2014 @07:56AM (#8583256)
It is not a myth. It WILL raise eyebrows, with HR mostly. A corollary of that is, if you don't actually have a HR department, there won't be any eyebrows to be raised.

However, even if HR doesn't like it, if you do get an interview, then you can tell them a happy story to explain what happened. It helps if you can convince them that this time you'll stick around, provided the necessary conditions are met. Then ask several questions to clarify the points that are important to you.

Re:How to write a developer resume that will get you hired by peteretep on Monday November 10, 2014 @07:21AM (#8583131)
Depends what you mean by "long". I think people should move every two to three years. But you say "myth", and I can tell you categorically that CVs with lots of 6 to 18 month non-contract roles on them get rejected on that basis alone.