Missing out on jobs because of LeetCode

[oaththrowaway]

I know some people hate take-home assessments, but for me it's a total life saver in interviews. I don't "think" out loud while I'm working, and there's no way in hell I'm doing it nervous while someone is looking over my shoulder.

Using Leetcode as a filter is great if you're looking for someone who interviews often, but in my experience it's not a great gauge if someone is a good engineer or not.

As a hiring manager we've tried implementing different strategies. On my team, we hired 4-5 engineers doing live coding exercises similar to leetcode, and none of them made it more than 6 months. We switched to a take-home project for the last 3 we've hired and they've all been with us for 2+ years and have been great.

Of course with the take home projects you're filtering for people who are willing to take a few hours of personal time to work on something, but over the interview process it seems like it washes out? Of course this is just anecdotal data on a fairly small team, but I hate LeetCode style interviews.

[some-guy]

I'm a staff engineer with ADHD and extreme test anxiety. When looking for another job during COVID I was rejected by every company at the screening stage I spoke to. The only offer I got was for Netflix which gave me a take-home assignment. It was wonderful because I had confidence in my code when I brought it back to the interviewers and could explain very clearly what was going on.

I ended up not taking the job due to the combination of a counter-offer from my employer as well as being a little weirded out by their culture. But I was thankful to get the opportunity to show my skills in a way that worked for me.

[mcntsh]

Now imagine you are a candidate interviewing with 3 companies and they all give you a take-home assignment and each one takes a weekend to complete.

[carlos-menezes]

I feel the same. I'd much rather do a take-home than a live coding intervie: it offers a much better representation of how I work daily.

[7speter]

If you’re getting quality hires with take homes, doesn’t that mean that even if theres filtering going on, its still effective to a degree as opposed to being totally arbitrary?

[nunez]

I generally dislike take homes because the grading criteria is often extremely arbitrary and making time for them alongside your day job can only be done on nights and weekends.

The only exception to this are take homes that you pair on during the interview.

[bdangubic]

We do the same thing - take home - but we pay flat fee of $250 (via Visa Prepaid Card), more to show that we value candidates time than anything else… it should take about 4 hours to finish at worst.

[lapcat]

> I had no job, I ran on my savings, and the workplace I was interviewing for looked nice. OF COURSE I WAS NERVOUS.

100% this. I've never been nervous on the job, even during a work crisis. But I'm not a stage performer, and I'm super nervous during an audition, where strangers are standing over you, judging you, and you can lose the job if you do any little thing wrong, or even if you don't do anything wrong. That's so vastly different from a workplace situation. Yet a lot of people assume, wrongly, "If they're nervous during the interview, then they can't handle job stress."

Ask a firefighter, who runs into burning buildings for a living, to give a speech in front of a crowd of strangers. It's an entirely different kind of stress. Not all stress is the same. Fear of public speaking is very common, regardless of the person's job. The firefighter is trained for and experienced with one type of stress, but not the other. Firefighting is their job, not public speaking. Likewise, programming is my job, not interviewing. I can write code just fine, even if the whole company is metaphorically "on fire" at the moment, but my brain freezes in job interviews. And then an hour later, when the interview is over, I can often easily do the thing they wanted me to do during the interview, because I'm no longer in that specific fearful state.

The good news is that I'm now successfully self-employed, and my goal is to never interview for another job the rest of my life. Of course running your own business is stressful, and everything depends on me, but I've demonstrably been able to handle that stress. In a sense, the insane job market forced me to become an entrepreneur. (I'm also getting "older", which is another issue, i.e., age discrimination. It's commonly assumed that programmers get worse with age. Fortunately, my customers don't care how old I am.)

[skarlso]

Ah envy you. I hate interviewing. I tried to put myself into positions where I present something. I actually did a LOT of presentations by now and yet every time I’m nervous. I just can’t seem to make it work with my brain. :D

[lamp_book]

LeetCode, concurrency, system design... each contrived in its own way and you can only figure them out by burning good opportunities. Reminds me of the Bridge Keeper in Monty Python's Holy Grail. My tip is just to ruthlessly ask questions because interviewers frequently are not remotely clear as they think they are.

I'll be branching off towards a different career path because of this. Tying your employability to passing these tests rather than your accomplishments as a professional is a sucker's game long term.

[p0w3n3d]

Good luck!

[skarlso]

Thank you! :) Luckily, I'm now happily employed and hopefully for the rest of my life. :D

[ilrwbwrkhv]

Leetcode is slavery for developers. Shun any company that uses that for interviews because they are cargo culting idiots.

[lcnPylGDnU4H9OF]

I don't like leetcode either but you harm your point when you compare it to slavery. You are not compelled to work. If you don't like it, you are free to walk out of the interview room and go on with your life.

[lylejantzi3rd]

It's more like sudoku for accountants.