Le processus a pris 1 jour. J'ai passé un entretien chez Meta en avr. 2012
Entretien
Took 2 weeks to schedule phone interview. Interviewer was nice..gave hints and examples on the way. and then after 1 week I heard that they will not be proceeding
Questions d'entretien [1]
Question 1
Say you use SVN for source control..you have several revisions of a file...R1, r2, r3..etc..Someone checked in a bug and the revision became bad..need t find the first bad revision..gave a function findBadRevision(int goodRevision, int badRevision) so for e.g the revisions were GGBB and function passes in 0,4 so the first bad revision is 2. There exists a function boolean hasBug(int revision) which will tell us if a certain revision has a bug.
can assume good revision < bad revision
Overall, the process took a little over two weeks, which felt a bit longer than I anticipated. After a quick screening, I went through two technical rounds focusing on coding and DSA concepts. One of the questions was a classic palindrome check; mid-way through, I realized it was something I had practiced on PracHub just days earlier. The final step was a casual behavioral interview. I was relieved to get an offer shortly after, which I happily accepted.
Questions d'entretien [1]
Question 1
Given a string, determine if it is a valid palindrome considering only alphanumeric characters and ignoring case.
J'ai postulé en ligne. J'ai passé un entretien chez Meta (Menlo Park, CA)
Entretien
It's honestly striaght from leetcode tagged
There are no surprises if you do tagged you would be good and do well.
System design is much harder. Would recommend using hello interview.
Questions d'entretien [1]
Question 1
Design Twitter and consider if it was suddenly an extremely low latency env