It should come as no surprise to learn many job seekers dream of landing a job at Facebook, which consistently earns top marks on “the best places to work” lists.
Thousands of candidates, both engineering and non-tech alike, seek out jobs at Facebook, which has offices all over the world. When you work at Facebook, I’m told, not only are you a part of creating something that has the potential to touch the lives of billions of people around the world, you also have opportunity for career advancement, good employee benefits and yes, the famous Facebook campus and all that goes along with that.
I visited Facebook HQ in Menlo Park recently and got to see the inside of the campus on a busy afternoon and it’s easy to see why people want to work there. It’s like a small city unto itself with numbered buildings, several cafeterias and food options in each, and a diverse group of employees walking around with laptops and phones, going from comfy workspaces to meeting rooms.
With thousands of applicants vying to be a part of the Facebook team, how do you know what they’re looking for? And how do you make yourself stand out from the crowd of applicants? I got the inside scoop from Laura Reyes, Diversity Recruiting Leader at Facebook.
People who interview for technical roles may participate in multiple coding interviews via phone/video chat or onsite, during which they’ll solve problems based on CS fundamentals, systems design, and more. The coding components of technical interviews are part of a multi-faceted interview process that also takes into account the skills and strengths necessary for the role and level and how well each interviewee will operate in Facebook’s environment. Like many things at Facebook, we continue to evaluate and adjust our technical interview process as we grow. And we’ll continue to invest in improving our hiring process and testing new tools and methods that best fit our needs at Facebook.
Prepare some examples of your past experience. Brainstorm some concrete, detailed examples from your experience and be prepared to speak about them. Think of times when you’ve built something, improved something, or collaborated with others to create something better than you could build on your own. Explain the problem and your approach: How did you try to build a solution? What worked, and what didn’t? What did you learn, or what would you do differently next time?
For technical interviews, practice coding. Review CS fundamentals like data structures and algorithm design/analysis, and practice using the platform (such as a collaborative code editor or a whiteboard) you’ll use to code during your interview. While you code, practice talking through the problem and your decisions as you go.
Ask your recruiter. Work with your recruiter to understand what your specific interview process will include and the best ways to prepare. This advice may be different depending on what role you’re interviewing for, especially for technical roles.