Earlier quoted context omitted.
I interviewed a guy the other day. CS degree. "I have a proven track record of building and leading amazing engineering teams." "Okay. What's the difference between a character and a string?" *crickets* We all have our specialities, but jesus ¢@&#ing christ: if you're interviewing for an engineering role, of any sort, you should be able to answer basic questions.
The bytes it takes up and how it can be cast? What answer would you be looking for
Possible good indicators: "I haven't written C code in a decades, but one is a byte, one is a structure" "I'd be in over my head with Unicode but.." "What are you looking to solve?"
Bad indicators: Hostility. Authoritative wrong answers.
(For a director of Product role once, I was asked the difference between REST and SOAP -- not because he cared that I knew the answer, but because he wanted to see how I could work with an engineer who was focusing on the wrong problem)