11 ms·
This is a shortsighted hot take. If it's a bad or average situation, the rational person abandons ship at the first available incremental improvement, or even
by metadat 4y ago
This is a shortsighted hot take. If it's a bad or average situation, the rational person abandons ship at the first available incremental improvement, or even for an orthogonal move to a less toxic environment.
When the situation is good or at least reasonable, the rational person will stick around and see it through.
There are endless shitty places to work. You don't owe anything to a bad situation which treats you, the individual, poorly.
Hiring managers who choose to judge a person in this fashion, solely based on their resumé and how long a person put up with a mediocre or poor work environment in the past, have nothing of real value to offer and don't deserve the good employees. They don't take good care of them.
- ZephyrBlu 4y agoThe author agrees with you. From the article: "You can absolutely explain those stints, and a reasonable interviewer won’t penalize you, but my lived experience is that landing a senior role requires passing multiple somewhat arbitrary process gates"
- hackitup7 4y agoYeah, and in my experience it's also about the pattern. There isn't a rule or anything. 1-2 short stints, totally fine. 3-4 short stints but with one or more 5+ year stints, probably also fine. 5 jobs, never for more than 9 months? Whatever is going on, it doesn't seem crazy to expect that it's going to manifest at job #6 as well.
- defrost 4y ago> 5 jobs, never for more than 9 months? So .. someone with less than 5 years on the workforce? Look, I'm 60+ (ish) and still actively managing projects in code, engineering, mining, signal processing+interp - from my PoV anyone with less than five years on the workforce is still a child. When I look for people to land roles that shepard a five+ year project through I'm looking for people with at least 8-10 years employed already with at least one two year run and a stated intent to "settle" into a position - ie maybe kids, perhaps a new house, maybe family in the area, etc. Exposure to multiple bad projects is fine, especially if they can articulate how things went bad and how things might have been better managed to avoid that (ie big picture awareness). You do have a point, however you might be setting the bar a little low .. less than five years in is barely a toe in the paddling pool of life.
- joebob42 4y agoFwiw this perspective (talking about expectations of age, family status, background as conditions) would get you kicked as far away as possible from any hiring decisions where I work. I think mostly for legal / dei reasons to my understanding, but your whole statement reads like a radioactive hr bomb to me.
- defrost 4y agoSure, none the less, if you're looking for someone (any age, any gender, any etc.) for a long term position who will stick through the good, the bad, and the ugly that might occur during a five to ten year time frame then you're looking for any signs and indications that people have some past experience of sticking through things, are willing to stick through things in the future, and have an understanding of how things can go sour and what steps can be taken to mediate. There are many indications of the ability to make a long term commitment and survive a rocky path, not all of them traditional and conventional, with the least common factor being some time at the pump.
- pc86 4y agoThis just smacks of wanting to treat people like shit. Given the tone of some of your other comments in this thread that actually makes perfect sense. If you want people to "stick through...the bad and the ugly" compensate them accordingly and perhaps most importantly make sure their salary keeps pace with the market as a whole instead of the typical 2-3% raises most people see every year. But even that won't keep the best people, because the best people don't have to tolerate assholes at their job, they can just go get a better one.
- greatpostman 4y agoWage slave mentality
- kortilla 4y agoExpectations of 10 years of experience is absolutely not an HR bomb. You need to retake your DEI training. To get what the op is looking for, you put the 10 year req, then structure comp ballooning towards the end of the vest and it will get you exactly those people op wants. You don’t say, “must be settling with a family”. You offer something that is only enticing if you’re going to stay 5 years.
- thrown_22 4y ago>I was there to solve a problem and stayed no longer than was needed to solve that problem. What problems do you have that need to be solved? Done. It's like people who stay at one job for year never practice for interviews or something.
- Silhouette 4y agoIf it's a bad or average situation, the rational person abandons ship at the first available incremental improvement. There is an old saying: once is luck, twice is coincidence, three times is enemy action. A similar argument applies to people who have past employments of unusually short tenure. Anyone can have a miss and want to move on. Some people could be really unlucky and have it happen twice. If someone gets five years into their career and still hasn't held down any job for more than a year then something is up. Even if they're the most unlucky employee in history they still won't have the practical experience to match their YOE. They're probably the perfect example of the meme about having five years of experience or one year of experience five times. So hiring that person into a senior role isn't looking like a smart move in any case.
- cableshaft 4y ago5 consecutive jobs on my resume: 1 year: Student software dev job working for the university I attended while in school. Couldn't continue it even if I wanted to. 1 year and 3 months: Game producer for a small game publisher that got some bad luck (and a few bad decisions in hindsight) with a few game releases, and the parent company shut it down. 1 year and 1 month: Lead developer at a tiny app development startup where after a while it became clear the board members funding the company didn't know anything about apps and the executive producer didn't know anything about proper marketing or making sure the product made had an audience (but that became clear a little too late to do anything about it). The apps we made were perfectly good quality, but didn't find an audience. Board members eventually pulled the plug after the fourth app release. 1 year and 2 months: worked as a developer (and project manager/dev on one game) for a company that was doing incredibly well when I joined, but had a string of struggles for the following year after. I was part of a major layoff after a big release when the client decided to stop most of the funding. I could tell things weren't going well with the main client, but it kept looking like maybe we were a month or two out from landing a sweet development contract for various large opportunities to work on a big game for a publisher (none of which ended up panning out), so I stuck around just in case. They never did. 0 years and 9 months: worked as a contractor for a consulting company at a small marketing department at an insurance company, mainly just me and a lead developer. One day the lead developer got fed up with his ideas not being used and walked out and started his own company shortly after. The marketing head at that point decided to do something else with the project and didn't need me anymore so my contract suddenly ended. Next job: 6 years. Joined the company and a few months later they announced getting bought by a major corporation. The merger started and everything started getting shittier, a couple major layoffs happened, people kept leaving on top of that, but I decided to stay, in part, because "I have so many short stints on my resume, I need something longer, I should stay at least 2-3 years!" At 3 years, the large corporation we merged with posted nothing but losses every quarter for 2 years, raises were pretty much nonexistent, the bonus I was hired with got taken away during the merger, and our department had about a third the employees it had when I started...but then the pandemic happened, and they had already closed down our office space, so I was already fully remote, didn't have to deal with any uncertainty about being forced back into the office, so I stayed even longer than I should have. So I've had short stints 5 times in a row, always being laid off for nothing that had to do with my performance or capabilities, and that led to me staying way too long at a shitty job to make up for it. A long stint that almost wasn't, btw, as during one of those major layoffs after the first year, as I found out I was on one of the big layoff lists, until a few people quit before it happened and my boss could lay off less people as a result. Been at my current job for a year, and so far it's been doing well and they've had 5 straight years of rapid growth, but we'll see. I sometimes joke that I'm the Ted McGinley[1] of software companies. [1]: https://www.nbcnews.com/id/wbna4549382 https://www.nbcnews.com/id/wbna4549382
- PragmaticPulp 4y ago> the rational person abandons ship at the first available incremental improvement. The problem with this take is that over time, those incremental improvements become harder to find for someone who has established a pattern of job hopping. It’s not a big deal when you’re 24 years old and you’re not really owning major initiatives and long-term projects. It becomes a big problem when you’re at 15 YOE and your resume has ten different companies where you never stayed long enough to even see the long-term consequences of your decisions. I’ve seen a lot of pattern job hopper candidates who clearly have “One year of experience repeated 10 times” who can’t really compete with someone who has fewer jobs but stuck around long enough at each company to make a bigger impact. If job hopping continues, it catches up to you later in a career.
- mejutoco 4y agoI think these concepts are orthogonal. You can have one year of experience 10 times by working 10 years in a single company and not self-actualising. One could argue an employee can stay too long at a job for the comfort and lack of ambition, coasting. Even at the executive level, staying long does not guarantee owning to one‘s mistakes, since there are many ways to deflect blame and many places where top of the org has little accountability.
- hnaccount_rng 4y agoGenuine question: How can you ever learn from feedback loops that take 2-3 years if you only ever stick around for a year?
- mejutoco 4y agoTLDR: you cannot. I am saying they are independent concepts. Basically, if you stay for one year it is not possible to learn the effects of longer projects (very valid point you mention). _But_, staying 10 years does not mean necessarily that you did learn from 2-3 years cycles. It will be _possible_. It could mean you are very good at deflecting, coasting, or playing golf with the right people, among many other possibilities. Unrelated: today is on the news that Unilever's CEO will be resigning after 3 years, which also seems short to me.
- dasil003 4y agoHere's the rub: the "bad situation" you are in is not independent of you as an individual. When you're young and early career you simply don't have the experience to judge what is good or bad (this is one of the reasons employers like hiring young people). You also haven't demonstrated what you are capable of, so why should anyone else hire you? Short of obviously toxic environments, the best bet early career is to put your head down and see what you can deliver in each job, build a network by impressing your colleagues, and keep an eye out for the next opportunity whenever the time is right. It's very easy to fall into a self-pity or entitlement trap that can work against you. Just as bad employers sabotage themselves by not caring about employees, individuals can sabotage themselves by not recognize what they are being paid for.
- zb1plus 4y agoYep. This whole thing about not hiring "job hoppers" is a conspiracy to suppress wages by the management class. Companies will drop you without a second thought, you should have the right to do the same. I think more software engineers should move into consulting where the gun for hire nature of our industry isn't hidden.
- dijonman2 4y agoI couldn’t disagree more. I want to see commitment, not leaving at the first sign of trouble. It costs a lot to acquire and hire talent.
- kortilla 4y ago> It costs a lot to acquire and hire talent. Probably because of your attitude towards it and throwing away people that follow the industry average churn rate. Reminds me of someone who complains about how hard it is to find a date but has criteria tolerances for partners that would make aerospace engineer blush.
- LunaSea 4y agoHow do you know it's only the first sign of trouble? Regular employees don't have the possibility to change companies from the inside, leaving is the only option.
- drc500free 4y agoThat makes sense early to mid career. At some point you become responsible for creating the culture, not running away from it.
- silksowed 4y agonever thought of this but glad you said it. one thing i also think about if i was manager was creating a resilient system of employment. what happens if x leaves tomorrow? is x too critical and knows too much domain knowledge? how am i as a manager going to share that knowledge across my team so if any one person leaves we at least have some way to continue on.
- onion2k 4y agoYou don't owe anything to a bad situation which treats you, the individual, poorly. If someone says they're a senior and they're hired into a senior position but then it turns out that they're not really capable of doing the job of a senior that isn't the company's fault. Those are the people who companies are filtering out when they reject resumes with lots of short jobs. The false negatives of people who left roles because the companies were bad are unfortunate but probably a lot less common.
- ravenstine 4y agoUh, what? Whether someone is capable of doing a job is totally up to the employer. Yes, one has to self assess to an extent and apply to realistic roles, but for the most part the blame doesn't lie on the individual. A senior position at one role may mean something totally different from a senior position at another company. Is it really someone's fault that they were a senior engineer at BrownGrassCo and applied for a senior position at GreenGrassCo only to find out that their definition of "senior" more closely resembles something like a team lead with managerial tasks their previous position didn't involve at all?
- pc86 4y agoThis reminds me of that wojack meme with the normal distribution. There are certainly people on the left side of the curve who just can't operate at a senior level. Nothing wrong with that, most projects need a solid mid-level or two who can chug through well-scoped tickets. They might have a lot of short stints on their resume. But on the right side of the curve are the really great engineers who recognize a situation as bad pretty quickly, and are able to easily get another role. You can't the difference between these two based on the resume, which is why I try to talk to all of them if I can.