Facebook phone interview
I have a first round phone interview with Facebook coming up! Any Tips?
study stupid sort algorithms and other things you never need to memorize on the job
I was asked back tracking so make sure you get your hands dirty with it
Clearly restate the question asked either in your own words or in the interviewers words. You will be surprised by how many times the question is never clearly stated or indirectly stated via bad examples and you get pigeonholed.
Ask what they expect the person taking the role to achieve in the first 3 months, 6 months and 12 months.
It's totally a standard phone screen. You'll call in and solve a problem or two on a shared editor.
From the FB's perspective, we're simply looking to weed out obviously unqualified candidates. The problem will probably be pretty simple. The biggest tip i have is to use the language you know best. You don't get points for using a cool or trendy language. FB is a very pragmatic culture. I've given strong hire decisions to candidates who interviewed in R.
What do you mean by obviously unqualified. In what way?
The vast majority of applicants can barely write a for loop. The screen is a way to make sure we don't waste time and money on applicants that have zero chance of making it through a full interview on site.
Please, please read the entire problem before answering. I've done countless interviews where the candidate didn't read it and basically implemented the wrong thing. Also, ask questions. The problem are built to be dug into. Don't assume everything you need for your solution is obvious. I'll often see a solution I wasn't expecting (this is totally cool), but without covering edges specific to that solution. Don't be scared to ask about the scale, bounds, potential failures, etc
This is good interview advice in general, but in my experience our screen problems are generally simpler and well defined.
Generally yes, but defining bounds is a must... Most candidates aren't experienced enough to define correct bounds for themselves and gate those bounds in their code, handling them properly...
Relax and do your best
What’s the likely hood of a dynamic programming problem during phone interview?
Don't stuck.
What do you mean?
It was probably a typo. "Don't suck"