Ask HN: In the 90s, did programmers job-hop frequently?

I co founded a 400 person company started in 1996 and sold in 2011; we had only 2 people leave (we fired a few but that’s not job hopping) before 2008. I have another company for the past 10 years and it’s nearly impossible to keep people, especially during&#x2F;after covid, no matter the pay. I would say it definitely increased from my pov.<p>Edit: reasons for leaving are; 1) want a bigger company for security (which is not really a thing here as you get paid even if the company goes bankrupt or you are fired; also I have funds for 10+ years for every person we hire; it’s not possible for us to go bankrupt as I am risk averse these days) 2) wanting to do resume driven dev; in that case indeed I wish them luck but good riddance; those are the most worthless to me; wish I could detect that behaviour earlier, but for obvious reasons, they try to hide that

We didn&#x27;t think of it as job-hopping, but yeah, staying at a job for about a year was not uncommon. The thinking was: demand is high, so if you aren&#x27;t eventually recruited out and you really can&#x27;t find anything better, maybe there&#x27;s something wrong with you.<p>Yeah, that line of thinking can be bogus. I ended up staying at a startup for quite a while, and occasionally had to defend myself for not bailing out even after a couple years. Saying, &quot;Stock options&quot; and winking usually quieted down the critics. There are reasons (even beyond stock options, LOL) for staying at a job for more than just a little while.<p>BTW a lot of what others have said here (pay raises came from getting new jobs, employers saw long stints at a company as a potential warning sign that you aren&#x27;t really very good) does ring true.

.com boom was full of 3-6 month contract roles, where each new contract was an opportunity to improve cash compensation.<p>Improving earnings via job-hopping is nothing new, the difference may be in the other reasons people hop.

I think it depends on how you define &quot;job hopping&quot;. I think that <i>very</i> short tenures (something less than 2 years or so) were rarer then than now, but I don&#x27;t think that anything over, say, 3 years is what I would even call job hopping.<p>I think 3 years is plenty of time to hone your skills, grow in an organization, and get exposure to multiple different projects or teams. After that, I don&#x27;t think anyone would begrudge you for leaving for a better opportunity, now or in the 90s.

I job hopped all the time in the 90s. It&#x27;s not a new thing. Whether it was common for most people I can&#x27;t say, but the idea of jobs for life was already gone.

When I was in highschool back on the early 80s I got a job paid internship. One of the programmers told me the average turnover in the industry was 3 years. I believe today the average turnover is 3 years. I don&#x27;t think much has changed, and it has nothing to do with LinkedIn, glassdoor, etc.

Seems normal for 20-somethings, yes people did this in the 90s. Probably necessary in your 20s, to get varied experience and increase pay. 30-somethings can be more risk averse if they have young kids. By 40s and 50s, more chance someone knows what suits them and found a place that&#x27;s a good fit and they want to stay, sometimes by then they have enough assets that they&#x27;ll stay in a job they&#x27;re happy even if pay is stagnant. 50s and older, do you really wanna do lots of job interviews, learn how a new company works? By the time you&#x27;ve done that a few times you lose appetite to keep doing it (not because you lose ambition, just, you know its not really gonna change your life and could be a bunch of hassle)

I sure did, as did most of the devs I worked with. For two reasons: first, that the only time you&#x27;d get a pay raise is by changing jobs and second, because lots of employers considered more than 5 years or so at any given job to be a yellow flag (because it&#x27;s a potential indication that your skills aren&#x27;t staying up to date.)<p>Even now, I rarely stay at a given job for more than 5 years or so. But that&#x27;s mostly because I get bored and want to do something new -- and because my skills get stale and I want to use new ones.

I did. Mostly because I kept finding myself on dead end projects. I&#x27;m not sure why I kept getting into that situation. After 2001 or so I had better luck but still usually switched gigs every couple of years. In my 28 year career starting in &#x27;86 the longest I stayed at one corporation was 7 years and I was on four different projects. Shortest was one month. Signed on and found they really had no plans for future projects. I&#x27;m not sure why they were hiring.

Yes, the general rule was to stay at least a year though. My first two jobs were a hair under 2 years each. The first one was an unbearably toxic environment, but that&#x27;s typical of your first job. I learned a lot because I did everything: networking, database, reports, server config, applications, integration, support, etc. All from scratch. The second I learned a lot but got stuck in a rut once I learned it. This was my big name company. I then did contracting for a year then the dot bomb + 9&#x2F;11 happened, contract expired and I was out of work for 6 months and miserable. I learned that it might be beneficial to stick around a place for a while that seemed stable. First job after dot bomb was 8 years (learned a lot but stayed 2 years too long), 6 years (learned a lot and left at the right time), then 2 years (didn&#x27;t learn much, tried to right a sinking ship) and currently 5 years (learned a lot and it was a file -&gt; new experience).<p>I did a whole lot of projects on my own time to keep up to date with interesting new tech and make some side money. Nothing really blew up though.

I worked and continue to work in the video game industry, and I started in 1994. In my industry, the norm is not to leave mid project, and so job hopping frequency correlates directly to project length. My first couple jobs were about a year a piece, and that wasn’t unusual for the time. Those stretched out into 2 or 3 year gigs later as the games got bigger. Now that I work in mobile games, and live service has become a big moneymaker, this has changed. The industry is reasonably volatile, companies come and go quite a but, so job lengths of only a few years isn’t particularly frowned upon.

Back in the 90s there was still this idea of working at the same company for life. Places like Kodak and Xerox use to have this.<p>Some of my adjunct professors in the Rochester area would tell me about this.<p>Things started to change after the dotcom crash and the acceleration of new technology taking out larger legacy firms.

I changed jobs every 2-3 years as its the only method to get a proper raise in this country. I only worked 6 years in one place which was my first job.<p>So this worked for me so far. I guess it depends on who you are and the level of shit shoveling you can handle. I noticed that this level is surprisingly high for some people.

I did. The interviewing situation was much more reasonable back then, so it wasn’t difficult. You could do lots of interviews without taking up a huge amount of time and I never did any live coding or whiteboard coding bullshit. Companies also fired people more quickly when someone wasn’t working out. It was a healthier job market in a lot of ways.

1996 to 2000, I was at 3 different companies. Then the company I joined in 2000, I was at for 5 years. Then a smattering of small companies and then two large companies.<p>These days people hop from job to job for more TC. For me it was about interesting projects (not always profitable).

&gt; Was it like this in the pre-Linkedin-recruiter-spam and pre-Glassdoor-interview-question days?<p>I will say this, we had way less information back then. People still job-hopped, but there was no levels.fyi tempting you with grand fortunes. For me at least, it was friends or friends of friends and word of mouth. &quot;Hey, there&#x27;s this new company VMWare, it&#x27;s only 20 or so people, but they are doing this cool stuff, you should look into it.&quot;<p>Typically if you were outside of the bay area, job hopping wasn&#x27;t as frequent because most cities didn&#x27;t have a LOT of companies to chose from. I was in San Diego at the turn of 2000 and there was military contractors, semiconductors, and telecom. If you made to the top and worked for Qualcomm, you usually stayed there. At the time, in that particular region, no one paid a whole lot more and everyone got their own office at QC. They started stock-splitting every quarter and no one was going anywhere, no matter how much they were over worked.<p>I would say the temptation for me personally to job hop now is less than before because there is just so much more information about companies, and at the end of the day, most companies who pay well suck pretty bad, and amazing companies don&#x27;t pay all that well. :)

Maybe in USA only!<p>Back in the day being a programmer was definitively NOT &quot;hot&quot;.