> I never heard anything about incompetence in your description. I was rushing trying to explain two years in a few words. You might not know what happened is

> I never heard anything about incompetence in your description. I was rushing trying to explain two years in a few words. You might not know what happened is such long span. To give you some ideas of why I said incompetence: - my colleague doesn't know yet how our infra works - he has no clue of the application architecture has he still make unforgettable mistakes after two years - in any architectural meeting where we have to discuss about something he got missed, and, when he's there, he will suggest an open source tool to do so even when it doesn't fit our needs - in any meeting when somebody ask something to him, the first answer would be "just go in google and search for a library to do x, z, y" even when the question is very architectural specific and domain specific - even after we implement something he still want to find an open source or SaaS to use for no reason, not understanding that we have a lot of integration cost that he doesn't even understand - he only had front-end (only in small-sized companies) experience and less than 6 years of total experience when he was hired (he joined right after me, I was not the interviewer) and he never lead a team before. I worker in multiple context during my career; mainly enterprise and consultancy and I had team leading experience before the role.