Skip to contentSkip to footer

Senior Network Engineer Interview Questions

Salaries
Interviews

1,039 senior network engineer interview questions shared by candidates

Networking: In & out - OSPF, BGP, Multicast - PIM SM/DM/Anycast related, Low latency, DC/ENT design questions, Protocol headers etc. Basically, L1-L4 focussed inside out. Programming: Python - lists, dicts, sets, Tuples & other Py data structures Cannot tell the exact questions - but parsing o/p, ip addresses related Programs Lots of Behavioral questions, Situational, what makes you tick, conflict resolutions, challenges faced in your roles so far, how do you respond in so & so situations etc. I enjoyed the interview process at Tower Research, interviewers are very professional, detail-oriented. Unfortunately, I couldnt cut to the final list.
avatar

Senior Network Engineer

Interviewed at Tower Research Capital

4.1★
Jun 22, 2019

Networking: In & out - OSPF, BGP, Multicast - PIM SM/DM/Anycast related, Low latency, DC/ENT design questions, Protocol headers etc. Basically, L1-L4 focussed inside out. Programming: Python - lists, dicts, sets, Tuples & other Py data structures Cannot tell the exact questions - but parsing o/p, ip addresses related Programs Lots of Behavioral questions, Situational, what makes you tick, conflict resolutions, challenges faced in your roles so far, how do you respond in so & so situations etc. I enjoyed the interview process at Tower Research, interviewers are very professional, detail-oriented. Unfortunately, I couldnt cut to the final list.

Telephonic - very cool, basic screening on background experiences, what is your future plans, have you received any awards earlier, how did you hear about Astir IT, What would be your contribution to your company in future
avatar

Senior Network Engineer

Interviewed at Astir It Solutions

4.1★
Mar 1, 2017

Telephonic - very cool, basic screening on background experiences, what is your future plans, have you received any awards earlier, how did you hear about Astir IT, What would be your contribution to your company in future

The coding test consisted of two questions. I had one hour to complete each. I did not complete the first one in an hour. I think it is possible to complete it in an hour if you don't have to look up methods and arguments on the internet and if you complete the code in the first 1/2 hour to 45 minutes and debug/polish in the next fifteen minutes. My solution, in my IDE was 150 lines long, including comments and white space. if you omit these you can save some time, but since I do not know if Roblox sees the code I did not know if I would be judged on style and documentation. The directions were silent on this manner and I assumed they would see it and I would be judged. The second problem was not well worded. There were many details that were glossed over. The description was terse and incomplete. If I had the same problem in a face-to-face interview I would have spent the first fifteen minutes discussing the boundaries and edge cases of the problem. Given it was an online test, I did not have that opportunity. Instead, I got to work and resolved to use the testing environment to answer my questions by printing the output from the runs. The testing framework only says if your code passed or failed each test. Each test has a cryptic label. You do not see the input or output. In effect, you are shooting in the dark. You cannot debug your code using the input to gauge the missing spaces in the problem specification. You cannot even use it to see what the inputs are so you can debug the code in your IDE. After my first run, I stopped working on the problem. The test framework advised me to 'develop more careful tests'. All well and good if I knew what conditions to test. I suppose I simply could have looked up the problem on the internet, but that did not seem honest. If you take the same test, I recommend doing just that. You will be under significant time constraints to solve the problems.
avatar

Senior Network Software Engineer

Interviewed at Roblox

3.8★
Feb 5, 2016

The coding test consisted of two questions. I had one hour to complete each. I did not complete the first one in an hour. I think it is possible to complete it in an hour if you don't have to look up methods and arguments on the internet and if you complete the code in the first 1/2 hour to 45 minutes and debug/polish in the next fifteen minutes. My solution, in my IDE was 150 lines long, including comments and white space. if you omit these you can save some time, but since I do not know if Roblox sees the code I did not know if I would be judged on style and documentation. The directions were silent on this manner and I assumed they would see it and I would be judged. The second problem was not well worded. There were many details that were glossed over. The description was terse and incomplete. If I had the same problem in a face-to-face interview I would have spent the first fifteen minutes discussing the boundaries and edge cases of the problem. Given it was an online test, I did not have that opportunity. Instead, I got to work and resolved to use the testing environment to answer my questions by printing the output from the runs. The testing framework only says if your code passed or failed each test. Each test has a cryptic label. You do not see the input or output. In effect, you are shooting in the dark. You cannot debug your code using the input to gauge the missing spaces in the problem specification. You cannot even use it to see what the inputs are so you can debug the code in your IDE. After my first run, I stopped working on the problem. The test framework advised me to 'develop more careful tests'. All well and good if I knew what conditions to test. I suppose I simply could have looked up the problem on the internet, but that did not seem honest. If you take the same test, I recommend doing just that. You will be under significant time constraints to solve the problems.

Viewing 921 - 930 interview questions

Glassdoor has 1,039 interview questions and reports from Senior network engineer interviews. Prepare for your interview. Get hired. Love your job.