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

initial thoughts about teams, stages, interviews and collaboration #4

Open
sandys opened this issue May 18, 2017 · 2 comments
Open

Comments

@sandys
Copy link

sandys commented May 18, 2017

UI is like a bug tracker - from top to bottom. it can be emails... or particular events.

stages are important in bigger teams - where there are specific people are statically assigned to certain stages and these people take care of the process there. in one stage, these people can schedule interviews, do what they like and then pass people to next stage.

interviews are a particular activity. the reason this is separate than stage is because an interview can be done by people outside the stage as well (if invited). plus, one stage can have multiple interviews.

again remeber, the UI is like a bug tracker... so start of a stage is just marked by a dropdown tag and an entry in the bug tracker "Stage 3 started"

@sandys
Copy link
Author

sandys commented May 27, 2017

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
Copy link
Author

sandys commented May 27, 2017

aedc1404-38c7-11e7-80e8-86082e730a23

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.
An application has multiple Stages and each Stage has multiple Interviews. Each Interview has one-to-one relationship with a User.
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.

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

2 participants