My lifetime's first interview.

I've just finished one tech interview with a engineer in Facebook, who is working with the search bar atop the whole webpage. I've got to say this interview went kinda breezy, but I was still nervous because this is my first time as an interviewee. The interviewer was very nice. She asked me some typical questions about information verification in a interview. Here is the list:




1.Why Facebook?
2.What is your favorite project?
3.What is your role in this project?
4.What kind of difficulties have you come cross in your projects?
5.What protocol do you use in your app?

I have prepared for those questions, of course. But real time interview is different from self practicing. I might not express as clearly as I am assumed to be. Anyway, we spent approximate 14 minutes on those problems. And then we went on to the coding part.

Traverse a binary tree and print the node values layer by layer. A newline starts when a layer is finished.

This is problem is an easy pie surely. BUT I DID BADLY ON THIS ONE. At first, I made a mistake when I tried to use a queue to solve this problem. Instead of saying using a queue, I said using a stack. Though in the following coding stage I was always referring to a queue, but the interviewer thought I was using a stack. So? I found this mistake when she finally noticed me and I told her the mistake.
What is worse, I made an another big mistake coding this program. My program was trapped in a dead loop and I was not aware of it until the interviewer pointed in the end. She was giving out hints to my mistake all the way but I did not get it. What a pathetic day! This is such an easy pie for me in regular days. However, I am now 'waiting' for the declining letter.

I asked how engineers in Facebook are assigned in projects and the interviewer answered the question very patiently. Nice interviewer, but poor interviewee, totally.

Anyway, this is my first interview in my whole life and I'll never forget this one. Now I've some sort of experience in interviews, and I also learned the following stuff from this interview:

1.Questions are common and they won't be harsh on the resume especially you are in an interview for internship.
2.Coding phase will be easy too as long as you are composed and try to grab every piece of information from the interviewer. If she/he told you to test your program, find the most trivial test case to run your code manually, you will find your problem easily( dead loop, access violation, etc. )