Skip to content

Instantly share code, notes, and snippets.

View pachchigarsnehi's full-sized avatar

Snehi Pachchigar pachchigarsnehi

  • Mountain View, California
View GitHub Profile
@pachchigarsnehi
pachchigarsnehi / README.md
Created May 24, 2024 15:28 — forked from akshatgit/README.md
Notes for Meta Production Engineer Intern Systems Round

I have received Production intern offer from FB, and while preparing for it I could not find many resources to prepare for the systems interview round. Hence, I decided to create my own preparation material. If you find any error, feel free to send a PR to improve the notes. I found these questions from this blog and I referred to OS book by Tanenbaum.

There are 2 rounds for PE internship, the first is the coding round and second systems round. In the coding round the questions are of easy to medium leetcode level. In the systems round, the main focus is to check the OS knowledge, with a particular focus on Linux based concepts. The following are the set of questions I had prepared, try to get an in-depth understanding of how and why a process is designed in such a manner.

What happens during the boot process from

@pachchigarsnehi
pachchigarsnehi / FB-PE-InterviewTips.md
Created May 24, 2024 15:27 — forked from ameenkhan07/FB-PE-InterviewTips.md
Facebook Production Engineering Interview

What to Expect and Tips

• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.

Systems

More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).

Design/Architecture 

Interview is all about taking an ambiguous question of how you might build a system and letting