Taro Logo

Software Engineer Interview Experience - Menlo Park, California

February 1, 2014
Positive ExperienceGot Offer

Process

The interview process for me was "uberly" long. I wasn't planning on applying to Facebook, but a recruiter reached out to me mid-December on LinkedIn. I thought, "What the heck, it's a great company," and got back to her the next day. However, she was leaving for the Christmas break. There was no further communication until early January.

Connecting on the phone was a pain. First, she didn't call until 15 minutes after she said she would. I had stopped standing by the phone and went to email her when she did call, so I missed it. We emailed and set something up for an hour later. This time, she called 30 minutes late, with no apologies or explanation.

She advised that I put all of my other interviews before the Facebook one so that I could get practice, and then signed me up for a free interview review course they run. I went, and things seemed great, so I told them I was ready. This led to another two-week pause while they tried to answer a question I had asked before scheduling me.

When I finally made it onsite for an interview (mid-late February), I had expected it to be a full day of interviewing. Instead, it was a 30-minute screen before I could do the actual interview. In all fairness, I should have seen that coming.

Anyways, I did the screen and got a response before I had even left the parking lot that they wanted to schedule my full interview. I also got a call from my recruiter that afternoon to give me interview feedback. I thought that was awesome, as most people don't do that. I can't say how useful it was, as I had no negative feedback from my interviewers and her advice was just, "Wow, keep doing whatever you just did!" It sounds like it could be useful if things don't go perfectly the first time around.

Anywho, by this time I had multiple other offers with deadlines on them. I went ahead and scheduled the final round interview for the following week but ended up canceling the day before as I had decided to go with another company. This seemed to irk my recruiter, despite the fact that she was the one who told me to interview with other companies first, and I had been upfront about that and the associated timelines during the whole process. When initial contact and end offer are 2.5 months apart, you can't expect someone to be sitting idle that whole time...

The only reason I still rank this as a positive experience is because I had a secondary recruiter I worked with coordinating onsite logistics (the girl who first contacted me was out of state), and he was awesome. If any of you get the chance, work with Charlie. He's direct and super straightforward and knows that candidates are people with multiple options and treats you as such. I do a lot of mentoring and will certainly be sending any of my mentees who express interest in Facebook Charlie's way; he's a real gem.

Questions

One of the questions I received was around bit manipulation that built upon itself in layers (i.e., how would you do X? Okay, say you have a function for X, how would you do this new thing Y?).

The other question was a modification of a sorting question (i.e., the question itself was to sort the array, but there were some parameters on the data type that made things extra fun/not a standard sorting algorithm).

Was this helpful?

Interview Statistics

The following metrics were computed from 359 interview experiences for the Meta Software Engineer role in Menlo Park, California.

Success Rate

28%
Pass Rate

Meta's interview process for their Software Engineer roles in Menlo Park, California is very selective, failing most engineers who go through it.

Experience Rating

Positive69%
Neutral18%
Negative13%

Candidates reported having very good feelings for Meta's Software Engineer interview process in Menlo Park, California.

Meta Work Experiences