Phone Screening

60 minutes: 30 minutes devoted to 5 SQL questions and 30 minutes devoted to 5 Java/Python questions.

• The important thing to note is that they are not just looking to see if you can code the correct solution. They are looking at your ability to communicate your thought process clearly. So, if you code a correct solution in complete silence, that's actually a strike against you.
• They also want to see if you can code quickly. So, if you are a hunt-and-peck typist, you might want to take some typing lessons.
• They also want to see if you can take hints. If you start to veer off course from the solution, do you pick up hints quickly from your screener to get back on track?

Onsite Interview

The onsite interview consists of two ETL interviews, one modeling interview, and one ownership interview.

• The two ETL interviews will involve you writing SQL and code that mimics ETL done at Facebook. You are given a vague description of what needs to be done and are expected to ask clarifying questions to get a clear idea of what needs to be done. While you don't necessarily have to write advanced SQL/code, they do expect you to write smart, efficient SQL/code.
• The modeling interview presents a business case where you are expected to design tables and write more SQL to retrieve data for use cases.
• The ownership interview is done by a manager.

The technical interviews also double as behavioral interviews. They are looking for the same behaviors described in the phone screening. Instead of typing skills, they want to see if you can code on the whiteboard quickly as well. This is important because you will be writing a lot of code during the interview session and may run out of time.

Reading about interview experiences on Glassdoor is good preparation, so do it.