4 ms·
I'm sorry but if your resume shows you've never spent more than 12 months in a job over the past X years then I pretty much drop it. I don't really care why yo
by andrewstuart 9y ago
I'm sorry but if your resume shows you've never spent more than 12 months in a job over the past X years then I pretty much drop it.
I don't really care why your career has played like that.
At best, you are a an awesome employee who won't stay with them more than your "frequency period".
At worst, you get discovered and fired within your frequency period.
Especially true for senior roles. Team lead for 5 months? Drop the resume.
Not always true, but in general terms if you are a great employee then you tend to hang around.
I know these are generalisations but when I am sitting there reading 300 resumes in a row and trying to work out who is going to get through an employers gruelling assessment process then if you hop jobs then it's just not worth the effort to even try to assess you.
In software development, there is a co-investment between employer and employee in which time spent in a job tends to result an an increase of value through knowledge of the systems and therefore productivity. Job hoppers don't accumulate such value, and leaving early removes that value from the employers side of the relationship.
- jgh 9y agoI see where you're coming from but OTOH the path to increase your pay in the tech industry seems to be switching companies. It's not like you're going to see a 10-20% raise every year staying with the same company. Obviously this usually only works for a finite number of years at the beginning of your career.
- deleted 9y ago[deleted]
- rimliu 9y agoExactly. If it goes both ways then it is also on the company to retain the employee.
- staplers 9y agoPeople like you are exactly why I lie on my resume and always put 1 year, even if I mean 6 months. I got a better offer somewhere else and somehow that makes me less valuable..
- kevinskii 9y agoIt does make you less valuable, for the reasons described.
- staplers 9y agoTwo way street. Pay better, offer better workplace, and other offers won't be appealing.
- lwhalen 9y agoOP should register himself as an S-Corp, hang out a shingle, and market it as a consultancy. Now the pay triples, your short stay at various companies is downright expected, and everybody's incentives align - OP wants to do the best work he can in the shortest amount of time possible (so he can move on to the _next_ client), and his employers^Wclients will pay more to collect on the value OP's work provides sooner. Ironically, if you start spending more than a year at any given client, future clients will start to get antsy about '...why were you there so long? Are you a foot-dragger? What's the matter with you?" This is why you should NOT do hourly-billing, to make sure everybody's incentives stay aligned as described above. :-) Difficulty level: stop thinking of yourself as a 'programmer' or an 'engineer', and start thinking of how your programming/engineering work impacts the business' bottom line. See: https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/ https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr... tl; dr - humans are weird.
- nunez 9y agoIt's a bit more complicated than that. A) I would do it as an LLC, as it's cheaper, easier to set up and doesn't require a partnership structure. B) Not every company is looking for a 1099 employee. In fact, I'd wager that most would rather hire W-2 (US) instead. C) Trying to go the real consulting route will lead to long-ish sales cycles depending on your rate and what you're looking to do. You'll also need to go through procurement at a big enough place; that, in and of itself, can take a while. D) You're on the hook for health insurance and retirement. Health insurance is expensive. E) Days off outside of the weekend and federal holidays comes out of your PnL. You can (and should) factor that into your rate, but see (C) for why that might make building a book of business more difficult. F) You'll need to sell yourself much more than you would as an employee. If you're the type that hates writing/speaking/meetings/selling, then I wouldn't recommend consulting.
- pbreit 9y agoI think the blog post was written specifically for you. Maybe you're wrong? Specifically with job-hoppers, I've found that they can hit the ground running very fast and make solid contributions in compressed time-frames. The best ones cherry pick the best practices from a more diverse set of previous employers.
- jjeaff 9y agoSure, maybe they are good at getting right to work. But then they are gone and all that institutional knowledge goes with them and you have to start over with someone else. There is a lot of value to having long term employees that have been around and know what is going on.
- lwhalen 9y agoThis is why a documentation culture is so very important. Even on the best terms, the average tenure of a tech employee is two years. That's just today's economic reality. As a leader, a project should not be considered 'done' until its documented to such a level that a well-meaning new employee can come in, read the docs, and be mostly up to speed with at least the daily 'care-and-feeding' tasks and the top 5 failure modes.
- sidlls 9y agoThere is a lot of risk of long term employees entrenching bad practices by leveraging their political clout due to seniority. In some ways that's worse than the scenario you describe.
- x1798DE 9y agoShouldn't this argue for everyone having long tenures, since it's unlikely you'll actively fire competent employees just because they started at their job too long and got too well trusted. Having a few long term employees and a bunch of short term ones is the worst case scenario, since it only accentuates the disparity in company-specific reputation and clout.
- citizens 9y agoI think this is tough for both sides. I work with early stage companies, and those companies don't always exist a year. I've also worked with companies (for multiple years) that were bought & sold a few times, so two employment stints can easily look like five.
- paulddraper 9y ago> those companies don't always exist a year You're not necessarily at fault for that, but being part of multiple failed businesses would probably not earn you any bonus points.
- extra88 9y ago> companies (for multiple years) that were bought & sold a few times, so two employment stints can easily look like five You can make it clear on your own resume that corporate changes differ from changes in your role.
- lainga 9y agoWhat if I was part of a university co-op program where I work for 4-8 months at a time between academic terms (which I am) ? I've left an interview where I could hear the CTO say "so why was he fired after 4 months?" as I walked out the door. I understand you have 300 resumes, though -- should I put Co-op or Internship in big red letters before the item?
- andrewstuart 9y agoAny reasonable or legitimate circumstance for short job periods can be explained with a well written resume, but yes it should be extremely clear one way or another that you aren't dropping into a series of short jobs and either getting fired or leaving for better job offers.
- nulagrithom 9y agoThis runs counter to your initial statement: "I don't really care why your career has played like that." Which is probably why he's had such a hard time explaining it in the first place. Lots of people aren't going to take the time to actually read and understand the situation.
- lainga 9y agoThis is my experience, yes. I suspect many hiring staff look over the job titles and snap onto company/dates employed -- and never see the word "co-op". Thus my idea.
- cakes 9y agoHaving attended a university that was coop-based, I've had this discussion (or did when it was more relevant) and the key truly is "a well written resume" (plenty of coop positions come and go so...) Often I would have conversations with people about resumes where they had problems and those problems would be things like: * How long is your resume...? (way too long, often) * Can you drop/compress any positions? (keep recent/relevant) * Instead of "Employment", can you say "Coop Experience"? for the section? * etc. (thought questions, not asking for responses). I do agree, you definitely have to make the "coop" part super obvious otherwise you won't make it past initial filters.
- x_tf2018 9y agoThis is just a silly point of view. What if someone is the victim of a huge restructuring, like a whole business unit or a whole team is let go? What if someone gets bait-and-switched by a hiring manager. (This happens all the time with machine learning, for example... in which you are expected to display an astronomically better quality set of skills during hiring than what the job will actually afford you to use or develop once you start working). What if someone has family problems, illness, etc. etc.? What if someone experiences _multiple_ of these things within a given ~5 year period? Truly, people complain all the time about job-hopping employees, but I don't see companies offering loyalty. People get randomly laid off for no fault of their own, sold on a vision of a job that never comes true, ripped off on their bonuses, or any number of other legitimate reasons to start looking for a new employer even after a short time. Also, if you find yourself in a position where you are reading 300 resumes, you're clearly going about this all wrong, and with the attitude you describe about dismissing people without even the tiniest bit of critical thought put into it, I guess I shouldn't be surprised.
- gfodor 9y agoAll other things being equal yeah you have to screen resumes somehow. But I think the point made in the OP is worth reflecting on: job hoppers may actually illuminate desirable candidates.
- jnsaff2 9y agoWell in the UK as a DevOps my role is in such a high demand that many workers (including me) only take contract roles as they pay roughly double than permanent. But as a contractor my CV is going to be 3 months, 6 months, 12 months and not years at a place. This is how it is here and personally I think I have accelerated experience accumulation as every contract excercises a different set of my skills. Maybe other markets don’t have a contracting culture but I don’t think my CV should automatically be trashed for having short but concentrated employers.
- deleted 9y ago[deleted]
- JustSomeNobody 9y agoI don't know, would it hurt to have one person on the team only interested in pulling tasks and banging out code? They rest of the team could use the extra time to deepen their knowledge of the business.
- extra88 9y agoGiven the expense that goes into hiring, on-boarding, and off-boarding employees, yes having to do that more than once a year can hurt. If it's fine, they should be contractors, not employees.
- tboyd47 9y agoI sympathize with your position but bad management/toxic culture are also systemic problems in the software world. It could be that the person just had a string of bad projects and was trying to avoid getting burned out. It would suck if someone got locked out of a good job that might have helped their career due to that.
- ddebernardy 9y ago> Not always true, but in general terms if you have a great employer then you tend to hang around. FTFY
- rimliu 9y agoYour statemen in the last paragraph about increased value is correct. Alas, too often that does not correspond to the proportional increase in pay. For some reason other companies are willing to pay more. There is also “people join companies but leave managers“.
- nunez 9y agoI understand the sentiment, but think about it like this: You've been working at a company for six months. Recruiters, good and bad, have been sending you offers to interview for all sorts of jobs. A recruiter finally sends you an opportunity that you can't turn down (2x compensation, more vacation, dream position at dream company, shorter commute with same pay, etc). You interview, you ace it, you get the offer. Do you turn it down to build more tenure at your current company? Or do you accept because it improves your situation right now? Rinse, wash, repeat. Based on the number of emails I've gotten from recruiters (on a stale resume, mind you!), I'd say that "the market" doesn't care about length of time at an employer as much as one might think.