3 ms·
Thanks for sharing! It sounds like your questions are calibrated to detect if the interviewee is passionate. I totally get that, 15 years ago, it was obvious e
by dueF7un3 6y ago
Thanks for sharing!
It sounds like your questions are calibrated to detect if the interviewee is passionate. I totally get that, 15 years ago, it was obvious everyone around was, but those last years I find myself wondering more and more if devs around me didn't get into coding just because "it's a good job", and it looked slightly more interesting than a career in law or commerce.
> I have one big issue with recruitment process: when I meet people, after those 2 questions, I can know very quickly that I don't want to hire with them. If we are in the first 5 minutes of the interview, how can I tell them "no" without being too rude?
Been there, I feel the pain :) I had briefly a job as a manager, and I knew it was not for me when I started to panic about how to tell people I won't hire them. Still better than to have to fire them, but damn, finding a proper way to say "you're not good enough" or any other reason is brutal.
Anyway, thanks for taking the time for sharing all of that with us.
- jbk 6y ago> It sounds like your questions are calibrated to detect if the interviewee is passionate. Yes, passionate, so they will work on something cool, and are going to like it. Not passionate in the sense "I can pressure 60hours from them per week" like some SV startups do.