The first "technical" telephonic round interview was just a formality. I went ahead to see what else they have to ask in next rounds and majorly for testing the waters. Come the presentation round and It was 10 minutes past the time set for the interview as I'll see someone relevant to the Interview that evening. The overall process gives one clear sense of them expecting you to be a robot. Most of the questions were never about how you approach the problem and no check on your thought process as to why a particular thing is done the way it is, and made it to the RFC. The sheer reliance only on a standard published RFC and expecting someone to rote-learn every word of it and keep on chanting it for years to come and stay "relevant" gives me jitters. The presentation is a good way of them making sure you prepare, So I did. The interviewers were not interested in anything you have to say other than chanting the static RFCs and some goggly questions which you can make your way through if you think logically. I agree this profile might not need anyone good with programming syntaxes but how could someone ignore the basic programming paradigms which helped shape design principals implemented by the servers following the RFC today, A straight out NO on any discussion of programming paradigm simply tells either they are unaware of it or really don't care about them. Working under this job profile must be very much like using the API and who cares about the implementation/design constraint which compelled the APIs to change in the past, you just go ahead and use the API haha. I would like to thank the panel for their time and letting me know that "Someone from the HR will get back to me". I am glad no one has come back with a feedback, What else to expect from a company initiating a robot search initiated by yet another robot.