I recently went through the interview process for a Software Engineering role. found the interview style challenging in a way that didn’t fully reflect real-world software engineering practices. The technical interviews were very brief and heavily focused on algorithmic questions (Do your LEETCODE). While I understand the importance of problem-solving skills, the format felt more like a one-sided evaluation rather than a collaborative discussion. At one point, I asked whether I was heading in the right direction, and the response was that the interviewer was “only there to listen.” This made it difficult to adjust my approach or demonstrate how I typically work through problems in a team setting. In practice, software engineering is highly collaborative, engineers ask clarifying questions, validate assumptions, and iterate with feedback from others. A more interactive interview style would better reflect this reality and allow candidates to demonstrate both technical thinking and communication skills. Overall, I appreciate the opportunity, but I would suggest making the technical interviews more conversational and providing minimal guidance when candidates are clearly off track. Advice to candidates: Be prepared for algorithm-heavy questions and practice solving problems while thinking out loud, as interviewers may not provide guidance.

Very quick HR interview (about 10 to 15 minutes), different than others that I did. Technical interview in a WORD document (live coding). Basically, to complete two Leetcode-like functions. Syntax was not being considered here, they wanted to check how you think and how to resolve a problem. I thought that I went well, I even checked after the interview (about 30 minutes), I only made one minor mistake (inverted the logic), but that was because of the short time provided and it is a poor experience typing in a Word document that keeps changing what you are writting and you have to go back and change it again