Me postulé a través de una facultad o universidad. El proceso tomó 2 semanas. Acudí a una entrevista en Twilio en dic 2016
Entrevista
Gave my resume to recruiter on campus. First technical interview about a string problem and how to solve it in a distributed setting. Had to write code in both cases. Then 2 back-to-back interviews with an engineer and manager. Engineer asked a simple coding question. Manager was nice and discussed some behavioral questions. Some questions to gauge my skill level. Overall process was very smooth. The team got back to me very soon as I had a deadline.
Me postulé en línea. Acudí a una entrevista en Twilio
Entrevista
I was given a take-home coding exercise, which was quite a bit more hefty than most others I've had. Sent a link to the public repo a few days later. The following week, the recruiter asked me to send the link I already sent. When I followed up the next week, I found that the recruiter's email bounced - they were no longer with the company. So I then emailed a higher-up, who passed me along to another recruiter, who I then sent my exercise to yet again. A rejection followed soon after with no feedback.
Phone screen and onsite with a few leetcode and system design questions. The overall process was professional and the recruiters did a good job of keeping me up to date.
Preguntas de entrevista [1]
Pregunta 1
Implement an LRU Cache with some existing boilerplate code
Me postulé en línea. Acudí a una entrevista en Twilio (Dublín, Dublín)
Entrevista
Very friendly talent acquisition staff member, was given plenty of info for technical test, including what concepts would be asked. Had to do a systems design interview also and was given enough to prep for that.
Preguntas de entrevista [1]
Pregunta 1
Programming question about traversing graphs, systems design question about a photo printing service