It’s a problem that everybody else is using the same process. (I blame it on CtCi)
It’s a problem that everybody else is using the same process. (I blame it on CtCi)
Even if you make it through the interview process, you're going to be working for people who cargo cult their business practices and surrounded by coworkers who are willing to spend vast amounts of energy on stupid things to accomplish their goals.
It's a massively negative indicator for company culture imo.
I can't remember the last time I actually enjoyed using Google's software or their libraries, I don't know why I'd work for a mini-Google.
Is your company able to back the trend when it’s obviously wrong?
I prefer money over perfect culture though.
as you said, i would never work at a company with bad interviewing practices because it means that either the employees were hired by these bad practices OR the practices changed and no one cares.
Most companies that pay very well and are competitive do it, and the reason is because we get so many crappy applicants that it remains to this day the least risky, cost effective way to filter out bad developers.
Here’s another avenue, show me your OSS work if you have it. That give me a far better picture of how you develop than LC ever could. Don’t have OSS, then a take home test also works perfectly fine or a programming exercise that’s realistic
> Here’s another avenue, show me your OSS work if you have it.
For the complaining elsewhere in this thread about how leetcode filters for people who have free time to work on it and thus selects for upper middle class... this is even worse in that regard. Furthermore, the contributions of a new grad are... often "poor".
The take-home test is similarly derided in many circles that refuse to do leetcode and the "write this program" is even less transferable to doing interviews at other companies.
The issue is that SV cargo cults extremely hard. A lot of startups copy the big companies (and often the founders of small companies are from big companies - so they take what they know with them). Then everyone is like, "SV is so cool and full of money! Let's copy everything they do to emulate their success."
That's all it is. I'm not a fan of the author (for personal reasons) of CTCI but I don't think she or the existence of the book is the issue.
The worse to me are the interviews that ask you technology specific commands (for ops positions, especially k8s) and/or specific language constructs.