Twilio Software Engineer interview questions

Absolute disaster. This is easily my worst interview ever. Avoid the Twilio Mountain View office if you can. First interviewer made it clear the the role will require long hours and even some weekend work if need be. I'd have to carry my pager everywhere 24/7. Obviously a big red flag. The technical interviewer was a crazy person with no social skills. Even worse, he rejected the correct solution to his question. The question: Given a word and a dictionary, find the anagrams that exist in the dictionary. I was as thorough as I could be. I discussed from obvious brute force O(n!) permutation to generate all anagrams and check against dictionary to the optimal character frequency map for all words of equal length to supplied word comparison (which is O(n) time and constant space as the map will never exceed size of 26). The interviewer wrongly thought it was O(n) space and wanted me to do better. I even suggested the prime number product approach where each letter would be mapped to unique prime number with danger of overflow for really big words. He did not understand why this would work. We spent the whole time discussing to no avail. When I asked him what he wanted, he would respond with "You tell me" or "come up with a better solution." In the end he didn't even tell me what he was looking for, and I was not given the chance to write any code up on the board. I think he may have been pushing for the sorting by character's ASCII method, but this is longer/less efficient than the frequency map approach. I was stunned at how such an argumentative fool was employed at a place like Twilio. The last "technical" interview was a joke. It was through a conference video and I was given a laptop and asked to fill in the blanks of code written on a text editor. The text editor actually crashed midway because the trial period Twilio was on had expired...honestly this interview was just not worthy to be called a technical interview. I wrote a complaint to HR detailing my experience, but they are useless in these situations. I just had to cut my losses and move on.

I applied for the Software Engineer role and was called for interview. Had two phone interviews. Asked to code in coderpad and the first round was easy. The interviewer for the second round hardly paid attention and I got a rejection mail later. It was one of the poor interviews. The question was not tough but his attitude made me uncomfortable. Questions were standard Data Structure questions and it was one of the easiest interviews I had ever had.