About 5 minutes after the call ended, my jaw dropped open and I slapped my forehead. To find the anagrams of a word, just parse the set and remove any words that are (a) the same length and (b) contain the same numbers of each letter in the original.
Fizz buzz. And I made it like 1000x harder.
A generous interviewer would say, "Well at least he knows recursion and can do it on the fly in a stressful situation". But this is Facebook and they don't have to be generous. I gave them a reason to say "no" and then they said "no".
But as for "dysfunctional jokes", I have to agree (and you can tell from my OP that I have plenty of experience with it). Asking someone to code on the fly is like asking someone to write a novella on the fly. You need focus and concentration. By demanding it with someone breathing into your ear the whole time, you're simply giving those who are better able to handle pressure an advantage and those who can't a disadvantage. If this were a bomb-diffusal position, you'd want to filter for that. But this is coding, so what should pressure-handling matter?
I mean i never research or think about shit. i just code it man and release it like a boss because thats how coding in the real world works. You better be quick on your feet if you want to get into the big guys. This is real world coding after all :) ...
haha
Did you mean memoization, the optimization technique where you cache intermediate results? Or were they literally asking you to memorize and recite minutiae over the phone?
I always get these two words mixed up, and it doesn't help that Firefox doesn't think "memoization" is actually word.
For example implement some specific algorithm. If you remember some of that algorithm or memorized it you are good. Otherwise you suck at development because you haven't had the need to implement that algo ever in your career..
The rest of the story? A couple years later I had a chance to talk with the hiring manager while he was applying for a position at a place I was working - seems the person HR picked led to their whole unit being disbanded because they failed so miserably. He felt he had to take some of the blame for not keeping a closer eye on the person, but still...
I've found this to be true in a small number of my experiences. There are certain positions I interviewed for where my history was 100% in line with their needs, the interviews all went well and I should have gotten the job. But then didn't. Have no idea why not.
Unless theres some racism going on since they can see my picture. Thats the only way they can differentiate between 2 people who have the same score.
I usually add these companies (and if possible, the team in question) and keep track of the position and project as well. They're not going to like it when the chip on my shoulder becomes too big and I decide to compete against them.
Just don't become a super villain like Guy Pierce did in Iron Man 3
My last interview at amazon went like this:
Stupid trick coding question over the phone that I did not understand at all. Followed by 3 memorization questions. followed by one question I felt was valid and i know i got it right.
I was being interviewed for a specific product that was right up my ally. I could literally build what they had built easily, but they never once asked questions related to the product or my experience.
I looked at the product a year later and basically nothing has been done to it.