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

Change the application form to be an interactive conversation #352

Open
jace opened this issue Jul 13, 2016 · 0 comments
Open

Change the application form to be an interactive conversation #352

jace opened this issue Jul 13, 2016 · 0 comments

Comments

@jace
Copy link
Member

jace commented Jul 13, 2016

The JobApplication model records a single application and response between a candidate and a job post, with a unique constraint1 preventing a candidate from applying again. This model is simplistic and causes problems:

  1. Any further conversation happens off-site, typically breaking the employer's workflow.
  2. If the candidate forgot to include something in the submission, there's no option for them to follow up until the employer responds (which then takes it into email).
  3. Hasjob has no insight into whether the connection panned out, a requirement for us to improve matchmaking.

JobApplication should be augmented with a new JobMessage model that captures to-and-fro messages between the candidate and the employer (in the context of a specific job, or perhaps even without a related JobPost). JobApplication could remain the link that tracks the candidate's status, or be eliminated altogether.


1 Enforced at the application level rather than the database level due to an initial oversight that has resulted in multiple applications caused by users double clicking the submit button. Since responses are included in the same object, enforcing a database constraint will now require manually reviewing and removing the dupes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant