You'll start with a quick tech quiz with the recruiter over the phone.

Then, two phone screens will be scheduled:

• One on coding (1 hour)
• One on systems (1 hour)

Once you pass the phone screens, you'll schedule an on-site visit, which consists of five interviews:

• Systems (45 minutes)
• Networking (45 minutes)
• Cultural (45 minutes)
• System architecture (45 minutes)
• Coding (45 minutes)

If you are not from California, they will fly you to SFO, preferably on a Monday.

The quiz was pretty simple; you'll be asked basic questions about Linux.

Here are some of the questions:

• Battleship game: Write a function that finds a ship and returns its coordinates.
• Write a script that connects to 100 hosts, looks for a particular process, and sends an email with a report.
• What is a filesystem? How does it work? Explain file permissions, properties, and file types. A write operation failed with an error; how do you figure out what happened? What's a signal, and how is it handled by the kernel? What's a zombie process?
• Talk about an iostat output (what do user vs. system CPU load mean, what does iowait% mean, cache vs. buffers, why do we need caching, how much cache is needed, how can disk performance be improved, and where is the bottleneck).
• How do TCP and UDP work? Describe what happens when a client opens a web page. How does DNS work? How does HTTP work? How does a router work?
• Various questions about your current experience. Talk about a conflict situation and how you handled it.
• How would you design a system that manipulates content sent from a client (e.g., clean bad words in a comment post)?
• Write a function to sort a list of integers that looks like this: [5, 2, 0, 3, 0, 1, 6, 0] -> [1, 2, 3, 5, 6, 0, 0, 0] in the most efficient way.