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

I like the writing on this article a lot more than I thought I would, some of the advice is sound - but the big caveat is most of this has nothing to do with a first round interview. What the author describes here are pieces that will come up in a typical interview process somewhere, but probably not a first round.

First round to me is typically a “bozo filter” - screen out individuals who are clearly unqualified or who are an obvious bad fit.

Any decent dev should get past round 1 without significant prep.



The article calls this out, stating that they define the first round interview as the one after a phone screen/video screen.


So it is like two screens before the “real” interview? Weird. Sounds like a very lengthy process!


Yep. Hiring is expensive.


But it didn't used to be, and not because of inflation. Somehow old school companies like IBM, Hewlett-Packard and NASA managed to hire top engineering talent by doing single interviews instead of multi-day seven interview slogs.


I’d imagine a smaller applicant volume helped a bit there.


I think some companies send junior techies to do first round filtering (with easy coding questions), while others keep the HR folks busy doing first round filtering (with, well, behavioural etc. questions as outlined in the article).




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

Search: