Process
For the coding interview, you need to solve two questions, with 45 minutes allocated for each round.
First, clarify the question, then explain your idea, implement it, and finally, go through the code with test cases. At last, ask the interviewers questions.
Questions
Behavioral questions, such as collaboration and teamwork.
Was this helpful?
Interview Statistics
The following metrics were computed from 1,861 interview experiences for the Meta Software Engineer role in United States.
Success Rate
14%
Pass Rate
Meta's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Positive54%
Neutral30%
Negative16%
Candidates reported having very good feelings for Meta's Software Engineer interview process in United States.
Meta Work Experiences
5.0
Challenging, Dynamic Role
Software Engineer • Former Employee
Seattle, Washington, United States
April 6, 2024
Pros: Great challenges and constantly moving.
Cons: If you don't like getting moved.
5.0
Transparent Growth, Challenging Code
Software Engineer • Current Employee
Seattle, Washington, United States
August 10, 2020
Pros: The job expectations and promotion progress feel very transparent at Facebook, and I feel that my manager has my best interests in mind. I receive plenty of help from senior engineers and feel that I am progressing well as a programmer.
My team also agrees to work 40-hour weeks, which is not what I was expecting before coming here (excluding on-call).
Cons: I work on a ton of refactoring, so having to understand undocumented and poorly written code can be a pain.
When I am on call, I can be paged to fix the production service after work hours, though I haven't been paged while sleeping yet.
4.0
Good Pay + Growth, Bad WLB
Software Engineer • Current Employee
Menlo Park, California, United States
May 13, 2021
Pros: It pays well, you'll learn a lot, and you'll have many opportunities for growth.
Cons: Pros come with a cost: it is highly competitive and often results in bad WLB.
- 5.0Challenging, Dynamic RoleSoftware Engineer • Former EmployeeSeattle, Washington, United StatesApril 6, 2024Pros: Great challenges and constantly moving.Cons: If you don't like getting moved.
- 5.0Transparent Growth, Challenging CodeSoftware Engineer • Current EmployeeSeattle, Washington, United StatesAugust 10, 2020Pros: The job expectations and promotion progress feel very transparent at Facebook, and I feel that my manager has my best interests in mind. I receive plenty of help from senior engineers and feel that I am progressing well as a programmer. My team also agrees to work 40-hour weeks, which is not what I was expecting before coming here (excluding on-call).Cons: I work on a ton of refactoring, so having to understand undocumented and poorly written code can be a pain. When I am on call, I can be paged to fix the production service after work hours, though I haven't been paged while sleeping yet.
- 4.0Good Pay + Growth, Bad WLBSoftware Engineer • Current EmployeeMenlo Park, California, United StatesMay 13, 2021Pros: It pays well, you'll learn a lot, and you'll have many opportunities for growth.Cons: Pros come with a cost: it is highly competitive and often results in bad WLB.
Meta Interview Questions
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences
