3 ms·
I'm hiring right now, and I read a lot of job descriptions before I wrote ours. [1] I've definitely seen what she's talking about: generic go-hire-engineers job
by wpietri 11y ago
I'm hiring right now, and I read a lot of job descriptions before I wrote ours. [1] I've definitely seen what she's talking about: generic go-hire-engineers job descriptions. I also think the kind of thing you describe, hiring for a very specific technology, is a similar failure mode. The technological pain point of the moment rarely lasts; the more stable needs are actually organizational. For example, over the next couple of years I want to be able to hire junior engineers, so right now I'm much less concerned with a particular technology stack than with someone who really likes mentoring and working in closely collaborative environments. That way I can bring the junior people rapidly up to speed.
I also have seen whiteboard coding interviews where interviewers are inclined to ding people for not remembering small details, so it's a legitimate concern.
[1] http://www.codeforamerica.org/jobs/chime/ http://www.codeforamerica.org/jobs/chime/