O processo levou 1 dia. Fui entrevistado pela Meta (Palo Alto, CA) em nov. de 2009
Entrevista
I was contacted via email by HR saying that my friend had recommended I be interviewed for a spot at the company. I was pretty surprised by this, but have found that this is how Facebook often goes about doing things. We scheduled an interview for a few days later, which I thought was going to be a technical interview. When I got on the phone with the interview he asked me about what I've been working on recently, and so I got into this whole thing about my research project which I probably took a good 10 - 15 minutes describing. He basically just verbally nodded through the whole thing. He then asked me about what positions I was interested in interviewing for at Facebook. In my push to prepare for what I was expecting to be a technical interview, I somehow neglected to actually figure out what specifically I could work on at Facebook. I mentioned doing something with the large data sets they work on, since my research focused somewhat loosely on large-scale data analysis. Should have prepped for that one, but no problem. He then told me that he'd be happy to set me up for a phone interview with an engineer as soon as possible and I was like "whaa?! I thought you were one!". Not actually, but I did say that I'd be happy to interview with an engineer and so he got that set up for me. I'll come back and post once I've had my *actual* technical interview (instead of just an HR sanity check)
Unexpectedly, the first question in the technical round felt familiar. It was about finding a subset of strings with unique character concatenation — same problem I had worked through on PracHub a few days earlier. The interview included a recruiter screen followed by a rigorous pair of technical interviews where I tackled data structures and algorithms alongside system design concepts. After successfully answering a few more challenging DSA questions, I received an offer. The entire experience was intense but ultimately rewarding, and I happily accepted the position.
Perguntas de entrevista [1]
Pergunta 1
Given an array of strings, pick a subset whose concatenation contains no duplicate characters, and return the maximum possible length of that concatenation.
Standard cookie cutter interview with a coding interview, a system design interview and culture interview. The coding part is basically leetcode. The system design is what you can find on many youtube videos. The culture one is more tricky as they want to see that you fit Meta's culture, not that you were doing great at your existing company. So skills like dealing with conflict without calling in managers is sought after.
Perguntas de entrevista [1]
Pergunta 1
coding: I forgot, sorry
system design: design ticketmaster
culture: talk about past project; when you disagreed with a peer; how I resolved dissagreements, etc.
The interview felt more straightforward than I anticipated for a well-known tech giant. After a recruiter screen, I faced a technical round that included a DSA question about finding the lowest common ancestor in a binary tree. I was pleasantly surprised when I realized the exact problem had popped up in the algorithm practice section on PracHub during my prep. Ultimately, the experience was decent, but I chose to decline the offer as it didn’t align with my current goals.
Perguntas de entrevista [1]
Pergunta 1
Given a binary tree, find the lowest common ancestor of two given nodes in the tree.
