Before every new class, we make sure to interview our potential students as a final step before acceptance into the course.
Get to the know the applicants
This is the first time we've ever met them! We have to be sure we can work with them for the next eight months
Assess that the applicants have retained the knowledge they have learnt in the previous steps
We should also confirm that the applicants actually did the work themselves
Assess the applicants have a good level of spoken English
Students might have got help from friends and family for written work
Make sure you have all of this information before you have your first interview
You have access to the Dashboard (or alternative way of getting information about the applicants)
If you do not have access, speak to your coordinator
Read this document fully
Make sure you have access to the interview form mentioned in the
Interview Days section
Make sure you have read the Interview Rubric
Make sure you have at least two volunteers welcoming the Applicants to the interviews. Record their attendance, give them a tour of the premises and get them a coffee or a tea. These interviews can be very intimidating for some of our applicants so you should take time to make sure that people feel welcome and safe.
Take time to explain that the interviews are to get to know them better and that if they've made it this far then we think they have great potential.
In this context a technical interviewer is somehow who is comfortable asking questions about code and programming skill. Personal (or non-technical) interviewers should access student soft skills and motivations to do the course. It is encouraged for interviewers to justify their decisions to each other.
Interviewers will typically have thirty minutes to conduct each interview.
Both technical and non-technical volunteers should:
Aim to be as objective and fair as possible
Be mindful of their biases
If in doubt, record more information than you think is necessary
Take notes on the applicant when they the other interviewer is talking
Personal Interviewers should focus on questions surrounding
Why the applicant wants to be a programmer
How the applicant will find time to do the course
Any support that the applicant may need during the course
This will mostly be the first section of the form.
Technical interviewers should focus on questions surrounding
The applicant's work that they have submitted
Assessing the applicant current understanding of programming (none is required but it's good to know)
This will mostly be the second section of the form.
You can find a guide for this section of the interview here
Our applicants come from a wide variety of backgrounds. You can see lots of background information on our students here
Interview days generally run the whole day and require a large number of both technical and non-technical volunteers.
As applicants arrive they should be taken to a quiet space with one technical volunteer (someone who understands code) and one non-technical volunteer.
Together they should complete this form:
The class coordinator should duplicate this form for each Class. Please contact your class coordinator for access to this Google form.
We ask that you arrive at least ten minutes before the interview that you will be attending to prepare.
You can find a guide for the technical section of the interview here
You can find an English Assessment test here.
The guide for the assessment can be found here
When completing the form you should endeavour to write as much as you can for each candidate as this will be our primary resource for deciding who will get a place on the course.
It is important to be firm but fair in grading applicants. Do not give a applicant 10/10 for everything just because you like them.
We will be cross-referencing scores against feedback recorded so it is important to always give a full description of how applicants responded to questions in the interview.
You should make sure you use the Interview Rubric to grade students responses.
When selecting applicants it is important to keep in mind that a applicant can be of too high ability as well as too low.
A applicant with too low ability may
not understand English to a sufficient level
not be able to explain their code well enough
not show a particularly great drive to be a programmer
A applicant with too high ability may
already know how to program to an advanced level
have studied programming for a prolonged period of time
be capable of getting a programming job already
It's important to spot both lower and upper bound applicants as our course may not be the right fit for them at this time.
For lower bound applicants, a referral to a less intense programming course or further English lessons may be a better solution. Our course can be very challenging for people and if we're not sure that they're ready then we should endeavour to be upfront and supportive wherever possible.
For upper bound applicants, it may be preferable to give them the skills they need to be able to get a job and have them start applying. This could take the form of personal development lessons or some sessions working on our tech projects. We're in the business of finding jobs for the people and if the most efficient way to do that is by not joining our course then that is the best outcome.
When selecting applicants your primary aim should be to answer this statement.
I believe that the applicant shows the potential and drive to complete the course and get the job as a developer.
You can read our outline of what an ideal graduate of our course might look like here
Previous programming experience is not required to join the course however it is a good determinant of a person showing passion for coding.
A strong candidate for our course should
show that they are passionate about programming
show potential or current experience of being a self-learner
show a good to very good grasp of the English language
show they are open to feedback
show they understand the scale of the challenge
show that they are ready to undertake such a large challenge
show that they are focussing on our course
be somebody who would fit into our community
Most of the students you are interviewing are part of the
Intro To Coding Slack Channel - most students can ask questions there.
You can find the most common questions answered here. You can send the student a link to this page as well.
You can let them know that this will be covered in the course and that now might not be the best time to ask.
For any other questions they can direct them to their city email address
You're also welcome to share this documentation website with them.