Internship Pilot Working Group
The business goal is to run a pilot internship program to determine feasibility for future programs.
Attributes
Property | Value |
---|---|
Date Created | October 2, 2019 |
Target End Date | January 31, 2020 |
Slack | #wg_internship-pilot (only accessible from within the company) |
Google Doc | Internship Working Group Agenda (only accessible from within the company) |
Issue Board | Issue board |
Business Goal
Run a pilot internship program to determine feasibility for future programs.
Overview:
- Intention of hiring available candidates that perform well at the end of the internship
- Limit duration (see exit criteria)
- Open to anyone starting their career in tech (not just students)
- Timeline:
- Design in Oct
- Recruiting in Nov
- Offers in Dec
- Internship start June 2020
- We welcome applications from anyone. 100% of the active sourcing our talent acquisition department will do will be from groups under-represented in the technology industry. This is in order to make the candidate pool more reflective of society at large. Offers will be made purely based on merit.
Phase 1 - Design program
Phase 1 focuses on designing and launching the internship program with the primary objective of designing the program and getting to the point of being able to recruit and interview candidates.
Roles and Responsibilities
Working Group Role | Person | Title |
---|---|---|
Executive Sponsor | Eric Johnson | VP of Engineering |
Facilitator | Jean du Plessis | Engineering Manager, Static Site Editor |
Functional Lead | Roos Takken | People Business Partner, Engineering |
Functional Lead | Nick Nguyen | Engineering Manager, Ecosystem |
Member | Tanya Pazitny | Quality Engineering Manager |
Member | Phil Calder | Growth Engineering Manager |
Member | Liam McNally | Interim Talent Acquisition Manager |
Member | John Hope | Engineering Manager, Plan |
Exit Criteria
- Define budget =>
100%
- Determine number of internship positions available ✅
- Determine compensation ✅
- Determine budget for co-location ✅
- Communication plan =>
100%
- Choose the internship program name ✅️
- “GitLab All-Remote internship”
- Define branding opportunities for all-remote company culture ✅
- Connect with Universities, Meetup groups and Programming bootcamps
- LinkedIn, Instagram, FB ads
- Sourcing
- GitLabbers to contact their universities/Meetup groups/programming clubs
- Define communication milestones ✅
- 2019-11-05: Internal announcement of the program + handbook update
- 2019-11-15: Opening of jobs (Glassdoor, LinkedIn, Stack Overflow etc.)
- 2019-11-30 - 2019-12-15: Internship branding campaign
- 2020-01-01 - 2020-02-01: Announce who will be invited/join contribute.
- 2020-03-27: Contribute blog on interns
- 2020-06-06: Blog on kickoff + Personal stories
- 2020-09-14: Evaluation blog post.
- 2020-10/2020-11: Announce next internship (if pilot was successful)
- Choose the internship program name ✅️
- Recruitment plan =>
100%
- Define candidate qualification criteria ✅
- Ruby on Rails and/or modern frontend JavaScript framework (React, VueJS, AngularJS, Ember etc.) programming experience.
- Contributor to open source projects
- Available full-time during the course of the internship
- Able and willing to travel to the United States of America and the Netherlands for 1 week each
- Interested in fulltime employment after the internship (either immediately, or “next semester”) - no upfront commitment to GitLab required
- Create job family page ✅
- Identify sourcing targets and engagement plan ✅
- Advertising
- Advertise the roles across all traditional platforms
- Advertise on internship focussed job boards (e.g. Youtern, angel.co etc)
- University Recruitment
- Proactively reach out to and engage with universities/colleges to hold a Virtual Careers Talk to encourage students at those universities to apply.
- Proactively reach out too and engage with any associations within these universities that represent underrepresented groups and hold a Virtual Careers Talk, to encourage students to apply.
- Hold virtual talks at 5 universities in the following regions: North America, European, APAC, MENA
- Underrepresented groups
- All our active sourcing activities will exclusively be focused on candidates from underrepresented groups.
- We will be utilizing LinkedIn, meetup groups and online tech forums to identify potential candidates.
- Advertising
- Create Greenhouse vacancies ✅
- Define candidate qualification criteria ✅
- Internship program structure =>
100%
- Determine duration of the internship ✅
- 16 weeks
- Determine timing of the program ✅
- Mon, June 15, 2020 until Friday 2, October 2020.
- Decide on all-remote vs timezone alignment vs co-located cohort ✅
- Week 1: Co-located in Amsterdam
- Week 2-15: All remote
- Week 16: Co-located in San Francisco
- Define the criteria for teams to be able to request an intern slot ️️✅
- Mentorship
- Does the team have a manager and at least 1-2 engineers who are willing to serve as mentors for the duration of the program?
- Do the mentors have previous experience mentoring interns or junior engineers? Previous experience is a nice-to-have, but not a must-have.
- Workload
- Does the team have a roadmap containing low weight issues with few dependencies that would be appropriate for an intern to work on?
- Team Size and Maturity
- How established is this team? Will they be able to take on an intern without risking a decrease in velocity?
- Define expected day-to-day activities for interns (skeleton outline) ✅
- The activities during the co-located weeks (1 & 16) are still to be determined.
- For weeks 2-15 an intern’s daily schedule will generally reflect how GitLab team members work, which is to say we will not impose a rigid schedule.
- Interns will be encouraged to favor async communication and to set their own work schedule.
- Mentors and program coordinators will provide coaching if an intern needs help adjusting to remote work.
- Interns will participate in the following pre-determined activities
- Weekly 1:1 with their manager
- Weekly 1:1 with a mentor
- Weekly 1:1 with an internship program coordinator
- Weekly intern coffee chat
- 2-3 group meetings per week moderated by the program coordinator, rotating in timezone assuming we have people in more than one timezone.
- Regular pair programming sessions with mentor and other team members.
- Determine duration of the internship ✅
- Interviewing =>
100%
- Define interview process and technical assessments ️️✅
- Comprehensive Application form including
- Technical assignment
- Situational questions rather than STAR, as may not have any direct work/relatable experience.
- Cover letter asking for candidates to specifically address defined areas.
- Automated online technical assessment
- Technical assessment interview (To be confirmed whether this step will be included)
- Behavioral/Values interview panel (Candidates must score a strong yes to move on to the panel interview stage.)
- Hiring manager
- Recruiter/HR
- Misc Interviewer
- Comprehensive Application form including
- Define interview process and technical assessments ️️✅
- Measurements of success =>
100%
- Determine criteria for considering the pilot a success ✅
- Feedback rating on the program experience as scored by the interns (questions and desired score TBD).
- Feedback rating on the value and overall experience working with the intern from the teams with interns (questions and desired score TBD).
- Throughput of at least 24 MRs over the period of the internship
- Average of 2 MRs merged per week
- This takes into consideration the 16 week internship with 1 week onboarding, 1 week offboarding
- Handbook/Blog MRs will count towards throughput
- Making a job offer(s) to 50% of the interns in the program
- Determine criteria for considering the pilot a success ✅
- Assignees for the program roles ️=>
100%
- Program Lead (overall DRI) - Roos Takken
- Recruitement Lead - Liam McNally
- Program Coordinator - Jean du Plessis
- Program Coordinator - Nick Nguyen
(✅ Done, ✏️ In-progress)
Phase 2 - Kick-off program
Phase 2 starts with the launch of the internship applications and has the primary objective of overseeing the recruitment, interviewing and hiring of interns and ensuring all program details are fleshed out.
The working group will dissolve once the exit criteria for these objectives are met and the program lead and coordinators will then take over the running of the program and seeing it through to completion.
Roles and Responsibilities
Working Group Role | Person | Title |
---|---|---|
Executive Sponsor | Eric Johnson | VP of Engineering |
Facilitator | Roos Takken | People Business Partner, Engineering |
Functional Lead | Jean du Plessis | Engineering Manager, Static Site Editor |
Member | Nick Nguyen | Engineering Manager, Ecosystem |
Member | Liam McNally | Diversity, Inclusion and Belonging Partner |
Member | John Hope | Engineering Manager, Plan |
Exit Criteria
- Determine host teams =>
100%
- Facilitate Q&A session for interested teams ✅
- Review and approve team applications ✅
- Onboarding/offboarding =>
100%
- Define onboarding process ✅
- Define offboarding process ✅
- Measuring program success =>
100%
- Promote the internship =>
100%
- Blog post ✅
- Flesh out program details =>
100%
- Define “Week 1: Intern Fast Boot” program details ✅
- Define “Week 16: Intern send-off” program details ✅
- Logistical details to be handled by program coordinators after working group closes. ✅
- Hire 4 interns =>
100%
- Job offers accepted ✅
- Invite interns to Contribute - Prague ✅
- Match interns to roles in teams ✅
- Training for Mentors of hosting teams =>
100%
- Include creating opportunities for interns to ask questions/ pair programming sessions ✅
- Provide guidelines on choosing the right project/ amount of work ✅
(✅ Done, ✏️ In-progress)
Last modified October 4, 2024: Fix GitLab capitalization (
7104f09a
)