2 ms·
You're preaching to the choir, but I don't choose our technical assessment. That said, it's not leetcode. I think that can work for plenty of orgs, but I'm not
by duped 5y ago
You're preaching to the choir, but I don't choose our technical assessment. That said, it's not leetcode.
I think that can work for plenty of orgs, but I'm not sure about my team. I've already worked with two people who had great references and decades of experience who couldn't contribute to what we are building due to their weak technical skills. That doesn't mean there isn't an org out there that they will fit in with better, but the current process we use was derived from experience. It's not hazing, like Google.
- karmakaze 5y agoWhen I'm in charge of hiring for a highly technical role, I'll ask them about a particularly challenging problem that they solved. The ongoing discussion with them getting me to understand the problem and solution in as much detail as they can describe serves as my 'turing test' that's hard to fake moreso than a hit-or-miss coding problem.
- b20000 5y agosome of the interviews I've been through started like that. Which is great. Then, it quickly went on to a coding test where I was asked to implement the optimal solution to a problem, which a certain woman, who wrote a book on coding interviews, and who will remain unnamed, needed almost 2 hours, to arrive at the optimal solution. I was expected to produce said optimal solution in less than 5 minutes. Needless to say, I moved on.