Phone screen followed by an interview at the New York City office.
The interviewer was new, had a poor, intimidating attitude, and no skill – he got every technical point wrong.
He asked simple questions on J2EE, got it wrong, like it's been called J2EE for years, and then said I should go along with being treated abusively and listening to wrong answers.
I am good at dealing with people; they were backwards and clueless.
They blundered again because they couldn't understand Java class loaders, and this was for a Sr. Solution Architect role.
Such a lack of talent! He and another non-technical manager kept saying, "I've never heard that before." What losers.
Management: If you want to get and keep good people, lose the no-talent, poor-attitude front-line people because you have no chance of getting anyone who has programming skill, let alone good professionals, with people like that.
I bet you'd double to triple the quality of your talent base by removing non-technical middle managers standing in their way.
Technical people ask technical questions, not non-technical, entry-level managers who don't know they don't know.
How do you handle clients?
The following metrics were computed from 2 interview experiences for the Red Hat Solutions Architect role in New York, New York.
Red Hat's interview process for their Solutions Architect roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Red Hat's Solutions Architect interview process in New York, New York.