I candidati per il ruolo di Software Engineer hanno valutato i colloqui presso Meta con un punteggio di 3,4 su 5 (dove 5 è il livello di difficoltà più alto) e hanno giudicato la loro esperienza di colloquio positiva per il 38%. Per fare un confronto, la media complessiva dell'azienda è positiva per il 45,1%. Queste sono le valutazioni degli utenti Glassdoor.
I tempi di assunzione dei candidati per il ruolo di Software Engineer sono in media di 19 giorni, in base alle recensioni di colloqui inviate da 8 utenti per questo ruolo. Per fare un confronto, il processo di assunzione presso Meta in generale richiede una media di 36 giorni.
Le fasi comuni del processo di colloquio presso Meta per il ruolo di Software Engineer secondo quanto emerso da 8 colloqui su Glassdoor includono:
Colloquio telefonico: 42%
Test attitudinale: 33%
Presentazione: 17%
Test della personalità: 8%
Ecco i ruoli cercati più frequentemente per le recensioni dei colloqui -
Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 3 mesi. Ho sostenuto un colloquio presso Meta (New York, NY) nel mese di set 2019
Colloquio
I was approached by a recruiter, but she didn't get back to my reply. I later went through employee referral.
I had one phone interview and (although I believed I was good), the interviewer was not confident in advancing me to the next round. I had another follow up phone interview and then advanced to the on site interviews. The results of the on site interviews had some mixed signals in the coding section and I went for a follow up on site coding interview. I received the feedback in one week after the final interview.
My recruiter was very open and communicated every step clearly. I was amazed by how he skillfully managed my process and was ready to help. The whole process was very smooth and I had a very good experience talking to the interviewers and the rest of the team.
Domande di colloquio [1]
Domanda 1
The coding questions are on average mid level questions. They are not tricky and they are fairly straightforward. Yet, it seems important that you need to solve the coding questions completely to the end, find the optimal solution and cover all the edge cases carefully. For my case, I solved two coding questions in each of the 45 minute coding interviews. The behavioral, system design and machine learning questions were straightforward and manageable.
Ho sostenuto un colloquio presso Meta (Londra, Inghilterra)
Colloquio
Generic LeetCode-style questions, many tagged as Meta, so extensive preparation is required to perform well in the technical interview. The experience varies significantly - some interviewers provide hints and guidance, while others expect candidates to solve problems independently with minimal assistance.
Spoke with interviewer over video conferencing. He was very communicative . He answered my questions. Asked me BFS question. A question that involved BFS search. Given a matrix, I am suppose to find a path from top left to down right.
Domande di colloquio [1]
Domanda 1
A question that involved BFS search. Given a matrix, I am suppose to find a path from top left to down right.
The technical round hit me with a classic array manipulation problem: moving zeroes to the end without disrupting the order of non-zero elements. As I tackled it, I felt a wave of familiarity wash over me; I had just practiced a similar challenge on PracHub. The rest of the interview followed a straightforward path, with some easy behavioral questions sprinkled in. Overall, it felt very easy, but I wasn’t quite the right fit for what they needed, so I didn’t receive an offer.
Domande di colloquio [1]
Domanda 1
Move zeroes in an array to the end while keeping non-zero element order, in place