3 ms·
In my experience, interviewing for engineering teams is an afterthought that comes from how little interviewers are included in designing the interview process
by madrox 4y ago
In my experience, interviewing for engineering teams is an afterthought that comes from how little interviewers are included in designing the interview process they have to use. When I approach each opening like a software project with a kickoff, buy-in from everyone working on the project, assignment of tasks, etc, you get more investment from the interviewers. You also get higher quality candidates making it past the recruiting stage, because the recruiters better understand what to look for. Without that, I think most engineers view interviewing as something that takes them away from their "real" job.
- projectazorian 4y ago> Without that, I think most engineers view interviewing as something that takes them away from their "real" job. This. I don't want to view interviewing as a thankless chore because I think it's important, but hard to view it any other way when your interaction with any given new hire will be minimal at best - especially since the extra work of interviewing usually just ends up as a footnote come review time. If you want people to take interviewing seriously, give them some skin in the game.
- isbvhodnvemrwvn 4y agoI agree - for me the idea of shared pipelines is what kills a lot of the motivation - I don't who what the person will be working with, what on, I might have a passing familiarity with another interviewer (but most likely not) - it's difficult to treat people as anything else than a calendar appointment.