Allen Control Systems interview questions

The first call was a recruiter screen. The recruiter was very friendly, professional, and willing to answer questions about the role and company. The next round was a 15-min live-coding interview. Overall, the technical interview felt unusually rushed. The problem itself was a very common and famous medium-difficulty leetcode question with minor modifications. It felt more like a speed test than a meaningful technical evaluation. The interviewer joined late, spent part of the limited time on setup and explanation, and then explained a specific and inefficient approach they wanted me to use. The expectation seemed to be that I should follow that exact approach and complete the implementation within only a few minutes. During the coding portion, there was little to no discussion, guidance, or engagement. The most disappointing part was the communication style. Once time ran out, the interviewer became dismissive and made comments along the lines of me not following what they wanted, not being capable of the role, and implying that I must have seen the question before. The tone felt unnecessarily disrespectful and unprofessional. As professional engineers and candidates, we completely understand that interviews might not be easy, and not every interview will go well. However, candidates still deserve a professional and respectful environment where both sides can fairly evaluate fit. This experience made me question the team culture and whether this would be a healthy environment to work in. I would advise future candidates to be cautious, especially if respectful communication and a collaborative engineering culture are important to you.