Adding a Job Application to Your Site

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
angelinardo's picture

Hi All,

Let's say your client asks you to add a job application to their site so users can fill out an application online rather than going through the outdated traditional paper process. Most big companies and job board sites today use online job applications, which is convenient for both the person applying and the employer.

My first thought was to use a module for this but unfortunately after doing some research, I was surprised to see the limited options for modules in this area. There is a module called eRecruiter but I'm not sure if that's the best way. I also heard some cons about it that seemed to outweigh any of the pros. Futhermore, I don't want users to have to have to register and login to apply. I want it to be simple.....They click a link that says apply and then they fill out an application and then they click submit when they're done.

A webform doesn't seem like the best way because it doesn't allow the site owner/employer to print out job applications as they are received. The job application data submitted in a webform will be delivered to the site owner/employer in an email format so you can see how this may not be an ideal solution.

Do any of you have any recommendations on how to create an online job application?

Thank you.

Comments

I would think the Weform

tommyent's picture

I would think the Weform module would be perfect for this. You can easily go to the submission page and print out the applications. They're all stored in the database and the data can be exported and imported elsewhere.

Also for that matter you can just print out emails if you really wanted to.

Ditto

acacciola's picture

I agree with all of the above, as I use Webform myself to collect applications for several different aspects of a non-profit program.

Angela

The approach I used

jax555's picture

I used the following approach and it has worked out great for me.
I first created a job posting content type with the fields:
Location: term reference, ( since I have more than one location)
Title: the job name that is open
Body: for the job description
Wage: if you want to include the wage
Department: term reference for the department that the posting is in.

then I created a Job application content type called Job Application
title: Applicants name
body: Their cover letter
resume: a file upload field
Job: as a node reference (referencing back to the job posting content)

Then I created a view for all job postings and a menu item to get to them
On each job posting now at the bottom of the posting you will see an "Apply for this job" and it then takes you to the job application form and they can fill it out from there. In the set up of this you can have an email sent to whomever you want with all the data and/or go online to look at all submissions. I liked this better than the webform but webforms are good too. If you decide to use a webform then I would advise using conditionals as well.
I hope this helps you out.
Regards
Don

Might want to check out entityforms

densolis's picture

Hi,

You might want to check out the entityform modules. It's advantage over webform is it creates node of entities type "entityform" rather than a submission to a node (which is what webform does).

Don't get me wrong, webform is great! I use it also. But it's main limitation is it does not create nodes. Therefore, you can only use the webform modules that have been written to interface webform with something else such as views or rules (hence the webform for views and webform for rules).

The nodes that entityforms create can be used by any other entity aware module such as views, rules, date, phone, etc.

I don't understand why you would want the application to go directly to the printer before anyone reviews the form. I would think that some would want to look at the application first to see if the person met the basic qualifications before they printed it.

Personally, I think either webform or entity forms would be a good choice.

Depending upon the complexity of your app, you can also setup both to them to allow the user to save their submission as a draft so they can complete the form at a later point in time.

Entityforms also notifies you via e-mail, which is an issue for you.

Good luck.

Thank you

angelinardo's picture

Thanks for the input everyone. AlI your input was very helpful especially the step-by-instructions (Jax555)!

Florida

Group organizers

Group categories

Florida Topics

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week