I applied through a staffing agency. The process took 3 weeks.

The interview process was very smooth and quick. There were only 2 stages, however I went through a recruitment agency, so I'm not sure if you'd have another first recruiter interview if you applied directly.

The first stage was a 1 to 1 interview with the Lead DevOps Engineer. This was a nice and relaxed interview, discussing my previous experience and then doing a coding exercise to do with reading in a text file and counting words, and then some technical questions after. After passing this stage, I was invited to a second stage interview. Prior to this, I had to prepare two things: to complete a Kubernetes-focused take-home tech test and to prepare a presentation on a previous project I'd worked on.

The second stage was a 2-hour interview broken into two parts: the first was running through my presentation, and the second was discussing the tech test. Although 2 hours seems a long time, the two interviews were really nice, and the interview setting was also relaxed, so it actually ended up overrunning, although also due to the fact I had screen-share issues for about 15 minutes.

The structure of having a previous project to discuss is really nice, as it works as a natural springboard to discuss certain topics, makes the interview flow nicely, and allows you to talk about something you're knowledgeable about. After this was discussing the Kubernetes take-home task, why you did certain things, explaining some Kubernetes concepts, etc. Finally, at the end, there was time for me to ask general questions about the role and the company, or specifically drill into the technical details.

Write me some code that takes a text file of any length and counts the number of words and prints out any that appear more than twice. Improvements for this, if it was a super long file etc.

Can you explain what ingress is and how/why you would use it?