Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Meta (Menlo Park, CA) en ene 2021
Entrevista
Role: Rotational Production Network Engineer
I was contacted by a recruiter on LinkedIn and had a brief exploratory call. After which I had a phone screen coding round (video). After clearing that, I had another phone screen round - Networking.
The interviewers were polite and the interview process went smooth.
Preguntas de entrevista [1]
Pregunta 1
Round1 - Coding
I was asked only one question - Dinosaur problem (parsing from two csv files)
Follow-up questions:
What is the time complexity? What is the maximum size of the dictionary?
One of the Dinosaurs present in first csv file is missing in the second csv file, how would you check that in the program?
What if there is some column missing in the csv file, how would you handle that? Focus on the error handling techniques - try and except.
Round 2 - Networking
Briefly tell me about BGP.
Why do we need the open messages, why can't we use only the TCP 3-way handshake to send data? What are the reasons for peer connection to fail?
Why is BGP used as an external routing protocol instead of OSPF or ISIS? What makes BGP special?
Difference between eBGP and iBGP peers? Loop prevention mechanisms?
What are the categories of BGP attributes?
What are the well-known mandatory attributes?
Why is Origin attribute mandatory - why does it have to be present in the update messages?
How does BGP choose the best path? Briefly explain all the attributes for path selection.
You have 2 hosts connected by a switch that are just booted up. How do the two hosts communicate?
What is the need for the switch to make note of the interface and MAC address?
How does this work in IPV6?
Full loop interview with 3 parts: Networking, SWE, Behavioural. Each 60 minutes. Networking interview: Asked about TCP, BGP, IP protocols, also about ARP protocol and Ethernet. SWE was a classic Meta SWE interview.
Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Meta (Londres, Inglaterra) en ago 2025
Entrevista
Disappointing Experience – Strong Performance but No Offer Despite Positive Feedback
I recently interviewed for a Network Production Engineer position at Meta (London). The process included a screening round where I successfully solved both coding problems:
• Problem 1: Battleship problem.
• Problem 2: Reading a file and finding repeated occurrences of words, along with explaining time and space complexity.
The first technical round covered networking fundamentals (TCP/IP, basic network topology, H-S-R-S-H communication, packet drop analysis, TCP flow control, and congestion control). I performed well in both rounds and received positive feedback from the interviewers.
However, five days later, I received a rejection email, stating they were “moving forward with other candidates.” Seeing the same position reposted on LinkedIn shortly afterward was frustrating and disheartening.
When I asked one interviewer about Meta’s work-life balance, his response felt dismissive and unprofessional, which added to the negative impression.
Advice to Management:
Please provide constructive feedback to candidates and maintain professionalism during all interactions. Transparency in the hiring process would improve candidate experience significantly.
Preguntas de entrevista [1]
Pregunta 1
Problem 1: Battleship problem.
• Problem 2: Reading a file and finding repeated occurrences of words, along with explaining time and space complexity.
The first technical round covered networking fundamentals (TCP/IP, basic network topology, H-S-R-S-H communication, packet drop analysis, TCP flow control, and congestion control). I performed well in both rounds and received positive feedback from the interviewers.
The process began with an online assessment covering networking, Linux, and coding fundamentals—15 MCQs in 16 minutes. Topics included TCP/IP, BGP, Python, troubleshooting, etc.
After passing, I moved on to two 45-minute technical interviews:
Coding Round: Focused on file handling, data structures, Big-O notation, and common algorithms.
Networking Round: Scenario-based, covered optical networking, switching/routing, and L0/L1 troubleshooting.
Pros:
Challenging but fair technical questions.
Interviewers were professional and respectful.
Process was well-organized and moved quickly.
Cons:
No detailed feedback post-interview.
Some questions were very Meta-specific with little public prep material.
Overall:
Great opportunity to demonstrate both software and deep networking skills. Would recommend preparing in-depth for both domains—especially optical layer concepts.
Preguntas de entrevista [1]
Pregunta 1
Walk me through how you'd troubleshoot a server that's not reachable.
What happens when you type a URL in a browser?
How does BGP work and when would you prefer it over OSPF?
Describe a time you troubleshooted a complex network issue.
Explain how TCP handshake works.
What's the difference between TCP and UDP?
How do you find a memory leak in a Python script?
What are common causes of high CPU usage on a Linux server?
Explain optical networking and the challenges at Layer 0/1.
How does DNS resolution work behind the scenes?
