[nph5667]

I find it quite amusing the efforts programmers have to put into a job interview. Especially comparing to what they will be doing every day at job if they are accepted. It's two separate worlds - job interview and job itself.

[goodrubyist]

Yeah, I found to read that part dispiriting too. The fact that practicing on leetcode has such a substantial effect on one's chances, to me, shows that it's very likely that either employers don't know how to select candidates, or maybe, they're just trying to track the best proxy they know for job performance.

I, personally, think that the ability to write "clean code", to think and care deeply about decisions related to code when it spans multiple fiels, is way more valuable in many jobs (not all!). Yet, unsurprisingly, I see that very few give any serious thought to it, given what companies care about is leetcode.

[tomp]

Better than doctors who have to put 10+ years into a job interview...

[nph5667]

Do you think so? I am not familiar with doctor's state of things, but do they have to prepare for 10 years for each interview during their career, or just once in a lifetime to get into a profession? Are they tested on irrelevant stuff to their job's duties every time they change the job? I am genuinely interested. I see that the current state of job search/acquiring in software industry is inadequate both for employers and candidates. Both sides can tell you horror stories in that regard. And I cannot say nobody tried to innovate here. They definitely did - certification efforts, recruiter's tests, not to mention each company has it's own "system". Nevertheless, what I see here is that you are almost always tested for irrelevant stuff, stuff you can completely get out of your head the moment you are hired. Until the moment you have to find a new job. Something's wrong here.

[PragmaticPulp]

Trying to compare a few weeks of LeetCode to years of graduate school followed by years of underpaid 80-hour residency workweeks is out of touch.

Also, any programmer with a few years of experience shouldn’t have to completely relearn how to do LeetCode style problems every few years. The LeetCode easy and medium problems aren’t that difficult for anyone with a few years of experience.

Finally, I don’t understand how so many people are convinced that LeetCode problems are an entirely different domain than typical programming work. Sure, they’re toy problems, but the concepts are relevant to anyone doing things at scale that involves more than just connecting some APIs together.

[bradlys]

> Finally, I don’t understand how so many people are convinced that LeetCode problems are an entirely different domain than typical programming work. Sure, they’re toy problems, but the concepts are relevant to anyone doing things at scale that involves more than just connecting some APIs together.

But the overwhelming majority of us are just connecting APIs or what not.

Most people (even in FAANG) are not using DP in their day-to-day...

[BossingAround]

At times, I feel like job interview might be the most exciting problem solving an engineer might do for a company. After that, it's more of the same old "do this thing you've done 10 times but now in Go with go-routines."