-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Design a rating system for interview preparedness #139
Comments
@TobyShanti The example of the rating system (see screenshot below from the deck) is not a good one. Let's keep it as a 1-5 or 1-7 Likert scale. Thank you! |
This comment was marked as resolved.
This comment was marked as resolved.
@TobyShanti Please provide update when you can.
|
Progress: Roll call tables have been added. I need to identify which recordings we have by cross referencing the roll call table and where the recordings are housed. I need to also review the recordings to identify pitfalls and compile a list of them and design the rating system. |
Availability for this week: 6 hours Provide Update
**Please note that interviews for interns 5 and 8 are not in the "Intern Exit Interviews" folder, but were found in the "TWE: IS22: RP012: Intern Exit Interview Roll Call and Session Table" column "Recording link" |
Availability for this week: 6 hours Provide Update Progress: I have completed reviewing the interviews. |
For next steps, we need to confirm:
|
@pandanista We discussed most of these today during our team meeting:
|
@priyatalwar Thank you for answering them. I will list the questions above to the Q&A issue and double check with Bonnie after she is back. |
Dependencies
Overview
We need a rating system for interview preparedness so that we can measure the improvement in their preparedness based on our coaching.
Action Items
Resources/Instructions
1.01 Example of rating system from linkedin deck
1.02 Interview recordings: IS22 Candidate Application Interviews; IS21 Candidate Application Interviews
1.03 TWE: Interview Summary Template
The text was updated successfully, but these errors were encountered: