I was initially contacted via LinkedIn by an internal Facebook recruiter who specialized in this role. I was impressed with the recruiter's technical knowledge, which is always a good sign, and agreed to proceed with the screening and interview process.

The process consists of five steps:

• Call with the recruiter about the position
• Phone screening with a few trivia questions regarding systems administration
• Cooperative coding phone interview
• Systems phone interview
• On-site interview

The call with the recruiter focused primarily on the position description and duties, and on assessing whether both parties felt it was a good fit. The phone screening, also conducted by the recruiter, involved a few questions that anyone with experience administering Linux for an organization would be able to answer readily.

The coding interview utilized a collaborative editing tool, allowing both parties to see what was being typed in real-time. The coding questions were not typical abstract data manipulation problems, but rather those requiring systems knowledge. In my case, they were most easily addressed with shell scripts.

I did not complete the systems phone interview, as they considered my programming interview strong enough to skip this step. I was informed this is not uncommon.

The on-site interview loop comprised five 45-minute segments: Programming, Systems, Networking, Solution Architecture, and a meeting with the Manager (not necessarily in that order). Additionally, there was a lunch with the initial recruiter and a brief chat afterward with a different recruiter who handled the financial and logistical aspects of the interview and negotiations.

One striking observation throughout the entire process was that everyone I spoke to—and I mean everyone, as I asked them all—absolutely loved working there. Every time I asked someone how they liked working at Facebook, their face would light up, and they would begin listing reasons for their enjoyment. Consistently, the primary reason cited was that they liked everyone around them, felt trusted and respected, and, in turn, trusted and respected their colleagues. This was unanimously the first reason mentioned, usually followed by "and the work is really interesting."

What options do you have, nefarious or otherwise, to stop people on a wireless network you are also on (but have no admin rights to) from hogging bandwidth by streaming videos?