Process
I had a technical phone screen and got a pretty hard LeetCode-type question, which is always a pain. The main issue I had, however, was that the interviewer had the thickest accent I've ever heard and made no attempt to communicate properly. At least try to type things out for me, since no living creature could understand you.
The interviewer was also pretty rude and clearly didn't want to be doing the interview, so I pretty much just gave up and cut it short. Why waste my time?
It's always a hit or miss when interviewing with these big tech companies, and I really got the worst of them, lol.
FB - please don't have these types of people interview candidates. What are you guys doing?
Questions
Hard LeetCode question along with decoding cryptic language from a seemingly speech-impaired individual.
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
Meta's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Meta's Software Engineer interview process in United States.
Meta Work Experiences
- 4.0A good place to work for motivated individualsSoftware Engineer • Former EmployeeAugust 8, 2025Pros: - Incredibly smart talent base. - Driven individuals who are motivated to do their best. - Company benefits are really good. - Payment is top tier in the industry.Cons: - Sometimes long work hours are needed. - Performance reviews are heavily weighted and take a lot of attention during certain times of the year.
- 1.0A very competitive work environment, but not accurately advertised as suchSoftware Engineer • Former EmployeePalo Alto, California, United StatesMay 3, 2011Pros: - Opportunity to write software that gets used by hundreds of millions of people - Opportunity to see how a successful company is run - Opportunity to launch often - Potential IPOCons: - Frontend work (i.e., work done in most of the product-oriented teams) is mostly mundane PHP and nothing intellectually challenging from a Computer Science perspective. (Backend may be different, but I never tried that.) - Potential to get judged too quickly for performance. They are less willing than other companies to let you try something different, which may be a better fit if you are not performing well enough on your current project. - Chaos that may hurt you: you may start out on one project but be expected to do something else for no good reason, that may not be the best fit for your skills. - Some managers are too busy to give useful, frequent feedback. - I get the impression that they manage by a bell curve but are not being transparent about it.
- 3.0Pretty great experienceSoftware Engineer • Former EmployeeMenlo Park, California, United StatesAugust 18, 2025Pros: Felt startup kind of energy, with lots of perks.Cons: But every communication through Facebook posts is insane.
Meta Interview Questions
