I have mixed feelings about this interview. I have received call out of the blue and technical recruiter asked me if I'm interested. He was polite and explained what they were looking for and asked me that there are multiple roles available. He asked me to focus on design patterns and concurrency since my experience is 11 years. I have asked for 20 days to prepare which he agreed. I was bit spectacle that the process will be smooth since I asked them to wait for 20 days. I have read a lot of interview experiences on this site which suggests that their followup and feedback process is not very efficient. Luckily for me it was not the case, the interview as well as feedback was quite effective and within acceptable time limits. Ok, so as for interview, I was asked to look at code repository and correct/write test cases. Which I found bit overwhelming since understanding the code repository and problem and then find place in code to fix the issue is bit difficult (specially when someone is continuously watching your screen). It was suppose to be peer programming but interviewer was no where close to being a peer programmer. He was criticising each time you fix something in code. I know may be he was trying to understand my thought process but he should consider the code repository size and pressure which the candidate is in during interview and guide the person. I have suggested him to discuss all the questions so that if I can not fix them all at least he gets my thought process which he declined and said let's finish the current problem. Which is not a great thing to do. Candidate can find for example problem 2 difficult but problem 3 easy to solve (which he never got a chance to talk about, since he was stuck on problem 2). Also, fixing code in that repository should not be the only thing to check. Interviewee could spare some time 10-15 mins to talk about design pattern, concurrency, Java features, TDD etc. If interviewee doesn't ask any questions other than fixing code in that repo, then there is hardly enough you can do to prove that you are worth hiring for. Prepare for TDD, writing test cases and make yourself use keyboard shortcuts so that you can move around the code quickly.