Additionally, the farther out from a candidate's graduation the interview takes place, the less their GPA matters compared the work they have done since they left. If you have a great resume and come highly recommended I'm not very concerned with how well you did in your calc 2 or operating systems courses.
Or are you referring to something other than the standard coding interview?
Candidate B dropped out after three years. But they've done some quite interesting side projects, they know a bunch of languages, and stuff outside the coursework, and the courses they took were the harder ones.
Generally, and for openers, 'A' is gonna struggle explaining what the heck an XOR is, while 'B' is going to toss off the answer in a couple of seconds. And their skills just keep diverging from there. I'll have confidence that 'B' will keep growing and learning, and they're going to be a handful, while 'A' is going to need to be told what to do, and that will be tiresome.
This ^^^ is kind of a parody, but you can tell what I'm looking for, early on. (People with more experience, I look for significant contributions to hard problems, and I'm really interested in how people decide what to work on).
In a small company it's pretty easy to avoid the automatic filters of large companies, the ones that screen out applicants without degrees, or from "wrong" universities, or who have low GPAs. Most of these metrics don't seem to matter in the long run (but they are easy for HR types to apply, so they do).
GPAs and such probably matter in government orgs, or places that are very strict and hierarchical. You probably want to avoid places like these anyway.