"What's the difference between a procedure and a function?"
Instantly weeded out 98%. Really what you are looking for is work ethic. If I pay you will you work hard. That can't really be determined in an interview.
Is that bad?
I'm tired of all this BS really.
I did know that a language like that must have a string function for it, the first result of my search was a docs.microsoft.com page with the syntax and examples.
I don't know C# very well either. Taking 10 minutes to research the possible solutions and their pitfalls doesn't sound like a bad thing. What's the idiomatic way, and is there more than one commonly used way? What are the performance characteristics of each way? Are there any pitfalls and caveats (as e.g. strtok in C has when it comes threads or to strings that may have empty fields)? Do these ways modify the original string or do they produce copies? Is the delimiter a single character, a string, a regex?
This should indeed be simple and quick if all you need is to speedrun to an answer through Google. If you need to be thorough and understand the ins and outs of what you're doing, 10 minutes doesn't look like much at all for someone who doesn't have extensive & recent experience with the given language.
So many ask, "How do you do X?" and the correct answer in a real job situation is always either "Look up the documentation for X, and do it that way.", or "There is a 20-year-old open-source library for doing X, so I'd use that."
I am not a walking catalog of esoteric programming knowledge. When working, I have 24-hour access to all official documentation, as well as all blogs, projects, and message boards on the Internet. The first step in solving any problem is checking to see if someone else already solved it.
The same goes for the brain teasers. If you can look up the problem on the Internet, I probably saw it first. Your original, non-plagiarized riddles, please, or don't bring it in to the interview.
Like most people, I am not looking for perfection, I am looking for a basic level of competence (I've had people who took 10 minutes to split a string in C# by a delimiter) and also to see how they think, how they work under pressure, whether they ask good questions instead of assuming things.
At the moment, these are mostly the best ways to tell if someone is a good fit.