Solicité el puesto a través de un captador. Acudí a una entrevista en Meta en abr 2021
Entrevista
After phone interview with HR, Coding interview 45 mins, then after passing Network interview supposed to be 45 mins mine took 1 hour 15 mins talking one then other etc.
Interviewing people are generally ok, they try to get most out of you and even if you are stuck at something they want to know if you know other things.
I did not pass Network part as I am a practical engineer not a theorical in-memory database also I have a life and job already and do not have time to train for months for a golden handcuff in a pricy country. (It seems doable if you train for a month or two fully on theory at least this part)
Preguntas de entrevista [1]
Pregunta 1
Asked a simple file open read do simple calculation and give output question.
Asked a battleship game question.
Interview 2 about Network.
Pure teoritical, they want to know if you know BGP protocol especially in details (which I just know general and do not care to learn in detail). Asked how DNS works and asked about TCP/IP communication and how to debug if your download is slow trying to get a file from other side of the world.
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?