The initial application stage was fairly straightforward. The application page provided sufficient detail regarding what Twilio was looking for in a candidate. The application form asked a number of questions relating to the core values.

The next stage was a 2-hour technical test on HackerRank, comprising two technical questions. In preparation for this, the recruitment team provided helpful information and materials, which was particularly useful for those going through this type of application process for the first time.

As the Hatch programme targets individuals from non-CS degree backgrounds (I came from a bootcamp), the HackerRank test reflected this. The two questions focused on general problem-solving, rather than tricky data structures and algorithm questions you might typically encounter (thankfully!).

The third stage comprised a further written application, again focusing on understanding the company values and cultural fit, which was relatively straightforward to complete.

The final stage consisted of an interview day(s), including two technical interviews and two behavioural interviews, each lasting 45 minutes. Again, the recruitment team provided excellent documentation in preparation for this. We also had a chance to meet with other Hatch alumni, which was a reassuring experience, although the meeting could have been structured better, as there were issues with everyone getting their questions answered in the limited time available.

The technical interviews involved a pair-programming exercise where I was the driver and the interviewer acted as the navigator. The interviewers did very well to settle my nerves and provide sufficient guidance, while still allowing me to focus on problem-solving and demonstrate my capabilities.

The behavioural interviews consisted of a number of competency-based questions to assess the demonstration of Twilio's core values. The interviewers again excelled at putting my nerves at ease and allowing me to answer the questions to the best of my ability. I won't reveal too much, but as long as you are familiar with the STAR technique, Twilio's values, and can provide real examples reflecting your achievements along with any constructive criticism, you should be able to answer these questions well.

Why did you decide to transition to software engineering?