The first stage was a screening interview with a recruiter, who was professional and great to chat with. I was contacted a few days later with a follow-up second-stage interview, this time with my prospective manager for the team. This interview was also professional and courteous, and I felt it was very productive. It covered the role and expectations (travel, expertise, etc.) and allowed me the chance to ask questions.
A week later, I was asked if I could attend an on-site interview loop at their San Francisco office, which would include paid flights and a hotel stay. Unfortunately, I had to decline as I was already on holiday in the UK but was able to compromise with an interview locally instead.
This loop lasted around five hours and involved five different people from various teams within the organization I was applying to join. The questions varied from data center engineering to network and sysadmin topics. They were all challenging and really pushed me to respond by digging deep to see how much I knew.
Twenty-four hours after that, I received an offer, which I accepted!
Various questions on fibre, DWDM, and networking commands.
Had to spec a project for installing various items in an 800mm wide x 1200mm deep rack in a way that ensured the best airflow.
The following metrics were computed from 1 interview experience for the Twitch Deployment Engineer role in London, United Kingdom.
Twitch's interview process for their Deployment Engineer roles in London, the United Kingdom is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Twitch's Deployment Engineer interview process in London, United Kingdom.