I applied in-person. The process took 4 weeks. I interviewed at Twilio (Pittsburgh, PA) in Oct 2013
Interview
Met team at campus recruitment event. Could use previous experience to engage with them. Secured on-campus interview next day. Went well, was mainly technical. Followed by dinner with team. Followed by 2 phone screens. Both technical. Not very challenging but needed basic CS and systems knowledge. Second one quizzed me on specific technology Twilio worked with - things I was somewhat familiar with. Third "interview" was discussion with team lead to discuss position and seal the deal.
Interview questions [1]
Question 1
Given a hash map implemented as an array of linked lists, how would you make it concurrently accessible?
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.
Interview questions [1]
Question 1
Implement an LRU Cache with some existing boilerplate code
I applied online. I interviewed at Twilio (Dublin, Dublin)
Interview
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.
Interview questions [1]
Question 1
Programming question about traversing graphs, systems design question about a photo printing service
