4 ms·
I have one and it’s quite difficult because it requires the interviewer to know their shit: drill down on a feature or technology listed in the resume in the in
by SamoyedFurFluff 4y ago
I have one and it’s quite difficult because it requires the interviewer to know their shit: drill down on a feature or technology listed in the resume in the interview with the developer. Get into the technical scope, the tradeoffs, pinch points and cruxes of problem set. Understand what the definition of success was in that feature and the individual contribution involved. A dev who only passably did the work or did so heavily relying on others expertise won’t be able to answer precise trade off questions in this way. Ultimately though if they did the work they did the work, and that’s more important than any leetcode/trivia nonsense.
- Hermitian909 4y agoPeople have been re-discovering this technique for over a decade now at least. It's actually used at quite a few big tech companies, but only for strategic hires. You touch on one of the reasons this technique isn't used in general: > it’s quite difficult because it requires the interviewer to know their shit Having an interviewing team in an engineering org n > 100 with the following properties is nearly impossible: 1. Everyone knows their shit 2. Everyone cares enough to give the interview well 3. Has enough throughput to meet the company's hiring needs 4. The interviews are given in such a way that legal isn't worried we'll get slapped with a discrimination lawsuit