I received a call from Capgemini HR for an interview at the ITPL location in Bangalore on April 30, 2016.

There were many other candidates who came for the interview. The interview process went like this:

The interviewer appeared to be in his late twenties or early thirties, and seemed somewhat desperate.

Interviewer: "Is this your resume? Do you know how to write a resume? You haven't written anything about technology."

Me: "Is there anything I forgot to mention? I have mentioned everything as far as technical specs are concerned."

Interviewer: "Tell me how your application works."

Me: "My application gets requests from different resources like web services, HTTP/XML, and sockets."

Interviewer: "Is a socket different from HTTP?"

Me: "Yes. A socket can bind between particular ports, which is not applicable to HTTP. If a socket is closed on the server, you cannot send a request to the server."

Interviewer: "Both are sockets only. As per your explanation, every network element is HTTP/HTTPS based and connected to a socket, just like email or whatever."

Me: ". Then why do we have different protocols? We could send all information using just sockets. As far as I know, for email, we have SMTP/POP3 protocols, and for different JMS providers, we have different protocols."

Interviewer: "No, listen. Every such thing is connected to a socket only."

Interviewer: "You have mentioned about a bulk system. What does your bulk system do?"

Me: "For the bulk application, I receive bulk files in a particular server location. I take that file, break it into small chunks, process each and every record, and send it to the downstream system in XML format."

Interviewer: "What do you mean by this? As far as I know, this is shell scripting with a cron job that works in a bulk system and processes everything."

Me: "For us, the traffic is high, and if a file does not have proper data, we have to take proper actions for those records."

Interviewer: "No, that's wrong. Tell me how you are creating XML."

Me: "I am using the XStream API for creating XML. In a few places, I am also using DOM and SAX parsers."

Interviewer: "Which Java API? I am asking you."

Me: "It's XStream that I am using."

Interviewer: "There is a Java-X something API that is provided by Java. I was asking about that."

Me: (stunned)

Interviewer: (folded my resume) "You can leave."

Me: "Sir, can you tell me what your actual requirement was here...?"

Interviewer: "Core Java."

Me: "Then, I have been working for the last 4 years and have not come across such an API. Anyway, thank you."

This was the worst interviewer I have seen in my career.

For his information, my resume was a copy of a top resume in IT, as featured in Google's Business Insider with the title "19 Reasons Why This Is An Excellent Resume."

Whatever his assumption was, he was forcing only that. Instead of getting such a bad mentor who has improper knowledge, I am happy with my client.

This kind of interviewer is degrading Capgemini's level.

Is HTTP and sockets the same?