Rotageek interview questions

The interview process was technically thorough and clearly designed to assess both hands-on ability and systems thinking. The first part focused on C# optimisation and architectural reasoning, followed by a deeper system design discussion. It was clear they value strong technical depth for this role. Two of the interviewers were engaging and open, and I appreciated the opportunity to discuss architecture and delivery practices in detail. However, one interviewer, the Principal Engineer, came across as very intimidating. The majority of the questioning was delivered in a rapid-fire style, with limited conversational flow or feedback. While I understand the need for rigour at this level, the tone felt more interrogative than collaborative, which made it harder to showcase strengths in a natural way. Also, a smile would go a long way in reassuring an interviewee under pressure.