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 online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Meta (San Jose, CA) nel mese di mag 2019
Colloquio
Phone call with recruiter, phone technical screen followed by on site technical interview. Overall a fast process and recruiters were also fast in scheduling and responding. Company culture is very nice. Employees seemed happy.
Domande di colloquio [1]
Domanda 1
Tech phone screen was general tech conversation of technologies worked on, projects and past work experience and telling me about the work and culture at Sage Intacct. The interviewer was very sweet and polite.
On Site:
All Questions were Leetcode HARD level questions variations, being copy pasted or typed exactly from Leetcode HackerRank by looking at screen.
1 was a tricky variation of the number of islands question from LeetCode, one was a super hard DP problem similar to coins problem of Leetcode. I mentioned to the interveiwer that although a DP solution is available, I am not comfortable with DP and hence doing the iterative version, he reacted in a very confused way as to 'why DP/what DP'. After I gave the full solution on the board, the interviewer didn't seem interested in discussing the approach or anything else. He just wanted me to write the same code from the board on HackerRank coding screen and submit it. Obviously, in the last 12-14 min, I couldn't complete this question at all.
This was followed by a system design question about online collaborative editing tool.
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
1 leetcode med, 1 leetcode hard. make sure you know your DSA and leetcode questions. I wasn't able to get an offer bc i didnt complete the second question. Got a reply 2 days later saying they would move on
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Meta (Menlo Park, CA)
Colloquio
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.
Domande di colloquio [1]
Domanda 1
Design Twitter and consider if it was suddenly an extremely low latency env