4 ms·
I interviewed a bunch and sometimes I saw folks attempting to write a perfect code snippet and it would almost always result in them not being able to finish th
by dilyevsky 2y ago
I interviewed a bunch and sometimes I saw folks attempting to write a perfect code snippet and it would almost always result in them not being able to finish the actual problem I wanted to see on time (which resulted in rejection). So after a few of those I started asking people to just get to the point first and then make it nice if there’s time
- deleted 2y ago[deleted]
- itronitron 2y agolike so? #include libutils { libutils.solveProblem() }
- Insanity 2y agoBut presumably you should be testing for people actually being able to write code, and not to solve some arbitrary problem unrelated to what 99% of engineers actually do. Being able to solve the leetcode problem tells you how well they crammed for the interview , not how well they code. And I say that as someone who is on the interviewer side of the table for the past few years at $FAANG
- dilyevsky 2y agoI never asked above leetcode easy/medium anyway and would explain solutions for some problems. That was enough to see who actually coded day-to-day and who did “thought leadership” or whatever