Overall experience was good, recruiter contacted me through hired and setup call for 30 minutes which went well, after that I was setup for 1 hour technical interview in couple of days with one of senior software engineer, and overall it was good, however when I got response from Recruiter, I was like SERIOUSLY Response I got was that "our Engineer "Felt" that you didn't explain production troubleshooting properly and you had difficulty resolving coding problem" man seriously, production troubleshooting is open ended question, and yes I may have not answered the way you may be thinking or may be the way you work in your company but I think as interviewer you should try to focus more on person's approach and way of thinking'. 2nd I had difficulty resolving coding problem, means what parameter you have to gauge it, I had 15 minutes to resolve the issue and yes I was writing and thinking same time i.e. 1st I though to resolve it hash but than I thought it's better to go with array , do you really call it difficulty? don't you think there is something called "Thinking Process"?, (and yes in real world you think it through and come up with logic before you start coding, but not when you have 15 minutes, that time you have to think and write at same time), even if you think it through before writing, I can bet 80% you will miss something and only way is to debug the code and see what's going on and than test it with different scenario, so that's slippery slop to say Oh you had difficulty writing it. and anyone can misuse it, so as interviewer you should be clear what you are looking for and should communicate the same i.e you want person to resolve issue or want person to resolve in best possible way or want user to don't use "backspace or delete" button when writing code. other thing I asked him to let me use my IDE to finalize the code ( I wrote the logic and ask him to let me use IDE to debug and finalize) which he said OK, and if this is the case he though than definitely I was not the gay. in 13 years you become so used to of IDE that it become difficult to work on Notepad (most of code testing tools are not more than notepad). Anyways, overall it was not bad and I enjoyed it but there are something company can try to fix to train interviewer and try to choose interviewer based on candidate.