I have a PhD in Chemical Physics. I got it about 15 years ago. The need to go deep into computation to solve chemistry problems is what gave me the computer skills that have served me well. That is, after I got my PhD, I haven't done any work in in chemistry or physics at all, but have been a high-performance computing expert everywhere I go. So, in my case, having the PhD really helps, but that's because I work in a field that secondary to my PhD work. I would wager, that's probably true of any academic field. The actual PhD work is so esoteric that it's not going to have any good application to reality (industry) in a reasonable time frame, but the underlying skills needed to get the PhD are going to be super useful.
Now, as for getting a job...I have had very bad luck (until recently) getting the FAANG-like companies to take me seriously: I'm expensive, I don't want to sit around all day gluing APIs together, and I don't have a public repository of code to point to. They want folks who fit into their mold of whiteboard interview. But now that I'm senior enough (15 years + PhD), I'm starting to get the target calls rather than the generic recruiter nonsense.
The point about not having the public repository of code is important: when you're a PhD, you job is to solve problems that _have never been solved before_. That is, it's not a rehash of the same problem in a new language, or a different architecture, or anything. It's new! The world hasn't seen it yet. That means 1) you can't go find an answer on stack overflow, and 2) your day-to-day work is HARD, and often demoralizing - at least I feel stupid every day until I find the solution, and then the dopamine hit keeps me coming back!. Since work is very hard (now, I also don't put tons of hours in, because the work is hard, so that's good). I don't have the mental energy for any side projects. I'm ok with that, I love what I do! But there is no public ego stroking and thought-leadership and all of that other stuff you see with other semi-famous developers. I can't point to a public project and say "I did that" or "I helped build that" because what I do is propitiatory.
Getting the PhD itself was a slog, and I didn't really enjoy the grind. But it is good have that credential. I know SV is all about "meritocracy" and whatnot, but having the PhD is a good signal that a person knows how to think and problem solve with little to no supervision, especially when the problem space is ill-defined. When hiring, I always count a PhD very high. I know a bunch of companies do too. So while the initial work of getting the PhD wasn't terribly fun, I've always had an easy time finding a job or getting a promotion.
I think another commenter said something to the effect that a PhD is a good signal that you can (and have) owned a full project start-to-finish. Don't discount that. It shows you as a closer. That's a good thing.
Sorry for the brain dump, but this was an interesting question you posed...tl;dr - I think a PhD can make you super valuable if you set it up in a way that the skills you learn while getting the degree are transferrable (now) to industry. You will have a leg-up on everyone else entering the field. Just don't get caught in pure theory that will not have an application for another decade. But you need to be ok with feeling stupid everyday because the problems you're solving are hard and new.