Then I guess I won't work there. There are a ton of very good companies that don't believe in competitive programming as a way to interview.
Just to clarify, I have no problem with technical assessments/challenges as interview questions. My issue is with competitive type programming and judging someone purely based on solving them correctly.
I will work where I am a member of the team. When you are interviewing for a company you should also be interviewing them and have just as many questions for them. See if you find yourself fitting in there. If I don't see that then I won't take the job.
I have personally turned down some interviews to go further because I can tell it's not a place I can see myself happy at.
Chad is not talking about whatever is fair for the company, he's talking about better ways to approach job candidates on which I completely agree.
I can assure you I'm not the best full stack developer, but beyond my decent skills, I would say my personality has opened many doors at workplaces than my skills, to the point that managers don't want to let me go, offer salary increases, and even give me side jobs after leaving the company. All that occurs because I am a team player, provide great customer service, are positive on any situation (issues) 99% of the time, have a sense of humor, doesn't get easily offended, are reliable, etc. Most of those personality traits are difficult to show when asked to code something too difficult.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's up to the employer on what they decide for the interview and how they eant it to be done, and if you want the job you do what they ask you.
Then I guess I won't work there. There are a ton of very good companies that don't believe in competitive programming as a way to interview.
Just to clarify, I have no problem with technical assessments/challenges as interview questions. My issue is with competitive type programming and judging someone purely based on solving them correctly.
I will work where I am a member of the team. When you are interviewing for a company you should also be interviewing them and have just as many questions for them. See if you find yourself fitting in there. If I don't see that then I won't take the job.
I have personally turned down some interviews to go further because I can tell it's not a place I can see myself happy at.
I understand and I just think it's fair for the company to have the interview their way, it's up to us at the end.
Chad is not talking about whatever is fair for the company, he's talking about better ways to approach job candidates on which I completely agree.
I can assure you I'm not the best full stack developer, but beyond my decent skills, I would say my personality has opened many doors at workplaces than my skills, to the point that managers don't want to let me go, offer salary increases, and even give me side jobs after leaving the company. All that occurs because I am a team player, provide great customer service, are positive on any situation (issues) 99% of the time, have a sense of humor, doesn't get easily offended, are reliable, etc. Most of those personality traits are difficult to show when asked to code something too difficult.