I think for a lot of engineering jobs this is absolutely true. That said, it depends entirely on what your focus or what your industry is. As an example, befor

I think for a lot of engineering jobs this is absolutely true. That said, it depends entirely on what your focus or what your industry is. As an example, before I moved into software engineering, I worked in digital media. There are maybe 22,000 working journalists in digital media in the United States (and that's also allowing for employees at the larger national papers like WSJ, NYT, Washington Post, etc) -- give or take a couple of thousand. If you then factor in for location (say, New York City) and coverage area (say, technology), you're now down to a small enough number of people that you can and will realistically know someone at almost every single place you would be going for a job. You run into people at conferences. You see people at the same parties. You have mutual friends. It's small and incestuous. So in that case, telling HR or your editor how the company can go fuck itself is usually not a great idea. Because you'll wind up working with these people again someday. Unless you're in a more specialized area or community, software is different because you have 8x employees at one FAANG than in some entire industries. So in that case, as you said, turnover can be so swift and the reference is usually "Bill worked here from X to Y and had the title of Z." But if you ARE in a specialized area, social capital matters a lot (I frequently get pinged by people at companies I don't even work at, asking my thoughts on a particular person) and so that's one more reason NOT to do the exit interview, or to at least not tell the person where to shove it in that interview.