Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vacancy builder and applicant tracker #323

Open
GDay opened this issue Jun 21, 2023 · 0 comments
Open

Vacancy builder and applicant tracker #323

GDay opened this issue Jun 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@GDay
Copy link
Member

GDay commented Jun 21, 2023

This is a little sidetracked from the "onboarding" aspect of ChiefOnboarding, but would definitely make sense to add as an optional thing.

This would consist of two parts: the "job application builder" and the "applicant tracker".

Job listings

List view of all open jobs

This page would list all open jobs, as well as show pictures and/or more information of the company. This page would be easily customizable and you can change the look by:

  • Selecting a few base colors
  • Uploading your own images for a slide show/gallery part
  • A multi purpose textarea (WYSIWYG) to write about the culture, benefits, etc

Individual job listings

This would list the actual job listing. Job listings get their own unique link.

  • You can use the WYSIWYG editor to modify the text (it also allows videos or images if you like). We will use templates (just like we already do in other parts of ChiefOnboarding), which can be used as a starting point for new job listings. These should be fairly generic.
  • Option to send applicant an automated email (can be configured per job application)
  • There will be an option to add one blind application to allow anyone to apply to if they don't see a specific job post that would suit them, but still want to work there.

Applying

Job listings will have a form that can be filled out by an applicant. These forms are very customizable for admins, very similar to how we create forms for todo items. Any of these fields can be made required. First name, last name and email fields will always be there as a minimum. The different types of fields would be:

  • Small text field
  • Large text field
  • Upload field
  • Select field
  • Checkbox field

The form will be protected by captcha to avoid spam (Google captcha, hCaptcha or roll your own simple q&a based catpcha)
Uploading files will be heavily restricted by AWS bucket permissions (size and file type). Uploads will go straight to AWS to avoid server load/potential security issues.

Applicant tracking

A new section in the admin dashboard will be added to allow a user to switch to the "hiring" part of the application. This a different part of the application with a new navigation bar to be able to fully focus on the hiring part.

The "start" page will show a list of all job postings (including the ones in draft/closed/open). Each job posting will show how many total applications there are for the position and how many have not been seen yet by the currently logged in user.

  • Clicking on a draft job listing will take the admin user to the job application builder. Any admin/manager user can edit this page and publish it to make it available to everyone.
  • An open listing will also have an "applicants" tab. This will be a kanban board with multiple stages (can be customized by admin) to drag the applicant to. Two columns will be required: "New" and "Rejected". All new applications will automatically be put in the "New" column. If an application gets dropped in the "Rejected" column, then it will pop up a modal with a form with a canned message which can be customized to send to the applicant (this can be toggled off).
  • Clicking on an applicant will take the admin/manager to the applicants profile, which will list all details about the applicant. There will also be a place to chat between managers/admins about this applicant and there will be a place where emails can be send to this applicant and also received from this applicant. This will rely on inbound and outbound email and the email provider will have to support that to make this work.
  • Once an applicant is hired, it can easily be moved to the "onboarding" part of ChiefOnboarding to be onboarded.
@GDay GDay added the enhancement New feature or request label Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant