3 ms·
Yes! This is what I use on technical interviews. I generally ask candidates to describe systems they have worked on in depth from an architecture perspective. T
by Scubabear68 3y ago
Yes! This is what I use on technical interviews. I generally ask candidates to describe systems they have worked on in depth from an architecture perspective. This very rapidly spots the BS hand wavers from those who know how their systems work. As a side effect it can also serve as a gauge on how mature or junior they may be.
- frickinLasers 3y agoI don't interview well. I wrote a program from scratch, tweaked it throughout my PhD, used it to get results for my thesis. I am quite confident in the robustness and accuracy of the program. I couldn't explain my code to an interviewer (partially because it wasn't production-ready code, but mostly because I don't interview well). I'm glad I didn't get the job. Moved on to work with people who know I'm not a hand waver.
- _ea1k 3y agoTBH, I've found there are people that can give great sounding answers that don't correspond all that well to reality. There are also people who struggle to answer, because reality is more complex than what they can easily convey to someone who doesn't already know the domain. There are pros and cons to both groups.
- scrollaway 3y agoHey if you want a mock interview in some as-real-as-possible scenario, find my post on whoishiring and email the careers@ email with your cv, I’ll make sure to get you an interview and get feedback to you.
- huytersd 3y agoI would fail this hard. Even if I write an entire system from scratch I forget the details in under 3 months.