Meta Network Engineer Interview Questions

Not good. It's not as expected as i got. Not much equivalent feedbacks. I didn't like the experience. Google has way better interview process than Facebook. The recruiter called me first, then held an initial conversation and then goes to coding interview round. Took me to the production Engineer, 10 years of experienced guy. The level of the Questions were amazing but couldn't land up

Well, It was a good experience over all. But a little disappointing. The process be like.. First initial interview call with recruiter Second coding interview 2 Technical interview back to back HR and Leadership

The interviewing process was alright. A recruiter reached out to me to see if I was interested and I accepted the opportunity to interview. I must say for this to have been a "New Grad" requisition the questions that were asked were very high-level and you would probably want to have some previous experience with being a network engineer (which is not the case with MANY new graduates). In the job description, it did not specify that you needed to have advanced networking knowledge which was a little misleading. In the description, it was mentioned that you needed to have a foundation of networking (which I did). But once you get to the interview process, you will notice the questions aren't geared towards a new grad at all; but rather for someone who has 5+ years of network engineering experience. Overall, I feel like I wasted my time and this could have all been avoided if they would have specified in the job description that you needed advanced networking knowledge. I know this is Facebook and they are competitive - so a challenging interview is expected, but they should probably not mislead prospective candidates with very broad job descriptions and expectations.

Tough Interview. Need a deep understanding of TCP/IP protocol stack, with all small details. They focus on finding if u really know your networking stuff. BGP OSP Python knowledge is also needed in a good level.

Started off with a technical interview with 2 simple-average coding problems that I solved. Then the next interview was an interview that specifically pertained to networks. This one was much harder than the previous interview.

Had - a brief call with my recruiter who asked some basic python and networking questions - Coding interview which lasted 45 mins long - Easy - 45 Minute Networks Interview. Medium - Hard.

Not bad. It was overall smoothly coordinated. Interview process went well. But after the result wasn't positive I had tried to get feedback but couldn't get anything back. That was a little disappointing considering the stature of the company

After the greetings, you'll answer simple behavioral questions through email. This is similar to a phone screening imo. Questions were like, why are you a good fit, your work authorization, and any deadlines they have to be aware. Then there is another round of online questionnaire, but these are technical questions. You have to answer about 20 questions within 20 minutes. Then comes the coding interview. I think it is pretty standard and comparable to any other company's coding interview. But, your performance expectations are high, since they are Facebook and very competitive. I didn't pass this stage nline questionnaire Coding interview

I received an email from Facebook recruiter for the network engineer job opportunity in Dublin or London. I went ahead and scheduled the call, During the call, she explained the process to me, the First interview will be coding, second will be networking. These 2 are screening interviews, if I have done well I will be called in for the final interviews which will be back to back (2 networking, 1 coding, and 1 behavioral) interview. post which she also asked me basic questions about coding, Linux and networking. what is list, tuple, etc, why do we use big o notation? where does DNS information get stored in Linux? what is split horizon, route reflector? Also, she mentioned that the hiring level and team will be decided post 2 screening interviews. And I can take as much time I want to prepare for the interviews. for the coding interview recruiter will provide a hell of lot of preparation material. But I would suggest practicing a lot on leet code In my coding interview, I was asked 2 questions to solve and the time limit was 45 minutes to solve both questions. 1. Split array in 2 equal sum contiguous sub-arrays. 2. The dinosaur question. My coding interview went perfectly and was provided feedback on the very next day in the morning. This was the first-ever coding interview of my life and it went perfect. For the networking interview, I was advised by the recruiter to prepare in-depth for BGP/TCP/IP protocols, Routing/switching, Basic MPLS/OSPF, Troubleshooting, Monitoring, Hardware knowledge, and Automation. And was also advised that the interviewer will be looking for my boundaries of knowledge in each topic. For my networking interview, the interviewer first asked about my experience and the most exciting project of my life. Then he started off with networking protocol. He also asked which protocol am I most comfortable with and I went ahead with BGP. The interviewer started with basic BGP questions, his questions were too generic (this is the catch). I had to go ahead and explain each and everything that I know about that topic. I explained each topic in BGP in detail. how ebgp and ibgp work, how they are different. what is AS number, how as numbers are used by service providers, how BGP can be used by any organization without purchasing AS number. Then the attributes, explained each and every attribute in detail, how they are used to influence inbound and outbound traffic and how loop avoidance work in eBGP. Then the interviewer started digging deeper into iBGP, how loop avoidance work in iBGP, what is route reflector, how it works, how split-horizon works, how route reflector cluster works (V.V. IMP). what happens in case of equal metric paths, how ECMP works in BGP (V.V IMP), what is hot/cold potato routing. Then he started questions more in terms of how packets travel, what happens to the ethernet frame when it travels across the network, how a switch work (ARP, CAM). how 2 hosts communicate via a switch. Then how 2 hosts communicate via a router, what happens to the IP header when it travels across the network, how a router works. How can I trace a packet in a network, I explained how tracert works hop by hop (interviewer was expecting the answer in terms of tracing multiple paths to a destination) how would you troubleshoot a slow web browser? I explained troubleshooting in detail as what steps can be taken to narrow down the issue (if the issue is in-network or server or application on server or its a client end issue) and then what I can do to troubleshoot network or server or server applications, mentioned about how I can use SNMP (should know a tool for SNMP) to troubleshoot server, how I can use Wireshark to troubleshoot latency/jitter/zero window events. This entire discussion took place in 45 minutes. He asked nothing about automation, in the end, I asked my questions about Facebook tools (NetNORAD, Open/R) which the recruiter mentioned to learn about before the interview. The feedback for this interview came after a week (the more time to arrive feedback, the less chance of getting selected), mentioning my advanced networking experience is not at the level it is required at FB, but the interviewer was impressed with my networking knowledge and skills. This feedback came to me as a big shock and the feedback felt like "I didn't like your face so I am going to give any XYZ reason to reject". I was quite satisfied with the way I explained each and everything in depth. Then I realized that I talked about the 'ECMP' and 'route reflector cluster' only at a basic level, considering the time limit we had, and also I was not expecting to talk about advanced topics in depth at this stage, and this is where I got hit.

1 Coding Phone Screen 1 Network Phone Screen 5 Onsite rounds - 2 Network, 1 Coding, 1 System Design, 1 Behavioral Happened over 2 months at my own pace. Recruiter reached out in LinkedIn