welcomemat

[sandys]

this is new codebase

1. for now, top level domain is welcomemat.hackergully.com
2. anybody can create a subdomain - like abc.welcomemat.hackergully.com
3. issue please use ActiveJob to fire emails - right now they are blocking #14 needs to be incorporated.

the initial goal is to build the simplest poc to handle complex email routing. you will continue to use mailgun.

1. create a job - just takes email and some text. same as before - other collaborators can be added for this job.
2. applicant applies for job. it creates an "application"
3. autoreply goes to applicant careers+f30pttd3@abc.welcomemat.hackergully.com. "f30pttd3" is unique to application.
4. if candidate replies to this email - it is saved in the "application" and all the collaborators will be copied.
5. collaborator can reply from "application" dashboard and the candidate will get a reply on his email as well from careers+f30pttd3@abc.welcomemat.hackergully.com
6. collaborators can send an internal note to each other from dashboard. it will be sent from collaborators+f30pttd3@abc.welcomemat.hackergully.com - it will not be visible to candidate. WARNING: even if candidate tries to send email to this address... it will be rejected.
7. change of state of application will send email only to collaborators. again from will be collaborators+f30pttd3@abc.welcomemat.hackergully.com
8. be able to send emails to multiple people (selected by checkbox). each one will receive the mail from their custom email address (so they can reply to it)

Next step:

1. customize application form fields. maybe use postgresql jsonb
2. search for applications
3. bulk import from file.

[sandys]

templates for emails is very important. huge productivity boost.
also - "remind me about this in X hours/days/months"

[sandys]

employee referrals and interview scheduling are the next important things.
for interview scheduling - it should have a customizable form. I can invite an interviewer for that interview who will get a unique link and he can conduct and fill in the interview form.

[sandys]

the most important feature is going to be interviewing

1. I should be able to invite outside parties to a particular interview session. they should only see that interview session and NOTHING else. So "Interview" must be a different model.
2. An application has multiple Stages and each Stage has multiple Interviews. Each Interview has one-to-one relationship with a User.
3. Once an interview is saved, it cannot be edited. it can be "soft deleted" and a new interview taken, but never edited.

Once an interview has been scheduled - it should have reminders built into it.

[sandys]

bulk import - all extra fields should be imported and automatically created in the applications.
Internshala_open_Applications_for_UI-UX Designinternship_2017-05-14 17-15-30.zip

this means that each application can have different fields - and can differ from application to application.

[sandys]

email confirmation - when an application is made, send an email and ask for confirmation click on link. show the application with a "email confirmed/not-confirmed" status on top in both cases.
maybe we should also put captcha underneath

[sandys]

helpful reminders - two kinds of jobs (temporary and permanent). if a person is moved to state "selected", then ask for start date and end date.

send reminders to everyone in the application (collaborators and applicant) reminders before and during end of internship.