Caveat over, onto the generalization: From having done a few dozen interviews now, the self-taught applicants are more likely to have holes in their knowledge that they don't know about. That is, CS grads have (hopefully) gone through a broad and formal program so they have a more complete mental map of the knowledge space and their own weaknesses. The self-taughts don't know what it is they don't know.
This gap can be overcome, but the pattern I've often seen is the knowledge gap and disadvantage is compounded by the first jobs the self-taught tend to end up in. Rejected from graduate programs in larger firms where they'll be exposed to a wider range of talent, they often end up in smaller shops where they work in a niche where they're not challenged to keep growing (just as often due to the nature of the business. Smaller shops tend to be contract businesses, and contract work doesn't provide much opportunity to go deep on problems in the way that will stretch and grow you). And because they don't know what they don't know, they don't realise the gap between their skillset and their contemporaries who went the formal CS track.
Frequently I've interviewed developers who've done this for 5-10 years and decided they wanted to try working in a larger company. And they're hard interviews. I hate it when an earnest applicant is an obvious 'no' in the first few minutes, and it's because they've specialised into a low-level dead-end, and they didn't realise it.
Having said that, I think we're at a point where it's easier for a self-teaching programmer to overcome this. Even compared to when I went through uni in the mid-2000s, it's ridiculously easy to get the material that would cover an undergrad's CS education. There's no need for a self-taught person to be caught short in an interview on not knowing what a linked list is, or the basics of algorithmic complexity. I could probably put together a list of 10-20 Wikipedia articles and Khan videos that, if you were to read and watch until you understood, would cover you for the vast bulk of CS-related questions you're likely to hit in an interview.