diff --git a/hiring.qmd b/hiring.qmd index abee239..9339d45 100644 --- a/hiring.qmd +++ b/hiring.qmd @@ -60,7 +60,7 @@ How to download application(s) from [Talent website](https://talent.arizona.edu/ 2. Go to hiring dashboard 3. Top right of page click menu --\> "Recruit" --\> "Bulk Download Applications" 4. Click number under Applicants column -5. Select checkmark for all candidates desired +5. Select check-mark for all candidates desired 6. Click "Download" button Committee members will perform a first pass at screening the applicant pool. @@ -79,7 +79,7 @@ The goal here is to provide rapid response to applicants who do not have key ski - Substantially less competitive based on skills or work experience. - A generic cover letter that does not address the specific position or area of research. - Little relevant work experience---this can demonstrate a lack of understanding of the position. *A cover letter that does address this lack of experience and hopes to learn will be viewed favorably.* -- A history of short term positions that indicates a low probability of becoming a long term member of the group. (This does not apply to students or early career professionals). +- A history of short term positions that indicates a low probability of becoming a long term member of the group (this does not apply to students or early career professionals). - Lack of career progression, evidence of being self-motivated - Poor communication skills as evidenced by cover letter and resume. For example, the cover letter should use paragraphs, complete sentences, and contain few typos or grammatical errors. @@ -94,7 +94,7 @@ The goal here is to provide rapid response to applicants who do not have key ski #### Screening interviews -- [List of questions not to ask](https://hr.arizona.edu/supervisors/recruitment-hiring/guide-successful-searches/questions-to-avoid) +- [List of questions **not** to ask](https://hr.arizona.edu/supervisors/recruitment-hiring/guide-successful-searches/questions-to-avoid) - Create list of interview questions in HackMD or Google Doc - See appendix below for possible interview format and questions - Should take about 30 minutes @@ -110,15 +110,15 @@ The goal here is to provide rapid response to applicants who do not have key ski - After, each interviewer fill out copy of skills matrix in new tab with yes, no or, maybe - Also write small paragraph about interviewee -#### In-person interviews +#### Second round, full-day interviews (virtual, via Zoom) - Compare results from screening interviews by and across each interviewee -- Decide who to invite to in-person interview (meeting or asynchronously) +- Decide who to invite to second round interview - Send out rejection emails if applicable - Send emails to schedule interviews (will require some back and forth) - This can be facilitated by asking candidates to rank a range of dates. - Create tentative schedule (will require some back and forth) - - Likely full day, including lunch and presentation + - Likely full day, including breaks and presentation - 1/2 hour orientation with Kristina - 1 hour: 30 min presentation, 30 min Q&A - 1 - 1.5 hour with each team member @@ -135,7 +135,7 @@ The goal here is to provide rapid response to applicants who do not have key ski #### Final hiring decision -- Entire or subset of group discuss results (meeting or asynchronously) +- Entire or subset of group discuss results - Choose yes or no for each interviewee - Send rejection emails if applicable - Kristina has salary discussion with individuals we want to hire @@ -167,7 +167,7 @@ Salaries in DIAG range from \$30k for a recent graduate to \$85k for developers *Note: 6 and 7 are specific to a pipeline job; other positions may have additional required/desired skills* | Category of interest | Description | -|------------------|:----------------------------------------------------:| +|------------------------------------|:---------------------------------------------------------------------------------------------------------------------------:| | **1. Learning new skills** | Demonstrates ability to acquire new skills, especially technical skills, through self-teaching or by reaching out to others | | **2. Collaborative** | Works well with a group and are able to problem solve with others | | **3. Software development skills** | Able to demonstrate using software tools to solve problems | @@ -247,23 +247,24 @@ Another example: > > Zoom link for interview: https://arizona.zoom.us/my/kristinariemer > -> The questions we'll ask are: 1. -> What led you to apply for this position, and how do your qualifications make you a good fit for the job? -> 2. -> For a particular collaborative project, preferably one that included coding, what was your role, what worked well, and what would you do differently if you were the lead? -> 3. -> A primary focus of our group's mission is training researchers. -> Can you tell me about one or two outreach or education activities you have been involved in? -> What similar activities would you be interested in implementing at University of Arizona to build computational and data science capacity? -> 4. -> What is your approach to staying up to date on new technologies and skills? -> 5. -> A key component of this job is to work on many projects simultaneously. -> How do you manage and prioritize multiple projects that you are working on?\ -> 6. -> Do you have any questions for us about the group or the position? -> -> We realized that our group's website is not linked on the job ad, so in case you haven't already found it, you can find more information about what we do here: https://datascience.cct.arizona.edu/ +> The questions we'll ask are: +> +> 1. What led you to apply for this position, and how do your qualifications make you a good fit for the job? +> +> 2. For a particular collaborative project, preferably one that included coding, what was your role, what worked well, and what would you do differently if you were the lead? +> +> 3. A primary focus of our group's mission is training researchers. +> Can you tell me about one or two outreach or education activities you have been involved in? +> What similar activities would you be interested in implementing at University of Arizona to build computational and data science capacity? +> +> 4. What is your approach to staying up to date on new technologies and skills? +> +> 5. A key component of this job is to work on many projects simultaneously. +> How do you manage and prioritize multiple projects that you are working on? +> +> 6. Do you have any questions for us about the group or the position? +> +> We realized that our group's website is not linked on the job ad, so in case you haven't already found it, you can find more information about what we do here: > > Please don't hesitate to contact us with any questions or logistics issues before the interview! > @@ -288,64 +289,13 @@ Another example: > > \[interviewer names\] -#### 4. Initial in-person interview - -> Dear \[full applicant name\], -> -> Thank you for interviewing with us recently. -> We would like to bring you on campus for an in-person interview. -> -> The interview would be approximately four hours in the Biosciences Research Laboratory building on the University of Arizona campus followed by either lunch or dinner with the group. -> During the interview, you would be meeting with Dr. Kristina Riemer, who runs the group, the members of his group, and our collaborators in the Data Science Institute. -> -> We will cover the cost of meals and travel expenses. -> Please let us know about any accommodations that would facilitate your interview; we want to provide an inclusive and comfortable experience. -> -> We would like to have the interview on \[date(s)\]. -> You can opt for morning (8am-noon) or afternoon (1-5pm). -> Please let us know which days and parts of days you prefer. -> -> We can also do a later date if that would work better, please let us know. -> -> Thank you for your interest in this position, and we look forward to meeting you. -> -> Sincerely, -> -> \[interviewer names\] - -#### 5. Details in-person interview - -> Dear \[full interviewee name\], -> -> This is to confirm that you are scheduled to interview with Dr. Kristina Riemer's group on \[date\] from \[time\] at the Biosciences Research Laboratory building on the University of Arizona campus. -> -> Below is the planned schedule for the interview: -> -> \[interview schedule\] -> -> The interview will happen in the Bioscience Research Laboratories (BSRL) building located at 1230 N Cherry Ave (https://goo.gl/maps/yTbKipGD6p2ZvFzb6). -> Meetings will be on the second floor, which requires a key card to access, so a member of the group will meet you on the south side of the lobby of the building at \[time\]. -> -> If you are driving to campus, you can park in the Highland Parking Garage one block west of the BSRL building (https://goo.gl/maps/HE3eBnQbyUMs2x8Y8). -> Parking is \$8 per day, which will be covered. -> -> Another way to get to campus is the streetcar, and the eastern terminus is right next to the BSRL building. -> Alternatively we will reimburse rideshare service charges. -> -> Please let us know if you have any questions about the interview format or logistics. -> We are looking forward to meeting you! -> -> Sincerely, -> -> \[interviewer names\] - -#### 5b. Full-day Zoom interview +#### 4. Full-day Zoom interview > Dear \_\_\_, > > I hope this email finds you well. > Following your recent short interview, we were impressed with your qualifications, experience, and the insights you shared. -> We would like to invite you to a full-day interview in the week of May 15--19 to provide you an opportunity to meet the rest of our team, learn more about the position, and give us all some more details about your background and interests. +> We would like to invite you to a full-day interview in the week of May 15––19 to provide you an opportunity to meet the rest of our team, learn more about the position, and give us all some more details about your background and interests. > > We are still finalizing the format but the agenda will include: >