Candidatei-me online. O processo levou 3 dias. Fui entrevistado pela Snap (Santa Monica, CA) em jan. de 2019
Entrevista
Three rounds of interviews: a phone screen with a recruiter, a phone interview with another QA and an onsite interview with managers, a dev, and another QA.
Overall, the interview was relatively easy. Everyone really went out of their way to make you feel as comfortable as possible. It was one of the friendliest, no-pressure interviews I've ever had.
Although (I thought) I provided the right answers, I was turned down. My guess is when I was asked a coding question by the dev, and I didn't provide the answer he was looking for.
The feedback I received was not specific either, but in looking at others' experience, this appears to be a common trend in Snap interviews.
Perguntas de entrevista [1]
Pergunta 1
- String and file manipulation questions
- Approach to testing/automation
6 rounds of interviews in 3 weeks. I felt I did great but didn't get the offer. HR was awesome and very quick.
Final round, I was asked to solve leetcode HARD (212) difficulty problem which solution contains advance DS like Trie.
They lack understanding of the difference between a QA and SDET engineer. Everyone is aware that QA with excellent programming skills is not the best in finding bugs. Do they want the buggy applications to customers on purpose?
It was a good experience.
Perguntas de entrevista [1]
Pergunta 1
leetcode 212 hard problem. They expect QA engineers to solve this in 25 min.
Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela Snap (Venice, CA) em set. de 2017
Entrevista
First was a screen phone interview, then a Google hangout interview, then an on-site interview at their office in Venice. Very professional organizing schedules. Phone and hangout were 30 minutes long. On-site interview was about 2 hours long. Received a Snapchat swag bag during interview.
Perguntas de entrevista [1]
Pergunta 1
How did you handle a disagreement with a co-worker?
