Right now I have it set that a user has to be registered and logged in to apply to a job. This means, if a guest visits the site, they click the apply link and it tells them to register first. This is a HUGE turnoff for many people. I see many jobs on my site with several hundred views and only a handful of actual applications, because people don’t want to have to create an account on every site they visit. However, I don’t want to allow guest applications because I want to capture these people!
So the goal should be to make them register, but not make it feel like they are having to register for yet another website. Does that make sense?
So here is what would be best: Add functionality to the existing registration page to instead make it an application page if the user is clicking from a specific job. From a coding point of view, that would mean when a user clicks the register link from the job page, they would be sent to the same page as before, BUT not only would it register them, but it would also submit their application to the job they were looking at. That way, they apply for the job, while not feeling like they had to register for yet another website in the process.
This changes the workflow from this:
1) Visit job
2) Click registration link (which nobody wants to do)
3) Register for website
4) Click back to job
5) Apply for job
To this:
1) Visit job
2) Click registration/application link
3) Apply for job/Register for website (in one step)
Does that make sense? I promise it would dramatically increase the number of applications per view rate!!