←back to thread

Hopping too many startups in a row?

23 points 15characters | 1 comments | 21 Oct 24 01:07 UTC | HN request time: 0.206s | source

The last 3 positions I've held have been SWE at relatively small startups. Within 2 years of being at those companies, big changes occurred prompting me to hop for job security (didn't secure next round of funding, C-suite got replaced, etc). For me, this is the nature of startups- fast turnaround and turnover. I thought this was normal until my last interview where a recruiter was looking for stronger explanations as to why I haven't held a position for 3-4 years recently. Being clear that it wasn't a positive sign to them. Is it really that strange, or were they maybe used to bigger company culture and expectations? Not going to risk my own security riding a sinking ship.
Show context
etcd ◴[21 Oct 24 09:12 UTC] No.41902140[source]▶
When you hop, at least get promoted. That way it paints a better picture. If you can honestly say that job C has more responsibility than B and B than A (even if same title) that is good too.

One option is to work for a large company with more opportunities negating the need to hop due to it going bad financially and more room to go up levels etc.

replies(1): >>41921762 #
1. bruce511 ◴[23 Oct 24 04:14 UTC] No.41921762[source]▶
>> When you hop, at least get promoted. That way it paints a better picture.

I mean, it does, but it's still got a good picture. It comes across as "I'll jump ship the moment a better offer comes along."

The problem with job-hoppers is that there are ones done for sensible reasons (I joined high-risk startups, but ultimately they failed, or got acquired or whatever) and ones who just treat the position as a placeholder until something better comes along, or until they get itchy feet etc.

It's hard during the hiring phase to tell the difference, so employers tend to err on the side of "why take the risk?" Especially in the current market where there are plenty of other applicants.