J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Twilio en mai 2016
Entretien
The application process started with submitting a required software project that utilises the Twilio API (no other requirements given), along with a typical web-based job application.
After my application was reviewed, I was invited for a couple of on-site interviews. The day started at 10am and took about 3h from start to finish.
There were 3 interviews (the interviewers partially changed for each of them):
- demo of the project I had submitted along with my application (30 mins)
- technical interview (60 mins)
- soft skills and mindset interview (30-60 mins)
Once the interviews were concluded, I was asked to join the rest of the team for lunch (I believe it was a weekly tradition back then). The atmosphere was very chill and friendly – we joked around and talked about things on our minds. This in no way felt like I was being actively judged and drilled – it really was just (or at least felt like!) a friendly lunch.
Questions d'entretien [3]
Question 1
On a whiteboard, implement a function called tripleRotate, which "rotates" all subsequent sets of 3 elements in an array, when the algorithm for one rotation is as follows:
Given the triplet ['a', 'b', 'c'], the 1st element ('a') is moved to index 1, the 2nd element ('b') is moved to index 2 and the 3rd element ('c') is moved to index 0. Thus, one rotation of the given triplet results in the new array ['c', 'a', 'b'].
Any programming language and data types could be used, although they did expect actual code, not pseudocode. No additional information was given so lots of additional questions about corner cases and requirements were expected to be asked by the applicant. Prepare to explain your chosen approach and used data types.
What are the runtime complexities for reads and inserts on arrays, hash maps and linked lists? What are the best and worst case scenarios for each? When would you use one over the others?
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