Acudí a una entrevista en Twilio (San Francisco, CA) en oct 2016
Entrevista
Had an initial phone call with recruiter. We seemed to connect and he said that he'll get in touch with me about next steps/interviews over the next few days. However, he stopped responding to my emails/messages after that. It's ok if you think a candidate isn't a good fit, but have the courtesy and spine to communicate that to the candidate.
8
Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer en Twilio
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
