Software Engineer Interview Experience - Palo Alto, California
Process
I was contacted via LinkedIn. I had a chat with the recruiter, a very friendly lady, who asked about my background and about 8-10 simple programming questions at the end.
I then scheduled a phone interview with an engineer, who was also quite polite and helpful. After asking about my background, he gave me two questions. It wasn't my area of expertise (algorithms), so I did just okay, nothing superstar.
Two days later, I was told that there aren't any positions fitting me at present, but they'd like to stay in touch.
Questions
Implement needle-in-a-haystack (string search). Make it more robust.
Implement a queue data structure given only stacks. What is the time complexity of enqueuing and dequeuing operations?
Was this helpful?
Interview Statistics
The following metrics were computed from 78 interview experiences for the Meta Software Engineer role in Palo Alto, California.
Success Rate
Meta's interview process for their Software Engineer roles in Palo Alto, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having good feelings for Meta's Software Engineer interview process in Palo Alto, California.
Meta Work Experiences
- 5.0A good place to growSoftware Engineer • Current EmployeePalo Alto, California, United StatesOctober 7, 2022Pros: Fast-paced, which makes it prime for growing quickly as an engineer.Cons: Everything always is broken.
- 5.02+ Years at Meta as SDESoftware Engineer • Current EmployeePalo Alto, California, United StatesDecember 13, 2023Pros: food, growth, learning, colleagues, perksCons: The work-life balance is sometimes bad.
- 2.0Fun at the engineer-to-engineer level, but brutally long hours and badly disconnected front-line managementSoftware Engineer • Former EmployeePalo Alto, California, United StatesJanuary 2, 2012Pros: Huge corporate upside potential (but might not apply to new hires as of 2012). Fun work environment (free quality food, game rooms, frivolity encouraged, etc.). High impact in terms of people using your code and recognition. Good opportunities to try new ideas and move teams.Cons: Brutally long hours for many, frequent pressure to delay or cancel vacation plans (even outside of release deadlines). Harsh, unjust, and badly cross-team calibrated reviews, coupled with frequent firings, so that the stick is very close to the carrot. It has now grown large enough that internal corporate politics have seeped in. Management, at all levels, is fixated on lots of shiny new features, no matter how broken, and lacks respect for necessary work getting done.
Meta Interview Questions
