Hacker News new | ask | show | jobs
by OrangeMonkey 1420 days ago
The goal of an interview is simply to identify the skills / personality of applicant. I have a role in mind when I am interviewing someone, but if their skills do not support this but it feels like there may be a good match at another team (at the right price) then I start feeling them out to see if that could be a match for them.

If their price is too high for their skills and/or I do not have a match, I politely but firmly end the interview. Be polite, wish them the best, but don't waste their time. Its the only way I can show respect to them - they have a hard path to travel.

1 comments

the goal of an interview, apparently, is to see to what extent the applicant was willing to repeatedly grind the same leetcode problems over and over again and memorize their solutions
I would never ask leetcode questions that have some trick to them. These are ones we've come up with internally and are incredibly straightforward.
i was in a FAANG interview where i was asked such a question that was internal and straightforward. the person assumed that the way they were doing this, was common industry practice. however, i have been in that particular specialization they were interviewing me for for a good 20 years and never heard of a company doing it that way. i am quite sure that the person mistakely assumed that because his FAANG did it that way, it must be industry practice.