Thanks, Yaser! This article clarifies me some things about the technical interview process and when I was reading I notice that I made mistakes taking a technical interview.
Sometimes I feel I responded to some questions like a robot, giving the answer that the recruiter waits, because they ask me questions that, in my opinion, don't give any information about me as a programmer or how I work with teams.
The weirdest question I received was: which teacher did you have in X course? I responded and the recruiter told me: 'that teacher is not good and maybe you don't have enough skills' (after this the interview finished).
In my last interview, I was asked about what was the last thing I learned I respond like 'I am learning X and improving Y'. Then I was asked to give an example of what I learned (this question is the same as 'How do you explain X in simple terms?'). At this moment I felt that I was applying for a real tech job.
Thanks, Yaser! This article clarifies me some things about the technical interview process and when I was reading I notice that I made mistakes taking a technical interview.
Sometimes I feel I responded to some questions like a robot, giving the answer that the recruiter waits, because they ask me questions that, in my opinion, don't give any information about me as a programmer or how I work with teams.
The weirdest question I received was: which teacher did you have in X course? I responded and the recruiter told me: 'that teacher is not good and maybe you don't have enough skills' (after this the interview finished).
In my last interview, I was asked about what was the last thing I learned I respond like 'I am learning X and improving Y'. Then I was asked to give an example of what I learned (this question is the same as 'How do you explain X in simple terms?'). At this moment I felt that I was applying for a real tech job.
Yes, unfortunately we all fall into that trap from time to time