|
|
|
|
|
by the_snooze
779 days ago
|
|
It's the curse of scale. Automation allows there to be plenty of job postings and job applications, but it sidelines the human part of actually talking to someone. Those in the know will end up sidestepping this altogether and using their networks to get a direct line to a real hiring manager or applicant. I've done this myself where I talk to past collaborators and professors I know and ask "Do you have an intern/soon-to-graduate-student you recommend with skills X, Y, and Z?" This is admittedly unfair to outsiders, but if you talk to someone, there's a high reputational pressure that assures you're dealing with a real person who's likely a decent match for the job/applicant. This is valuable precisely because there's high friction and doesn't scale. |
|
Past collaborators are also a great source but she is junior and doesn’t really have any she can leverage.
My initial advice to her was do some real projects, document her work and insights in a blog and engage with others on social media but that’s mostly screaming into a void.
My approach to hiring is to focus on competencies (what do I need them to accomplish) rather than skills (how many years of JS) but that doesn’t cut down on the number of applicants any, just makes initial eval a little easier. I was pondering the idea of leaning in more on AI to screen on competencies which might incentivize higher information density on resumes but the quality of that eval might not actually be any better and only increase the “black box”-ness of it all.