J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Twilio en mai 2012
Entretien
I was contacted by a recruiter who encouraged me to take part in a phone screen. The hiring manager missed the first call. It was clear during the rescheduled call that they had not reviewed my application materials. The hiring manager was also quite uncomfortable with a straightforward description of their business model, preferring instead to present their business in extravagant, hyperbolic terms.
J'ai postulé en ligne. J'ai passé un entretien chez Twilio
Entretien
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.
Questions d'entretien [1]
Question 1
Implement an LRU Cache with some existing boilerplate code
J'ai postulé en ligne. J'ai passé un entretien chez Twilio (Dublin, Dublin)
Entretien
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.
Questions d'entretien [1]
Question 1
Programming question about traversing graphs, systems design question about a photo printing service