Software Engineer Interview Experience - Palo Alto, California
Process
Typical process:
Two phone interviews, one onsite interview. Finally rejected after the onsite interview.
Facebook recruiters seem to act very respectfully until they want a candidate. Once they no longer need a candidate, recruiters are unresponsive. I traveled all the way to Palo Alto for the onsite interview and felt like I did well. However, five days after the interview, I had to follow up with the recruiter for a decision. The recruiter then emailed me, saying she had an update and asked for my availability for a phone call the next day.
I was eagerly waiting, but there was no call from her. I had to remind her the next day to call me. The recruiter finally called and informed me it was a reject. I asked for feedback, and she stated there was no feedback, just an "overall evaluation." Actually, I was told by the recruiter that Facebook would provide feedback on interviews, but it was the complete opposite after the onsite interview.
Questions
Signed NDA. Cannot reveal questions.
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
- 4.0Rewarding Experience, Heavy WorkloadSoftware Engineer • Former EmployeePalo Alto, California, United StatesJune 16, 2014Pros: Have a great experience and meet new people.Cons: Workload can be heavy and grueling for some people.
- 4.0Good experience, great peopleSoftware Engineer • Former EmployeePalo Alto, California, United StatesJanuary 18, 2010Pros: Really smart people that care about building a great product. It's clear that people are really excited about what they are doing.Cons: It's getting political and seems like there is a lot of jockeying. That's not great for an engineer who really cares about making a great product. It gets in the way.
- 2.0Trending towards bureaucracySoftware Engineer • Current EmployeePalo Alto, California, United StatesMay 24, 2011Pros: - Free food - Reasonably good compensation - Reasonably flexible hours - Lots of smart, capable people - Work can be excitingCons: Working on product teams is trying because of the micromanagement of Zuck and other upper management. Many projects get delayed because they ask for random changes. Working on backend teams doesn't have that problem, but they are typically second-class citizens and don't get as much respect as frontend teams. Facebook is very large now and the bureaucracy is starting to accumulate quickly. It used to be that engineers could just do stuff, but now almost every change requires a great deal of pointless discussion or overhead. For instance, you now have to fill out a form just to log some data. Very strong focus on some of the "hot" product teams means that the rest of the company doesn't get preference with respect to product managers, designers, etc. Most frontend work is boring, mundane PHP. The only challenge comes from poorly-designed legacy systems. Managers will often ask you to work on something you don't care about just because it's a priority for the company. This goes against the claimed philosophy of Facebook, but it's the way things are trending.
Meta Interview Questions
