Hacker News new | past | comments | ask | show | jobs | submit login

Where are you interviewing? Are you putting tricky restrictions like you can't allocate a second array and other things like that?

I recently had 2/5 candidates with Master's degrees in CS unable to give me a number in hex. I didn't ask them to write a program to do it, just to include it in the email subject when replying to a posting. Another 2/5 of them gave me awful code to do it. It's kind of sad.

I interviewed at a very large corporation. 3-4 interviews a week.

We accepted any correct solution.

You've said correct twice, but what do you mean by it? Do you give a spec they have to meet or a test set to compare against? Must they handle encodings/Unicode, or fail predictably in edge cases? Or are you talking about characters swapped, even/odd lengths/ empty strings, that's all?

Oh, we usually ask a very simple version - function to return a reversed string that's passed as a parameter. It consists of English letters, it's not blank. You're not allowed to use the standard string reverse function/method.

It never gets to edge cases. Most people can't even write the simple version.

I'm pretty sure nobody can write the unicode-safe version during the interview, even the smartest developers I've worked with (I guess that depends on the language though).

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact