We've tried Workable, Lever and about half a dozen other platforms. None of them stuck.
What has worked is to do everything in GitHub.
We wrote about it a few years ago [1] and should probably write an updated version of our approach, but in a nutshell;
- When candidates apply through our online form on our website or via email, we create a GitHub issue and assign it to the right person on our team.
- Everybody on the team gets to see who's applying and can easily take part into the discussion.
- We wrote a few small Chrome extensions that act as helpers for managing applications. For example Gdocs Preview [2], which allows us to display the preview of attachments (i.e. resumes) in the GitHub issue directly.
- We've added some automation with Zapier [3] (and some Python) to do things like;
- Automatically close an issue and email the candidate if we label the issue as "To reject",
- Automatically pull email answers from the applicants in the issue thread,
- Automatically send an email asking people to book an interview time with Calendly [4]
- ...
Now, this works mostly because we're a software company first and we're using GitHub for everything [5]. Additionally, compensations and feedback on applicants are shared with the whole team, not sure every organization would be comfortable with that level of transparency.
The main benefit is that there is virtually no friction for team members to help out with recruitment and share their opinion.
It's also part of our on-boarding to point new employees at their recruitment issue; they get to see what we discussed and how we perceived them through the process.
This is impressive, mainly because of the level of clarity around the hiring process and your group's transparency around compensation and candidate feedback. Kudos. Most orgs wouldn't even consider something this open.
What has worked is to do everything in GitHub.
We wrote about it a few years ago [1] and should probably write an updated version of our approach, but in a nutshell;
- When candidates apply through our online form on our website or via email, we create a GitHub issue and assign it to the right person on our team.
- Everybody on the team gets to see who's applying and can easily take part into the discussion.
- We wrote a few small Chrome extensions that act as helpers for managing applications. For example Gdocs Preview [2], which allows us to display the preview of attachments (i.e. resumes) in the GitHub issue directly.
- We've added some automation with Zapier [3] (and some Python) to do things like;
Now, this works mostly because we're a software company first and we're using GitHub for everything [5]. Additionally, compensations and feedback on applicants are shared with the whole team, not sure every organization would be comfortable with that level of transparency.The main benefit is that there is virtually no friction for team members to help out with recruitment and share their opinion.
It's also part of our on-boarding to point new employees at their recruitment issue; they get to see what we discussed and how we perceived them through the process.
[1]: https://wiredcraft.com/blog/github-as-your-recruitment-platf...
[2]: https://github.com/Wiredcraft/gdocs-preview
[3]: https://zapier.com
[4]: https://calendly.com
[5]: https://wiredcraft.com/blog/github-for-everything/
reply