J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Snap (Chantilly, VA)
Entretien
Interview went over my professional background and technical skills mentioned on my resume. There was clear guidance from management on how to update my resume and answer client interviews so that I was able to get on a project with minimum bench time. Hiring process was smooth and there was minimum paperwork.
Questions d'entretien [1]
Question 1
The only challenging question was regarding the reason for change in employer
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Snap (Sydney) en sept. 2021
Entretien
- Call with recruiter (10 min chat about expectation and experience etc)
- Call with a dev the next day, 1 hour session packed full, started with a few behavioural questions, then moved onto two code snippet reading questions and 2 leetcode style questions (medium -> hard), didn't finish the hard one and probably made lots of mistakes.
- Onsite the week after. 5 interviews in total, 4 coding ones structured similarly (~10 min behavioural and ~40 coding then ~10min chat)
Had a call with the recruiter day after the interview, very straight forward actionable feedback and the whole process took less than 7 days as I had other offers lined up. Will definitely rate this as one of the most professional recruitment processes I've had.
Questions d'entretien [1]
Question 1
- 2 code snippet reading, recursion and string
- Coding questions I feel are not super difficult - I didn't really do any leetcode/hackerrank before coming into the interview but I felt like I was given mostly medium difficulty ones (not sure if they're actually leetcode medium). There was a lot of variation of requirements.
- One system design question, scaling, backend design, distributed systems, message queues
- One object oriented design question which I felt would be more lower level specific (L2/L3). Basically designing a parent class that interacts with a few different library classes that came in various shapes. Asynchronous programming was thrown in here as a final variation.
