Live data from Hacker News

Never hire job hoppers. Never. They make terrible employees.

bothsidesofthetable.com

71–80 of 134 posts

Re: Never hire job hoppers. Never. They make terrible employees.

#71
post #45

Earlier quoted context omitted.

There are absolutely loyal companies. It's just not the norm.

They're definitely not startups. If I need to launch a complex product in 6 months or die, I don't care whether my senior developer had his entire family die from serial dysentery. You're either working as hard as you can getting us to the milestone, or you're not a developer here. The truth is that being "loyal" will kill a startup.

I realize you probably didn't mean this, but the thought that went through my mind reading it is "What kind of psychopath would take such a position?"

Actually, I know what kind of psychopath: the kind who ran the only startup I ever joined. He once told me, "I am at war, and if one of my men can't keep up, I will shoot him." A remarkably similar sentiment to yours! He also used to phone people up and yell at them if they didn't stay till midnight or come in on weekends.

Needless to say (or so I would have hoped), this is an algorithm to produce not a "complex product" but a fiasco, and that is exactly what happened. I was long gone before then, though. What kind of leader shoots his own men? What kind of people want to work for a leader who shoots his own men, or doesn't care if their families die? I know what kind: scared, servile placators. And since such a team hardly makes for startup success, there really isn't an argument here, only a form of hypnosis.

Re: Never hire job hoppers. Never. They make terrible employees.

#72

I think both extremes look bad. Somebody who has had 24 jobs in the last 24 months looks pretty bad. Somebody who has had 1 and only 1 job in the last 24 years also looks rather bad -- depending on the field. If it was a librarian and that's what you're looking to hire, great. But I've noticed that as a general rule, in the software field, if somebody stays at the same employer for 10-20 years, that's usually a bad s…

As much as I support job changing (see my other comments), it's perfectly fine to stay at the same job for 24 years (heck, why not 50?) if it's really good, you're constantly growing, and can demonstrate a rising skill curve throughout.

Your extreme suspicion of anyone who stays for so long reveals a more fundamental truth about the software industry: very few companies manage to keep employees happy and challenged for so many years.

Re: Never hire job hoppers. Never. They make terrible employees.

#73
post #45

Earlier quoted context omitted.

There are absolutely loyal companies. It's just not the norm.

They're definitely not startups. If I need to launch a complex product in 6 months or die, I don't care whether my senior developer had his entire family die from serial dysentery. You're either working as hard as you can getting us to the milestone, or you're not a developer here. The truth is that being "loyal" will kill a startup.

Well if you want to be a startup loyal to your employees you wouldn't back yourself into this kind of corner in the first place, if I was applying for a job at a startup like you mentioned I wouldn't expect much job security and expect to be compensated accordingly.

Re: Never hire job hoppers. Never. They make terrible employees.

#74
post #71

Earlier quoted context omitted.

They're definitely not startups. If I need to launch a complex product in 6 months or die, I don't care whether my senior developer had his entire family die from serial dysentery. You're either working as hard as you can getting us to the milestone, or you're not a developer here. The truth is that being "loyal" will kill a startup.

I realize you probably didn't mean this, but the thought that went through my mind reading it is "What kind of psychopath would take such a position?" Actually, I know what kind of psychopath: the kind who ran the only startup I ever joined. He once told me, "I am at war, and if one of my men can't keep up, I will shoot him." A remarkably similar sentiment to yours! He also used to phone people up and yell at them if…

If you read my other comments in this discussion, you will surely see that I am in fact very pro-employee.

I also am, however, very pro truth.

Anyone who tells you he can have employees with low or zero productivity, for whatever reason, as select members of a small, highly leveraged startup - is either lying to you, or will fail unless he's extremely lucky not to have such employees.

If your team consists of 3 senior developers, and one of them stops producing, your project will likely be pushed back a third or more over schedule. This can easily kill a startup, since if your idea has any merit at all (which is your only chance of success anyway), then you have ten other teams competing against you to launch first.

I totally agree that employees should be respected and cared for, and that a key employee leaving a startup is generally the startup's fault. However, if someone doesn't work out, he will be let go. Not just by the employer - his co-workers will call for his head, since his problems (whether he's to blame for them, or not) endanger the entire team.

Re: Never hire job hoppers. Never. They make terrible employees.

#75
post #73

Earlier quoted context omitted.

They're definitely not startups. If I need to launch a complex product in 6 months or die, I don't care whether my senior developer had his entire family die from serial dysentery. You're either working as hard as you can getting us to the milestone, or you're not a developer here. The truth is that being "loyal" will kill a startup.

Well if you want to be a startup loyal to your employees you wouldn't back yourself into this kind of corner in the first place, if I was applying for a job at a startup like you mentioned I wouldn't expect much job security and expect to be compensated accordingly.

What "corner"? Having to launch a very successful product, very fast, or die - is what startups are all about. Certainly all the VC backed ones.

And yes, anyone expecting any kind of job security at a startup, especially a VC backed one, is simply fooling himself.

Re: Never hire job hoppers. Never. They make terrible employees.

#77

"If you’re 30 and have had 6 jobs since college you’re 98% likely to be a job hopper." If you have had lots of employees leave your company during a recession, you’re 98% likely to be an ineffective employer.

Right on the money. That was one of the most self serving "startup guy" blog posts I've read that didn't come from Spolsky.

Upvoted for dragging Spolsky into the discussion

Re: Never hire job hoppers. Never. They make terrible employees.

#78
post #48

This is the 21 st century. People don't get to get married to their jobs, think of it just as casual dating. As long as both of us are having good time, it is all good. People have been loyal, but they have been paid back with lay offs, either the company goes belly up, or people/projects get cut. Once it happens to you once, you don't do that mistake again. If you see the 'shitty times' ahead sign, some people will…

There is also the situation of someone that wants to code and not be a manger, if they continue to receive interesting projects, are rewarded with pay rises accordingly, I wouldn't say that these people have no ambition, even though they are not really moving up into management ranks.

Re: Never hire job hoppers. Never. They make terrible employees.

#80

Fucking asshole. Almost no one wants to change jobs every 12 months. Looking for work is a pain in the ass and changing jobs is inherently risky. Everyone goes into a job hoping they will work out so well at the company as to have no incentive to leave... at least for 5-10 years. All this is even more true for the best employees, because the number of desirable employers drops off faster than the number of talented p…

> Everyone goes into a job hoping they will work out so well at the company as to have no incentive to leave... at least for 5-10 years. All this is even more true for the best employees, because the number of desirable employers drops off faster than the number of talented people. (The best people, who want only to work at the best companies, have what is in a way the most difficult kind of job search.)

This is a great comment. While part of working for a start-up is being willing to do work that is "below" you (e.g., doing operations and release engineering from time to time, because it has to be done even though you're a software engineer), at one point you have to ask yourself: suppose this company sinks or has a layoff, will I still feel that I've learned and moved my career forward in the mean time? If the answer is no, politely bring it up with the management first (perhaps they don't realize you're underused and not learning), and if no concrete steps are taken to improve the situation, find another position.

The reason to bring it up before looking (or at least before submitting your resignation and accepting a job offer from elsewhere) is not to be tempted to stay when given a counter offer. If there's a genuine desire to retain you long-term, they should have responded when you brought the issue up; otherwise, they just have a business-critical project they want you to finish and can then let you go.

I do have one comment to make: when selecting a job, don't select by thinking "which company will be the most stable and profitable?". Think, instead, "if all of these companies were to tank in a year, my stock becoming worthless, in which one would I have learned the most?". The "paradox" here is that the interesting working and continuous learning will make one feel engaged and fulfilled, leading them to stay longer and contribute more to the company, becoming less likely to be laid off and earning respect from coworkers and business partners, leading to employment opportunities in case of failure.

Compensation and the perception of a company (especially a start-up) as possessing a unique business idea can also cloud people's brains. A lesson I've learned is that if I can't decide between several offers, as they all seem the "same" (in terms of quality of the engineering team, technology used, culture, interesting-ness of their focus), I should pick the one that seems the least financially lucrative to be sure I'm not being "blinded" by the money.

Paul Bucheit's experience at Google (taking a paycut to join Google, despite being convinced they will fail) illustrates this. He didn't go in thinking "I will build my career and become rich here", he went in thinking "I will learn tons here".

Post reply on HN