Four interviews, 45 minutes each:
Code challenge: This was a HackerRank link with a problem about dependencies. An array was given in the structure A = [[P0, P1], [P1, P2], [P3, P2], [P4, P1]], where P represents a program to be installed and dependencies were represented by their positions in the array. For example, P0 depended on P1, P1 depended on P2, and so on. The task was to print the programs in the order they needed to be installed. The problem is solved using a graph data structure or similar, rather than array methods.
Hiring manager: This interview focused on your technical experience, specifically as a software engineer in your current and previous roles.
Values interview: In this interview, you were given specific situations encompassing company values and asked how you would handle them.
System design: This interview, conducted on a HackerRank link with a whiteboard, required you to draw a design for an application that uploads media files and allows searching them. You had to start by selecting the front-end, back-end, database, and other required components, and then provide details on specific parts of the diagram. Although REST architecture might seem appealing, the task was looking more towards a SOA architecture solution.
Here's a breakdown of the interview process:
The following metrics were computed from 6 interview experiences for the Twilio Software Engineer role in Colombia.
Twilio's interview process for their Software Engineer roles in Colombia is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Twilio's Software Engineer interview process in Colombia.