Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's a difference between live coding round and leetcode rounds where you need to perfectly write code for as medium or hard leetcode question in 20 minutes.


1) that’s not what most companies do

2) if you have thousands of applicants for a position, and probably a dozen stand out by passing a really tough bar, wouldn’t you want to find those dozen?


> 2) if you have thousands of applicants for a position, and probably a dozen stand out by passing a really tough bar, wouldn’t you want to find those dozen?

It's a reasonable assumption, but you might not. If the role doesn't actually require those skills you might hire someone who's going to get fed up and leave in 3 months or (worse) who invests time in making their job more interesting instead of solving your actual business problems.


Good points. Most FAANG/MANGO companies in India do leetcode. And I know Amazon still does leetcode in US/Europe.

So, yeah, you are right. Live coding is very good, which is what I do, but too many people confuse live coding with just leet coding.


The question is, however, whether this is a good proxy for one's future colleague and employee.

I have no idea what could be a better option (well, maybe preparing some small feature to work on together), but it often turns out that good problem solvers are not really great at doing the job, for reasons that have nothing to do with the hard skills.


Totally valid critique.

Hiring is really hard. You only get a few hours to decide whether someone will be a good engineer and colleague for several years.

By the nature of the constraints alone, anything you do will be extrapolation, and a guesstimate at best.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: