Skills & Training Events - Application process

# Skills & Training Events - Application process ``` Authors: Bridget Nea, Sarah Nietopki, Chloe Poon, Mishka Nemes, Amy Gallimore ``` [TOC] --- ## 1. Current application process The Skills Team runs the process together with the lead trainers who are asked to first fill in [a HackMD template](https://hackmd.io/5qF9uqKkRSOuzl5unPZHhA) to request detail about the event, and the Skills Team uses this information to create an EventsForce application page. ### Changes Clarifications on process - Selective application / scored highest on statement of motivation and comparative to quality of apps - Turing places are prioritised - X amount of spaces/X of applicants/first come first served for application review - do we still need a deadline as well? ## 2. Current reviewing process ### Changes ### Responsibility matrix ## 3. Current delivery process ### Changes ## 4. Current evaluation process ### Changes - Team delivering training absolutely need to be involved in selection process - ideally 2-3 reviewers per application - EDI checks should not be carried out by same people doing reviews ## Questions/clarifications - Should we allocate a % for Turing or continue to allow all? - Should we put a limit on the amount of apps? (cap at 150?) - cap at 3x amount of spaces - REG courses - need input as content too technical - RSE split into two (intro/intermediate) - Need new application questions designed by team running training - confirm entirety - Take attendance/cert of attendance and hold accountable to deter drop-out rates ## Skills Team's role - Set up application (events page & application form) - Promotion - Logistics and admin - Eligibility checks - EDI reviews ## New process - Revised application form from hosting team (adapt Skills template) - Set up and promote application (2/3) - mitigate numbers of applications - Eligibility checks from Skills Team (1 day) - Shortlisting from hosting team (2-3 days) - Final selection meeting w/ host and Skills team (1 day)- optional - EDI reviews (TBC) - Logistics and admin (emails, Slack, home page, feedback) - Zoom links to be hosted by host team ### Developing selection criteria for Turing RSE/RSD courses - Clear and fair criteria - Aims and objectives (feedback learning aims to community) - Signpost opportunities to learn about Turing REG roles as opposed to training course - Lottery 50% - Enable enrichment students - maybe reserve some places? 50% for Turing people - put other 50% back in pool for lottery - open registration earlier? - Worth capping number of applicants? - not a good idea in this case - Questions to ensure engagement - Initial multiple choice questions/eligibility - Collaboration examples - Why are people not engaging? - Initial filtering - maybe a programming test? is this an additional barrier - Cannot select on protected characteristics: - age, disability, gender reassignment, marriage and civil partnership, pregnancy and maternity, race, religion or belief, sex, and sexual orientation - might be legal to consider positive action for disability (unlikely we have this information) - can possibly use location (want national reach) - decide with Skills Working Group - can use discipline