Network Production Engineer Interview Experience - Menlo Park, California
Process
The interview process consisted of three stages:
- Coding (average)
- Networking (average)
- Design (hard)
The entire process took about 3.5 weeks to complete, with one week between each interview. The recruiter and interviewers were very nice and accommodating to my speech impediment. Interview preparation resources were also provided by the recruiter.
Although I didn't get the role, the recruiter still went above and beyond to suggest other roles that fit my resume.
Questions
A Meta branch in California has 30 computers that are connected to another 30 computers in a Meta branch in the UK.
A specific computer in the California branch can't ping a computer in the UK branch but can ping the other 29 computers.
What could be the issue and how can it be solved?
Explain a 3-way handshake. And how would that play out in the 2 servers, 1 router, and 4 computer scenario?
Was this helpful?
Interview Statistics
The following metrics were computed from 3 interview experiences for the Meta Network Production Engineer role in Menlo Park, California.
Success Rate
Meta's interview process for their Network Production Engineer roles in Menlo Park, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Meta's Network Production Engineer interview process in Menlo Park, California.
Meta Work Experiences
- 4.0New Grad SalaryNetwork Production Engineer • Current EmployeeMenlo Park, California, United StatesJuly 7, 2025Pros: Base: 137000 Stocks: 37500 Annual Bonus: 10% Free foodCons: No sign-on bonus 401k
- 4.0Supportive People, Lacking GuidanceNetwork Production Engineer • Former EmployeeLondon, Ontario, CanadaOctober 7, 2025Pros: food people benefits culture communityCons: A lot of interns were left to scramble for a solution with little to no guidance.
- 5.0Meta 2021 - 2023Software Engineer • Former EmployeeMenlo Park, California, United StatesNovember 13, 2025Pros: - Easy to switch teams. - Relatively clear and transparent perf evaluation and growth path. - Eng heavy and data driven culture; less top-down. - Strong ownerships. - Flexible working hours.Cons: Sometimes it's too data-driven and lacks direction, driven by product strategy and user research understanding.
Meta Interview Questions
