6.3 KiB

Raw Blame History

Interview Formats

The following interview formats are based on my experience interviewing with Bay Area companies. Formats would differ slightly depending on the roles you are applying to. Many companies like to use CoderPad for collaborative code editing. CoderPad supports running of the program, so you might be asked to fix your code such that it can be run. For front end interviews, many companies like to use CodePen, and it will be worth your time to familiarize yourself with the user interfaces of such web-based coding environments.

For on-site interviews at smaller (non-public) companies, most will allow (and prefer) that you use your own laptop. Hence it is important that you prepare your development environment in advance.

Airbnb

Recruiter phone screen.
Technical phone interview:
- 1 or 2 x Algorithm/front end on CoderPad/CodePen.
On-site (General):
- 2 x Algorithm coding on CoderPad.
- 1 x System design/architecture.
- 1 x Past experience/project.
- 2 x Cross functional.
On-site (Front End):
- 2 x Front end coding on CodePen. Use any framework/library.
- 1 x General coding on your own laptop.
- 1 x Past experience/project.
- 2 x Cross functional.
Tips:
- All sessions involve coding on your own laptop. Prepare your development environment in advance.
- You are allowed to look up APIs if you need to.
- They seem to place high emphasis on compilable, runnable code in all their coding rounds.
- Cross functional interviews will involve getting Airbnb employees from any discipline to speak with you. These interviews are mostly non-technical but are extremely important to Airbnb because they place a high emphasis on cultural fit. Do look up the Airbnb section of the behavioural questions to know what sort of questions to expect.

Asana

Recruiter phone screen.
Technical phone interview.
On-site (Product Engineer):
- 3 x Algorithm and system design on whiteboard within the same session.
- 1 x Algorithm on laptop and system design. This session involves writing code on your own laptop to solve 3 well-defined algorithm problems in around 45 minutes after which an engineer will come in and review the code with you. You are not supposed to run the code while working on the problem.
Tips:
- No front end questions were asked.
- Asana places high emphasis on System Design and makes heavy use of the whiteboard. You do not necessarily have to write code for the algorithm question of the first three interviews.
- All 4 sessions involve algorithms and system design. One of the sessions will be conducted by an Engineering Manager.
- The last session will involve coding on your own laptop. Prepare your development environment in advance.
- Regardless of Product Engineer or Engineering Generalist position, their interview format and questions are similar.

Dropbox

Recruiter phone screen.
Technical phone interviews:
- 2 x Algorithm/front end on CoderPad/CodePen.
On-site (Front End):
- 2 x Front end on CodePen. Only Vanilla JS or jQuery allowed.
- 1 x General coding on CoderPad.
- 1 x All around. Meet with an Engineering Manager and discussing past experiences and working style.
Tips:
- You can code on your own laptop and look up APIs.
- Dropbox recruiters are very nice and will give you helpful information on what kind of questions to expect for the upcoming sessions.
- One of the front end sessions involve coding up a pixel-perfect version of a real page on www.dropbox.com. You'll be given a spec of the desired page and you'll be asked to create a working version during the interview.

Facebook

Recruiter phone screen.
Technical phone interviews:
- 1 or 2 x Algorithm/front end on Skype/CoderPad.
On-site (Front End):
- 2 x Technical coding interview on whiteboard (Ninja).
- 1 x Behavioural (Jedi). Meet with an Engineering Manager and discussing past experiences and working style.
- 1 x Design/architecture on whiteboard (Pirate).
Tips:
- You are only allowed to use the whiteboard. No laptops involved.
- For the Jedi round, you may be asked a technical question at the end of it. Front end candidates will be given a small HTML/CSS problem nearing the end of the session.
- For the Ninja rounds, you may be asked one to two questions depending on how fast you progress through the question.

Google

Recruiter phone screen.
Technical phone interview:
- 1 or 2 x algorithm on Google Doc.
On-site (Front End):
- 3 x Front end on whiteboard. Have to use Vanilla JS (or at the most, jQuery).
- 2 x Algorithm on whiteboard.
Tips:
- You are only allowed to use the whiteboard. No laptops involved.
- In rare cases, candidates may even be allowed to skip the phone interview round and advanced to on-site directly.

Lyft

Recruiter phone screen.
Technical phone interview:
- 1 x Algorithm/Front end over JSFiddle.
On-site (Front End):
- 4 x Front end on Coderpad/your own laptop. Use any language/framework.
- 1 x Behavioural. Meet with an Engineering Manager and go through candidate's resume.
Tips:
- Can use whiteboard and/or laptop.
- For front end coding, I opted to use React and had to set up the projects on the spot using create-react-app.

Palantir

Recruiter phone screen.
Technical phone interview:
- 1 x Algorithm over HackerRank CodePair and Skype.
On-site (General):
- 2 x Algorithm on whiteboard.
- 1 x Decomposition (system design) on whiteboard.
On-site (Front End):
- 1 x Front end on your own laptop. This session lasts about 1.5 hours. Use any library/framework.
- 1 x Decomposition (system design) on whiteboard.
Tips:
- I opted to use React and had to set up projects on the spot using create-react-app.
- You may be asked to meet with Engineering Managers after the technical sessions and it's not necessarily a good/bad thing.

Recruiter phone screen.
Technical phone interview:
- 2 x Algorithm over CoderPad.
On-site (Web Client Developer):
- 4 x Algorithm on whiteboard.
Tips:
- No front end questions were asked.
- 1 of the interviewers is an Engineering Manager.

6.3 KiB Raw Blame History