Well @Bradley, I do understand that after a certain level of experience you may find it offending solving these questions but that's not the goal. If you are hands-on with coding, you can easily solve these problems but if you struggle with solving these, it means you are a bit rusty and not really doing coding everyday.
It doesn't matter to me how easy the questions are to answer. To me:
The question is trying to verify that I know how to do trivial and/or esoteric operations off the top of my head, which lets be honest, who has ever had to reverse the words of a sentence? Likewise, who hasn't had to strip bad characters out of a string?
The interviewers care about my rote memorization, which has nothing to do with being a good developer.
The company put someone in charge of interviewing that isn't a developer and they pulled questions off the internet thinking this is what makes a great developer.
The person in charge of hiring is too busy or too lazy to put the time into determining if a long list of candidates are a good fit for their organization, so they use this as a quick way to weed out candidates in round one. Mission successful; if they're not going to put the time into selecting quality candidates then right off the bat I'm not too excited about my prospective coworkers, nor the support I can expect from the organization.
What I'm saying is that a company asking this type of question tells me all I need to know about that company.
About the most I'll do is some sort of take home project and discuss at the interview: at least then I can either use a language or library I haven't used in a long time or learn a new one while I'm doing the project so that I'm not wasting my time.
Exactly! Job interviews are a two-way thing. Or at least they should be.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.