6 ms·
I agree with what you've written, but I will say that as someone who's hired lots of folks, the time spent at each "hop" matters. That is, I want people who ha
by hn_throwaway_99 8y ago
I agree with what you've written, but I will say that as someone who's hired lots of folks, the time spent at each "hop" matters.
That is, I want people who have dealt with a reasonable lifespan of a product and been responsible for multiple stages of growth. Thus, if you've had 5 different jobs in the past 5 years I would look at that as a real negative (one reason being that given how difficult hiring is I want to invest in someone who is going to stay longer than 6 months or a year). However, if you spent an average of at least maybe 2-3 years at different companies (and perhaps a much shorter term stint at one company for whatever reason), I wouldn't look at that negatively at all.
- jhall1468 8y agoMaybe you should start paying people what they are worth? Those annual job hoppers do so because a year later someone is offering a 20% raise and you offered a 3% bump and an "atta boy". Companies are trying to control wage inflation by refusing to pay market rate to their current employees. For the record the average tenure in the Bay for a software engineer is 2 years. So your "at least" is the average.
- ryandrake 8y agoIt’s so strange, you’d think the cost of recruiting, hiring, and ramping up a new employee would be much more than just bringing your existing productive employee up to market rate, yet few employers seem willing to do this. I left my previous employer on very good terms and on the way out made it clear that I liked working there and all it would have taken to retain me was to adjust my comp up to market rate. They looked at me as if I just escaped the lunatic asylum.
- deleted 8y ago[deleted]
- oculusthrift 8y agothe strangest is when if you were a new hire you would have gotten the salary you asked for..
- ryandrake 8y agoSometimes I think it would be worth it to just quit and re-interview for your current job every year as an outside candidate--you'd end up ahead of just staying there.
- CzechTech 8y agoFrom my experience, one of the causes of this issue is that in some companies, the people who are in charge of the money (upper/top management) are rarely also people with software engineering backgrounds. These people are often unable or unwilling to fully grasp the concept of "ramping up a new employee" in the context of software development. The fact that any large codebase will take a smart person 3-6 months to acclimate to and become productive. The fact that other people on the programming team have to help these new people (and therefore lose productivity themselves). The fact that the new person is going to produce more errors and the number of defects in the product will temporarily increase. If you look into the history of a company (e.g. by looking at how many users in the issue tracker are no longer in the company etc.), it's usually quite obvious when there's a systemic problem - the employee turnover is high. The management is interested in saving money by looking at the market and trying to hire at or just below the average compensation levels. In their eyes, it's cheaper to bring a new employee to the team (and there's always some fresh meat on the shelves of the job market) than to pay the current (experienced) employee more. And in the short term, they're probably right. But in the medium to long term, this approach tends to have a cumulative effect resulting in high employee churn rate. The problem? Software development is not fast food industry. You can't have high employee churn rates without it manifesting somewhere. But pointing out exactly where and how is not easy (linking causation and effect in a discipline involving multiple people across multiple years is not trivial), especially when you need to link it to the bottom line (the market state and marketing efficiency will mess with your analysis... not that you typically even have access to the financials as a run-of-the-mill employee) and even if you do, there is no reason to expect that you would be able to effectively bring these findings to the management (such work would probably be seen as you overstepping the bounds) or that the management would change the processes responsible (that would be expensive). It's an uphill battle. When you are in a company with high employee turnover, there's typically not much you can do other than to start looking elsewhere. These types of companies will have problems (lower level of respect/loyalty, higher level of product defects, lower productivity, higher technical debt), it's best to leave them as soon as the opportunity presents itself.
- AlikhanPeleg 8y ago> The fact that any large codebase will take a smart person 3-6 months to acclimate to and become productive. If this were true nobody would hire contractors on a short time (less than a year) basis.
- eeZah7Ux 8y ago> It’s so strange, you’d think the cost of recruiting, hiring, and ramping up a new employee would be much more than just bringing your existing productive employee up to market rate, yet few employers seem willing to do this. Not strange at all. The company is willing to sacrifice employees to send the message that people are replaceable and will be let go if they demand salary raises. It's a way to keep salaries from growing. > They looked at me as if I just escaped the lunatic asylum. Good old gaslighting. You get the same look from managers even in high turnover company.
- vinceguidry 8y agoI think a lot of companies think of themselves as the better side of a tradeoff between QoL and compensation. "Sure, you could make more money elsewhere, good luck with that!" Makes sense when you think about it from a business perspective. Some people like running lifestyle businesses. These businesses won't make anyone rich, but one can carve out an economic niche regardless. That niche is predicated on being willing to accept less comp than the broader market pays. My last job was just such a compromise, and, I gotta tell you, if they had listened to me when architecting their new ecomm platform, I'd still be working there, not moved on for $20k more comp. Corporate feudalisms are actually really nice when you're living in the castle, not working the fields.
- iamdave 8y agoThus, if you've had 5 different jobs in the past 5 years I would look at that as a real negative Why? Because the only way to for a working professional to accumulate a "reasonable lifespan" of product knowledge is to anchor themselves to one company? That seems incredibly short-sighted thinking given the changing dynamics of the workplace from remote workers to an increasingly freelance economy where people can work for disparate organizations and still accumulate knowledge, skills and capabilities that you might still find valuable if you weren't looking at arbitrary numbers like how long a person has spent with the same company name in their email signature. Is it a good way? Sure. Is it the only worthwhile and relevant way? Mmmmmprobably not.
- michaelt 8y agoWhat if it takes 6 months for new hires to be net contributors, because they have to be trained in X which hardly anyone else uses?
- iamdave 8y agoA company uses x that no one else uses and you're blaming the job seeker for not having that particular skill?
- michaelt 8y agoOf course not. I'm saying if it takes 6 months to train a worker to productivity, it's not unreasonable for a company to reject someone who's had 5 jobs in 5 years.
- iamdave 8y agoMaybe you've lost me, and I misunderstand your post. Initially I replied thinking you were talking about getting training in a specific set of tasks or platform, you mentioned "Product X". But it seems, now you're talking about training a worker "to productivity", which is a bit more oblique and not as specific of a regimen against what you initially posited-on this I have somewhat of an easier time giving you the concession. Let me just ask, before going further: which position are you taking? Training an employee to use a specific tools set that we've established isn't widely used, or training an employee to be most effective and productive day to day? Or have I misunderstood you altogether?
- kelukelugames 8y agolol, reminds me of a twitter thread. A guy said "As a hiring manager, job hopping is a red flag" . Then someone else posted that guy's LinkedIn page, which was a succession of short stings.
- danieltillett 8y agoWell he would know :)
- neilwilson 8y agoInevitably. Hiring managers with that attitude in this market will rapidly be let go.
- InclinedPlane 8y agoThat implies that all jobs and work places are more or less equal, and in my experience they very much are not. I've had about 7 different tech employers in my career. Of those experiences 3 were pretty terrible and one started out pretty good but devolved into being borderline terrible near the end. Of the truly terrible experiences, only two of them had enough red flags before taking the job to make it obvious that they would be terrible, but at the time I was much less experienced and didn't see those flags at all. There are plenty of folks out there who are even less lucky than I was. Folks who were lured into a shitty job early in their career before they had the experience to know better. Folks who just got unlucky and ended up working at places that seemed fine from the outside but were hell holes on the inside, or turned into hell holes due to mismanagement or reorgs or culture shift or what-have-you. Those people shouldn't be punished for making the rational choice to go somewhere else. Additionally, people don't usually work just for a specific company, they work on a team as part of an org within a company. And sometimes changes in a company mean that teams get changed or eliminated. That can happen for a lot of reasons independent of the quality of the work of the team, but when it does it can often put people in a tough spot, in the best case they will have to go on a job hunt internally, but often times (especially in hot tech markets like SV) if one is doing that it makes sense to also cast a net outside the company as well. Asking people to spend 2-3 years at a company without any knowledge of what the conditions were like there or the reasons for someone to switch jobs is pretty silly. In fact it could be an indication of a lower quality employee. When conditions go south the people who have the highest intrinsic motivation to do good work and the people with the best skillsets are precisely the ones who are more motivated to leave and can more easily find a new job. People who just cash paychecks and have mediocre skills are going to hang on to whatever job they have for as long as they can. Additionally, if a company is worrying excessively about holding on to employees, worried that they might be "too flighty" or what-have-you, that is kind of a red flag for me. If they don't have the confidence that they can convince someone to stick around then maybe they are expressing a subconscious judgment of the poor working conditions (or lack luster compensation) there.
- sidr 8y agoOk, so a handful of short stints could be because of toxic environments. But say you classified all 7 of your previous tech employers as toxic; at some point the only common factor left is you. No company can guarantee zero employee churn - some people are just the type to bail after a few months regardless of what the employer does to hold on to them. It's only logical for a hiring manager to try and identify and avoid those people.