4 ms·
I find a 30 min technical interview really weeds them out. Ask them what they think about so and so technology that they put on their resume. "Why do you prefer
by muzani 5y ago
I find a 30 min technical interview really weeds them out. Ask them what they think about so and so technology that they put on their resume. "Why do you prefer MVVM over MVC? What's your experience with Jetpack? Why did you migrate code over to Jetpack over something like RxJava? You put TDD on your resume, is there any reason you prefer that over just writing tests on completed code? You mentioned functional programming on your resume, but why didn't you put a map() here?"
These questions are basically fizzbuzz for those who have done the work. But you'd be surprised how many people do things for absolutely no reason.
The downside is people tend to hire them anyway when they flunk the technical interview but have excellent leetcode score. One is fairly subjective, the other is objective, and people tend to lean towards the subjective one. You can work around this by having two technical interviewers, but they have to be fairly senior enough to trust.
- b20000 5y agoso do you think people lie on their resume? if you think they do, keep this bias in mind.
- muzani 5y agoOn a skill rating of 1-20, I'd say most resume items are 2-6. It's fine. Unless you're FAANG or a higher tier startup, you're not going to get applicants with over a 15. Most of the time, you hire someone with a 4 and take them to 9. The scale is fairly logarithmic, like a 8 might be 10 times better than a 3. 1 is hello world, 2 is being able to debug something with stack overflow, 3 is your fizzbuzz tier of being able to chain three concepts together, but not able to build anything without help. And then there's the Dunning-Kruger peak. Most evangelists are like this. They're very excited for a technology, but you find that they have no practical skill in it. Very often, they misunderstand the concepts too.