@httpjunkie
's comment on front-end interviews was just frustrating to read (in a good, thought-provoking way). I know that times are changing and all, but the fact that I've heard stories of front-end interviews including questions about sorting algorithms and computer science-related problems makes me feel like the whole interview process for front-end development nowadays is unnecessarily complex. It's truly frustrating!
I get that companies are looking for the cream of the crop (in accordance with their coding style and philosophy), but isn't it frustrating how someone who is really good at UI gets rejected just because, for example, they didn't know how to implement a bubble sort in JavaScript or some other related programming language to the job description? It's just insanity.
Anyway, that's my take on it. It just really bothers me that seemingly unrelated topics to the job description are prerequisites for a job that is unlikely to even encounter those topics. Don't get me wrong; I totally agree that learning new things (such as algorithms and whatnot) and improving as a programmer are great, but at this scale, it's just atrocious.
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.
@httpjunkie 's comment on front-end interviews was just frustrating to read (in a good, thought-provoking way). I know that times are changing and all, but the fact that I've heard stories of front-end interviews including questions about sorting algorithms and computer science-related problems makes me feel like the whole interview process for front-end development nowadays is unnecessarily complex. It's truly frustrating!
I get that companies are looking for the cream of the crop (in accordance with their coding style and philosophy), but isn't it frustrating how someone who is really good at UI gets rejected just because, for example, they didn't know how to implement a bubble sort in JavaScript or some other related programming language to the job description? It's just insanity.
Anyway, that's my take on it. It just really bothers me that seemingly unrelated topics to the job description are prerequisites for a job that is unlikely to even encounter those topics. Don't get me wrong; I totally agree that learning new things (such as algorithms and whatnot) and improving as a programmer are great, but at this scale, it's just atrocious.