Some organizations maintain lists of people who have either applied to roles there or who might be good candidates for future roles. They often share these lists around when other orgs in their space are hiring. (I only know directly of CEAâs list, but when I was recently looking to hire a content person, I got ideas for candidates from staff at many other orgs, often with quick turnaround that made me think they had those names on hand already.)
Typing at the speed of thought, not very confident in any of the below:
This project seems reasonable for someone to try. Obstacles that might come up (none of which seem like compelling reasons not to try):
The usual âthis will take a long timeâ obstacle that goes with any big technical project. Building this well will take hundreds of hours of someoneâs time, and job seekers will spend hundreds of hours of additional time adding their information to the system (if it ends up large enough to be broadly useful). Maybe the system will help to save even more time for hiring managers, but it seems like it would have to be quite successful to do so.
The categories youâve listed donât track the most important thing â someoneâs actual skill. When candidates are referred from one org to another, itâs often in the context of âthis person applied for our role and almost made itâ or âthis person we worked with was impressive, and you should hire them because we donât have a role for themâ. Thatâs a lot more evidence for reaching out to them than a tag on their resume.
This doesnât seem like it actually makes it easier to get hired. It could make hiring managersâ jobs easier (which is valuable), but if anything, it seems like this would increase the # of applicants per position (if orgs find it much easier to source lots of candidates). This is good for the orgs (and the world), but makes each application process more challenging for each applicant.
Put another way, someone whose struggle was âI applied to ten jobs and got no interviewsâ would now experience âI added my resume to the system and no one ever reached outâ, which seems even more frustrating.
On the other hand, someone who applied to four jobs and got four interviews might get a lot more reach-outs this way (from jobs they hadnât considered or known about), so this platformâs core function might just be âmatching the best candidates to jobs more easilyâ, which is a different sort of thing but still good.
I also wonder if thereâs a way to do this through a platform like LinkedIn that people already update regularly. Iâm not familiar with that platformâs search capabilities, but if there were some way for people to join an âEA groupâ on LinkedIn, maybe hiring managers could just filter for people in that group (and then take advantage of all the other LinkedIn filters)?
Another way to get a bunch of info added would be for several orgs to agree to handle their hiring through it â that is, rather than having their own resume collection systems, theyâd ask candidates to add their information to the centralized system.
Regarding using something like an âEA groupâ on LinkedIn, I like that concept. I think that might be a better idea for a MVP than a Google Sheet. Thanks for mentioning it. Iâll let the idea percolate for a while.
Regarding several orgs to agreeing to handle their hiring through a single system, my first thought about hiring was actually somewhat related: having a centralized hiring/ârecruiting team for multiple large EA orgs. This way, rather than organization A, B, C, and D all employing a recruiter, getting a subscription to a applicant sourcing service, learning/âtraining how to write job descriptions and do interviews, a âshared servicesâ team (part of a traditional HR model) could do these tasks for all member organizations. Iâm not highly confident that it would be a net positive, but I am intrigued by the idea and it seems worth exploring. Of course, that would require changes/âagreement from multiple large/âcentral orgs to get started, which would be another challenge.
Regarding not making it easier to get hired, my thought is that this would be something that would be âbackground active.â If there are 10 openings a job seeker is interested in, she has to spend effort to seek out (generally reviewing far more than 10) and apply to each one. If she submits information to a system like this (if I have relevant skills) then multiple hiring managers would see the info over the coming weeks with no additional effort from the job seeker. The hiring managers might not contact her if she is not a good fit, so this system might not do any good for job seeker moral. But my hunch (totally untested and unproved) is that there would be more job openings that she would be considered for. (I suspect that part of the source for my hunch is that I personally applied to a role at one organization a while back, and about a month later I got an email from a different organization saying that they had been passed my info and would like to consider me for a role; thus Iâm fairly confident that an informal network already exists.)
Some organizations maintain lists of people who have either applied to roles there or who might be good candidates for future roles. They often share these lists around when other orgs in their space are hiring. (I only know directly of CEAâs list, but when I was recently looking to hire a content person, I got ideas for candidates from staff at many other orgs, often with quick turnaround that made me think they had those names on hand already.)
Typing at the speed of thought, not very confident in any of the below:
This project seems reasonable for someone to try. Obstacles that might come up (none of which seem like compelling reasons not to try):
The usual âthis will take a long timeâ obstacle that goes with any big technical project. Building this well will take hundreds of hours of someoneâs time, and job seekers will spend hundreds of hours of additional time adding their information to the system (if it ends up large enough to be broadly useful). Maybe the system will help to save even more time for hiring managers, but it seems like it would have to be quite successful to do so.
The categories youâve listed donât track the most important thing â someoneâs actual skill. When candidates are referred from one org to another, itâs often in the context of âthis person applied for our role and almost made itâ or âthis person we worked with was impressive, and you should hire them because we donât have a role for themâ. Thatâs a lot more evidence for reaching out to them than a tag on their resume.
This doesnât seem like it actually makes it easier to get hired. It could make hiring managersâ jobs easier (which is valuable), but if anything, it seems like this would increase the # of applicants per position (if orgs find it much easier to source lots of candidates). This is good for the orgs (and the world), but makes each application process more challenging for each applicant.
Put another way, someone whose struggle was âI applied to ten jobs and got no interviewsâ would now experience âI added my resume to the system and no one ever reached outâ, which seems even more frustrating.
On the other hand, someone who applied to four jobs and got four interviews might get a lot more reach-outs this way (from jobs they hadnât considered or known about), so this platformâs core function might just be âmatching the best candidates to jobs more easilyâ, which is a different sort of thing but still good.
I also wonder if thereâs a way to do this through a platform like LinkedIn that people already update regularly. Iâm not familiar with that platformâs search capabilities, but if there were some way for people to join an âEA groupâ on LinkedIn, maybe hiring managers could just filter for people in that group (and then take advantage of all the other LinkedIn filters)?
Another way to get a bunch of info added would be for several orgs to agree to handle their hiring through it â that is, rather than having their own resume collection systems, theyâd ask candidates to add their information to the centralized system.
Regarding using something like an âEA groupâ on LinkedIn, I like that concept. I think that might be a better idea for a MVP than a Google Sheet. Thanks for mentioning it. Iâll let the idea percolate for a while.
Regarding several orgs to agreeing to handle their hiring through a single system, my first thought about hiring was actually somewhat related: having a centralized hiring/ârecruiting team for multiple large EA orgs. This way, rather than organization A, B, C, and D all employing a recruiter, getting a subscription to a applicant sourcing service, learning/âtraining how to write job descriptions and do interviews, a âshared servicesâ team (part of a traditional HR model) could do these tasks for all member organizations. Iâm not highly confident that it would be a net positive, but I am intrigued by the idea and it seems worth exploring. Of course, that would require changes/âagreement from multiple large/âcentral orgs to get started, which would be another challenge.
Regarding not making it easier to get hired, my thought is that this would be something that would be âbackground active.â If there are 10 openings a job seeker is interested in, she has to spend effort to seek out (generally reviewing far more than 10) and apply to each one. If she submits information to a system like this (if I have relevant skills) then multiple hiring managers would see the info over the coming weeks with no additional effort from the job seeker. The hiring managers might not contact her if she is not a good fit, so this system might not do any good for job seeker moral. But my hunch (totally untested and unproved) is that there would be more job openings that she would be considered for. (I suspect that part of the source for my hunch is that I personally applied to a role at one organization a while back, and about a month later I got an email from a different organization saying that they had been passed my info and would like to consider me for a role; thus Iâm fairly confident that an informal network already exists.)