How do you develop a solid hiring workflow? [closed]

manpreet Best Answer 2 years ago

I'm a computer Science major working at a consulting company who was given the task of restructuring our Hiring Process. I have no idea what I'm doing really. I was given a basic out line and I've been fumbling my way through some charts. I find the charts to be really annoying because of all the what ifs that need to be demonstrated, making flowcharts incredibly complicated. I'm also researching Applicant Tracking Systems will little understanding. One of the big requirements my manager had was weekly updates on passive candidates. This seems to be a feature I never see (We are a small company so that won't be too crazy of a list). Is that because its a terrible feature? I also am always seeing ATSs that are geared more towards recruiters and not towards internal departments.

One of the things I'd really like to see are some example workflows for hiring. I want to see if I'm on the right track with what I have.

manpreet 2 years ago

I don't have an example of a programmer hiring workflow, but here is an outline of what you should do to create one that fits this company.

1. What is the goal of changing the hiring? Better candidates? Decrease the time it takes to hire? Making sure no one misses anything or everyone who needs to get involved is involved. Simiplify the tracking?
2. Create a general workflow of the existing system. This may be a mess, but that's the point. If this was working they wouldn't need you to do this task.
3. Who is required to make a hiring decision? Can this list be limited?
4. Meet with employees you're glad you hired and get feedback on the good, bad and ugly parts of their hiring process. Were the interviews too long, too many, wrong interviewer, etc.

Take all of this feedback and create a suggested workflow that is much more simple. Not only should you track passive candidates, but track and encourage referals from existing employees.

Another part of this process, is everyone needing to document what they're doing. Someone is going to suggest additions, but you need to push back on the complexity issue. Usually people back-off when they discover their suggestion will create more work for them.

Finally, devise a way to measure this workflow. Does it meet the goals?