3 ms·
Credentialing in software probably has a really short half life. I agree with the comment about how insanely inefficient it is though! I have this near conspir
by thr0waway1239 10y ago
Credentialing in software probably has a really short half life. I agree with the comment about how insanely inefficient it is though!
I have this near conspiracy theory about why the interviewing process includes such ridiculous things as balancing red black trees. Like every other regulation/tax, the propagation of crazy ideas about interviewing practices is really self serving for the tech giants. In a large orgy of stupidity, companies which can neither afford the impedance of nor are particularly good at these CS type questions mimic the practices because they are probably trying to show that they have a high bar.
Unfortunately, the multi-billion dollar companies can churn through the candidate selection process and waste more money in the process than many other companies' annual revenue. But I am sure they realize the halo effect of making a great deal of noise about this practice, because this is one of those strategies with very little downside and all kinds of unintended upside.
If I were a recruiter at one of the top 10 companies, I would spend half my time creating fictitious accounts on various social platforms to ask about the CS question du jour at these interviews. It would be the equivalent of click fraud in tech job search.
On a more serious note, I wonder if companies trying to hire these employees ever really do a cost analysis of the interview process itself? At what point does it stop making sense to "just wait till we get that truly exceptional candidate"?
- rafiki6 10y agoReally? Yet it seems that the "standard" CS101 interview is still pretty much the same. Unless you're talking strictly about credentialing for a specific language or framework which I would agree would be stupid. Also, as with other professions we can frequently update the credential to ensure it stays relevant. The IEEE has already created a software body of knowledge. There are fundamentals every software engineer should know that aren't the latest JavaScript framework.