News for hackers. Stuff that matters.
Re:Avoiding Leetcode Anxiety by onion2k on Friday April 30, 2021 @02:15AM (#26990325)
These types of interviews favor those who have the luxury of ample time to prep for difficult interviews...

Interviews that test for anything that isn't directly related to the job the candidate will be doing are essentially codified discrimination - the expectation that someone will have a skill or significant knowledge outside of the job itself is effectively a way to filter out candidates based on arbitrary criteria even if they are capable of doing the work.

In other words, Leetcode interviews favoring people with lots of spare time is by design, because that's who companies that use Leetcode want to hire. There is little reason to believe that will change.

Re:Avoiding Leetcode Anxiety by 988747 on Friday April 30, 2021 @10:48AM (#26994135)
That's one way of looking at it. But there's also another side of it: this type of interviews let you change career path.

Imagine that you're run-of-the-mill java programmer, but you'd like to dive into Machine Learning, or BlockChain, or whatever. Some companies will require you to have 3 years of previous experience before considering you for such job. Others will give you a Leetcode interview to ensure that you're smart, and then let you learn the actual tech stack on the job.

Also, Leetcode problems might be removed from everyday development work, but most of us did learn those things at some point, i.e. in college, so asking them in the interview kind of makes sense, it's kind of "common denominator" for all programmers.

Re:Avoiding Leetcode Anxiety by pjmlp on Friday April 30, 2021 @11:07AM (#26994404)
That is wishful thinking in most cases, because unless you are targeting a startup without ageism agenda, unless the techonology is listed as something that you actually worked on (side projects don't count), the CV won't survive HR review.
Re:Avoiding Leetcode Anxiety by EvilEy3 on Friday April 30, 2021 @03:49AM (#26990800)
Nobody obliged to give you work. They gave you a task and you couldn't solve it, fair and square.

I can stretch your logic even further that giving BE task to FE person is a discrimination because they don't have luxury to work on BE. Why do we discriminate against QA people who don't have luxury to work on dev jobs? Why do we discriminate against people who don't work as developers at all?

Re:Avoiding Leetcode Anxiety by onion2k on Friday April 30, 2021 @02:15PM (#26997196)
Asking someone whether or not they can do the job isn't discrimination. Asking someone if they know something basically unrelated to the job might well be. It could be designed to filter out people who wouldn't know that thing rather than filter in people who'd be better at the job. What is that if it isn't discrimination?
Re:Avoiding Leetcode Anxiety by EvilEy3 on Sunday May 02, 2021 @05:32AM (#27013682)
Having algorithmic knowledge for a job is like having a common sense. You wouldn't hire someone who can't think, would you?