Me postulé a través de una recomendación de un empleado. El proceso tomó 1 semana. Acudí a una entrevista en Meta (Dublín, Dublín) en abr 2025
Entrevista
Tough interview, not much equivalent feedbacks. After finishing a simple online assessment, I booked a date two weeks later to have time to prepare. I got turned down after the first networking and coding interview, and the coding question is a bit hard for a network position (Leetcode medium). I have to say for this to have been a "New Grad" requisition the tech questions that were asked were very high-level. The interviewer kept asking me questions in depth without guidance, which was very challenging.
Preguntas de entrevista [3]
Pregunta 1
A brief self introduction, followed by asking 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). Why can't we use OSPF to connect all the systems together, and what is unique about BGP? What is autonomous system? How is the routing information exchanged? What's the difference between iBGP and eBGP peers? How does BGP differentiate between external and internal peers? How is a BGP session established? How to prevent loopback? How to control inbound/outbound traffic? Is there any inspection before sending a route to a different neighbour, by the sender or receiver?
Given a scenario of experiencing network performance issues such as latency and packet loss. What are the possible reasons for these issues? What steps can be taken to narrow down the issue?
Coding interview: An adapted version of the Leetcode "Battleships in a Board", returning all coordinates of a battleship by placing bombs. The interviewer kept asking me the solution of dealing with multiple situations, and I spent a long time understanding the rule of the game, since I have never played such game before.
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.
Me postulé a través de un reclutador. El proceso tomó 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?
