4 ms·
>As soon as we started doing them however, I saw a problem. Almost everyone was passing. Our filter was not filtering. We tried extending the duration of the in
by vdnkh 11y ago
>As soon as we started doing them however, I saw a problem. Almost everyone was passing. Our filter was not filtering. We tried extending the duration of the interviews to probe deeper and looking at code over Google hangouts. Still, the pass rate remained too high.
To me, it seems like your team isn't that good at judging ability. To compensate, you rely on coding questions. This what the industry has been doing for years. What exactly is innovative here? I see the need for coding questions (and think that your method sounds pretty good) but too often culture fit & 'soft skills' are overlooked in favor of cramming as many technical questions as possible.
One of the best experiences I had on an interview involved no coding on-site at all. I completed a project for them, they liked it, I got an interview. 3 hours of culture/team/work philosophy. There were no surprises - if I wasn't "technical enough", I wouldn't have been let in the door. It took time up front, but at least the interview itself wasn't waste of time, PTO, and money.
- paxcoder 11y agoSo you bet your time. It's how I got my job too, but that should be the norm (unless there are guarantees). Companies should cover the expenses of finding employees, instead of crowdsourcing the unemployed.
- paxcoder 11y agoI meant shouldn't be the norm. Screw these uneditable, permanent forums.
- ZanyProgrammer 11y ago3 hours of soft questions seems much more preferable to 3 hours of whiteboarding data structures. Hopefully your project wasn't a bunch of questions from an undergraduate data structures/algorithms class.
- vdnkh 11y agoThey were tough, insightful soft questions. And I asked a lot of them too. Gave me a good feel for how they worked and what they valued (which is what I really want to know). The challenge was pretty tough but it wasn't just graded on performance. The team lead came in with feedback from each member which was really good. Stuff like "you could have done this with less objects" or questions for me to resolve for them. I've used the feedback to improve my code since.
- deleted 11y ago[deleted]