Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Meta (Palo Alto, CA) nel mese di ott 2010
Colloquio
I had on campus interviews in the spring and then decided to interview for full time in the fall. I had three interviews - the first went very well, the second was terrible, the third was alright. The terrible interviewer asked some basic technical questions involving writing code on the board. As I thought out loud, I asked the interviewer clarification questions and then ultimately asked whether I should start writing code on the board. The interviewer either did not respond to my questions or mumbled off a few incomprehensible words. I started writing code and as soon as I stepped back from the board, the interviewer pointed out my mistake without giving me a chance to assess the code myself. He did this an another two times for the subsequent questions.
Overall, the questions were not difficult at all. It seems that Facebook wants to make sure that you code frequently enough that you do not make any errors on your first hack at a problem. This seems to fit the "go fast and break things" motto. Although things didn't work out for me, I got an offer from Google, so I guess that's not a bad second choice.
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.
Domande di colloquio [1]
Domanda 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.
Domande di colloquio [1]
Domanda 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.
Domande di colloquio [1]
Domanda 1
Given a binary tree, find the lowest common ancestor of two given nodes in the tree.
