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

As someone that has held that title at multiple FAANGS and done hundreds of interviews: please don't equate performance in the absurd interview process with ability to code.

Most of the best developers I know would fail a technical interview for their current job.



I think I just did last week. The interviewer asked me to explain SOLID. I could only remember the O and the L. All of these practices are deeply internalized but without having interviewed in a while, or even used English at work, the little speeches and buzzwords escaped me. Then he brought up REST. “What are important principles of REST?” Ummm, nounifaction? Uff.


I usually google SOLID before job interviews just in case someone actually asks about this.


I fully sympathize and I had to mute my mic once so the interviewer doesn't hear that I am searching for what SOLID stands for, and then I proceeded to explain each of the characters.

But to be fair... is that an actual technical interview?


I agree with you, but I’m talking about literal FizzBuzz-esque questions. Experienced or not, any “senior developer/engineer” should be able to write a for loop.


> Most of the best developers I know would fail a technical interview for their current job.

Yes, that's because they can't code.

(No, connecting APIs and navigating information complexity landmines isn't coding.)


Amen to that.




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

Search: