Experienced Devs

I've switched jobs about every two years on average for the past 19 years of my career. Unfortunately it's just like you said, the only way to get a meaningful increase is to jump ship. That said, once you break 100k, that motive seems to calm down a bit. You start caring more about the culture and the people you work with than how much you're getting paid. I've taken a pay cut even once because my mental health required a better environment.

But sadly, at least in the startup world, there is this perpetual arch I see all the companies take. They all start good then slowly devolve into something worse, where when you finally leave you're glad to go. Something about getting bigger corrupts what was good about a place, and if you IPO good luck. Culture goes out the window as soon as shareholders become your only driving concern.

So as jaded as that sounds, sometimes you do find a good place, and they give you decent enough raises and you can stay a while. Although for me personally, the longest I've stayed somewhere yet is 4 years or so. Maybe one day I'll find that magic place that's worth staying at for a full decade

I worked for my first company for a decade. I cannot stress enough how much this held my career and technical growth back. I got raises in that position - in one case a good one - but none of them compared to how fast my salary went up once I started hopping jobs from time to time.

I'm finally to the point after twenty five years where I'm making enough for the cost of living and I almost don't care about pay - it's much more about culture and finding a good team.

A 50% pay bump is unusual though. I'd expect more like 10-20% depending on the current market. I'm in the middle of a job search and I'll be damned lucky not to take a shave because there are so many laid off developers now. If someone offered me a 50% bump I'd take that in a heartbeat if there were no red flags. Although I'd need a massive freaking raise to go back to an office - QoL is so much better working remotely 90-100%.

It's strange because I have never had leetcode questions. I'm a C++ developer and, when I switch, I'm always asked about my previous jobs, and maybe my experience in C++20 with a few questions like "what objects of the C++20 STL have you used so far?"

I guess it depends on the country (I'm in France) and the language I want to work with (mostly C++ for me but I can do everything else).

Over a decade later I'm still with my first employer.

I could make more elsewhere, but I suspect at max 2x after twelve years - not 2x every 4 years. Did I receive more reasonable raises than they happen in your experience?

With other things I value about my work environment and employer, my pay is fair and good enough for me to stay.

I'm so glad I don't have to hassle with prep and interviews. (I had one phase where I did but ultimately stayed with my employer in a bit of a different setup.)

Switching every 2-3 years? Sounds about right. The only time I've stuck around longer was if there was a really good reason (like an RSU vesting schedule). It seems as though most companies will prioritise getting new people in rather than retention of existing staff. The other issue I've seen is that sometimes people who stick around at the same company for a while get a bit institutionalised and have difficulties switching to another company. Where I'm currently working in all hands meetings there's usually a work anniversary section and some people have been at the company for over 30 years. I just couldn't imagine that.

My last few jobs have only lasted 6 months though. One of them lied to me in the interview and when I started it turned out I was doing nothing but dealing with legacy systems. Another had some interesting problems which meant I had 3 managers in 6 months. Then I got an intern who couldn't program because he was related to one of the senior guys in the office.

Anyway, in terms of interviewing, personally I tend to just prep a few months before I start looking. Just do a load of leetcode, read up on some system design crap, that kind of thing. It all feels like a bit of a farce to be honest because everyone asks the same questions and by now everyone knows what will be asked and what the standard answers are. It's just a case of being able to memorise the standard answers.