The recruitment process was initiated through shortlisting based on CGPA, which was somewhat strange. Then it was followed by a presentation about the role. They were very clear that this is not a code-oriented job but an on-call, customer-facing support position. The tone at this session was somewhat mean, as they told directly those people who were interested in coding that they had to go. The computer networks assessment online contained MCQs about Computer Networks, Operating Systems, virtualization, hypervisors and some basic commands in Linux/Unix. This section is simple when you are well-versed with the basics of CS. The technical interview was split into the first technical interview (approximately 30 minutes), which involved resume and projects as well as computer networks and OS basics. They anticipated good conceptual perception, particularly application knowledge. The second technical interview was in front of a more senior panelist and was much more challenging. It began with questions on cloud vs. their own products, a network design and troubleshooting exercise, like Cisco Packet Tracer. They provided a situation in which you were to troubleshoot the problems with switches/routers and use Linux network commands such as curl, telnet, ping, traceroute, etc. The test was highly practical and obviously aimed at testing the practical troubleshooting skills. Surprisingly, the interviewer also pointed out that this position is not to be shared by people who like coding. As a matter of fact, he even posted his own experience of struggling to leave this kind of support position to a development job. The general atmosphere was that they are seeking individuals with no interest in coding whatsoever. All in all it was a good experience but certainly a feelings evoking one among freshers. In the second interview, I also had an inkling that maybe there was a certain regional bias in the selection of the candidates -although I cannot say that it was so, the list of final selection appeared to show that.