I spoke to an HR member over a call. She was really nice and tried to help me find a good fit, but she did tell me they would be focusing on new grads first and would let me know if the HM role was still open. No biggie.
After a week, I heard back from another position I applied to. Another HR person booked a meeting with someone. It wasn't mentioned if he was the HM or HR; I assumed the former.
We had a quick phone call. He gave an overview of the position and sent a HackerRank assessment. That was it – a 10-minute call. I wasn't prepared, so I couldn't ask any questions.
I didn't know until the very end that he was not the hiring manager. I reached out after the call and requested if we could set up another quick call, as I had a few questions. I was ghosted. I followed up with my availability after two days. I was ghosted. I completed the assessment and informed him. I was ghosted. After a week, I was rejected for the position.
Two HackerRank questions:
Given a file with filenames and extensions. Create new files based on the extension so that each new file only contains its respective extension.
Log parsing. Find records that have a GET request and a 200 status code, and then identify the name of the GIF file.
The following metrics were computed from 1 interview experience for the Twilio Software Engineer - Observability Infrastructure role in Canada.
Twilio's interview process for their Software Engineer - Observability Infrastructure roles in Canada is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Twilio's Software Engineer - Observability Infrastructure interview process in Canada.