Why We Quit Our Jobs
A manager’s cheat sheet to understand why all of your software engineers left last week and you most likely can’t find any replacements.
Apparently people love listicles, something that I originally thought was some kind of (frozen) tip-top to be quite honest, but on looking it up and putting it on my “avoid these simplistic bullet pointed articles with pretty much zero content” list I generally don’t like them at all.
I’m more of a Dostoevsky or Tolstoy man myself, more so than a Marcus Aurelius or (what’s that guy’s name I blocked on LinkedIn) Simon Sinek. But, enough of that, this article is already longer than pretty much all of Sinek’s in any case…
I feel listicles are perfunctory, contribute to decreased attention spans, and besides I generally like to write in extremely long train of thought unforgiving breathless paragraphs like this one, so this will be a long form list (with added insight, explanation, and much cynicism disguised as humor) and very definitely not a short form bullet pointed list that you can cut and paste into your management PowerPoint love-in.
Spoiler: At least until the very end.
That said, let’s have a bit of a foray into why software engineers generally quit their jobs. You see a lot of dross on LinkedIn about “people quit bosses not jobs” but that’s not always the case.