The application process started with submitting a required software project that utilizes 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 10 am and took about 3 hours 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 minutes)
• Technical interview (60 minutes)
• Soft skills and mindset interview (30-60 minutes)

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.

On a whiteboard, implement a function called tripleRotate, which "rotates" all subsequent sets of 3 elements in an array. 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 can be used, although actual code, not pseudocode, is expected. No additional information was given, so lots of additional questions about corner cases and requirements would be expected from 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?

Explain how running multiple tasks on a single processor core works.