At Ada Developers Academy, students are assigned internships through an abbreviated interview process. This provides valuable experience with the interview process for the Adie as well as allows for the host teams to familiarize themselves with their prospective interns.
This process is known as "Interview Week." Please review the content below to familiarize yourself with the structure of Interview Week and what to expect.
Hiring managers will interview several Ada students per intern spots on their team. The specific number of students is determined by the modality and location of your internship opportunity, to ensure that teams only interviewing students who could actually be assigned.
Hiring managers will need to block one 4 hour time block per intern spot that they are filling.
We have morning blocks (9:00am to 1:00pm Pacific Time) or afternoon blocks (1:00pm to 5:00pm Pacific Time). This provides time to conduct up to six interviews and to write up notes. Due to the time sensitive logistics of scheduling dozens of interviews, we do not have the ability to conduct interviews outside of this week.
These interviews will take place through videoconferencing (e.g. Zoom) and will use a real time collaboration tool called Repl.it.
These interviews will feel different from your company’s normal hiring practices! You’ll be scoring each candidate independently from each other on the basis of your ability to support their learning – you’ll interview all candidates on your slate, and potentially any of them could be a great fit.
We recommend the following format for interviews:
Get to know you and share pronouns (5 minutes)
Technical/white-boarding problem (20 minutes)
Time for questions from the students (5 minutes)
You can also choose to only ask behavioral or conceptual questions rather than a technical/white-boarding problem.
We want to make sure that both students and company partners are set up for success during these interviews. This involves company partners having a solid understanding of what content our students have covered in class and what are appropriate questions to ask.
All interviews will be conducted in Python. We understand that your team may not use Python. Students have primarily been doing their learning in Python up until this point and will have only just started the unit on front-end development in the classroom. They will not be ready to answer interview questions in front-end development-related languages like JavaScript. If you would like your interview question vetted by one of our instructors, please contact us.
We focus on practical coding skills, and though we introduce our students to Computer Science Fundamentals, it is not our focus and your interview questions should reflect that.
Example questions to ask:
Write a function to determine if a string is a palindrome
Write a function that counts the number of unique words in a string
Write a function that validates a phone number given some validation rules
Given coordinates of two rectangles determine if they overlap
Given two lists return the intersection of the lists
Write a function that takes an array of unique sorted integers (eg. [1,2,3,5,7,9,10,11]) and outputs a string of the ranges (eg. "1-3,5,7,9-11")
Express the relationship of a set of objects with an ERD or similar diagram
Describe software that could improve the efficiencies in one of your previous jobs
Example questions not to ask:
Given a binary tree, mirror the tree. (Students learn a high level of ADTs, but do not work on specific implementations for every variation.)
What is the difference between an inner join and an outer join? (Students learn data modeling at an introductory level.)
Is programming a "hobby"? (Our students all quit their jobs and found means to dedicate a year of their life to this program. Programming is not a hobby to them.)
After your interviews are done, you’ll be asked to submit a feedback form for each student which will be shared with you via email the day of your interviews. The key part of this will be providing a numerical score according to the following scale.
How successful you think this student would be on your team?
5 – This student would be a great addition to our team
4 – This student could be successful on our team
3 – This student may or may not be a good addition on our team
2 – This student may struggle on our team
1 – This student is not likely to be successful on our team
Considerations
You will not be stack-ranking students. These are not rankings, but instead a score for each individual interview.
Assuming your interview questions are within the scope of Ada’s curriculum, it's highly unlikely all students you interviewed didn’t receive a passing interview score. If we see that none or only 1-2 students received a passing score from your interviews, we will review your interview feedback and follow-up with you to review your interviews. If you are unsure if your interview question is within the scope of Ada’s curriculum, please contact us and we can forward it to one of our instructors to provide feedback.
A space for confidential feedback to help Ada make the best placement possible
Example of useful feedback: “I liked how this person asked questions! This will be useful on my busy and ambiguous team.”
Example of not useful feedback: “Coding and design need improvement.”
Feedback shared with students:
Technical feedback
Example of useful feedback: “You were able to define the problem effectively and identify edge cases, but need more work on recursion and testing your proposed solution.”
Example of not useful feedback: “This student has poor programming skills.”
Non-technical feedback
Example of useful feedback: “You asked good questions about company culture that showed us you knew about our company. Next time, try asking more questions when you get stuck.”
Example of not useful feedback: “You should be less nervous.”
We highly recommend submitting the feedback the same day as your interviews (even in between interviews, if you can). It is hard to remember key details on interviews with different people a few days after your interviews have happened.
I’m unsure if the technical/white-boarding problem I’m planning to ask is appropriate and within the scope of Ada’s curriculum.
If you would like your interview question vetted by one of our instructors, please contact us and we can forward it to one of our instructors to provide feedback.
The student I was scheduled to interview no-showed and I can’t get in contact with them via email or the repl.it chat.
Please contact us to reach out to the student directly and we will follow up with you on next steps.
I’m experiencing technical difficulties with my video conferencing tool/internet/laptop/computer etc.
Communicate with the student via email or the repl.it chat the technical difficulties that you are experiencing
Have a back-up video conferencing link or tool ready to move to with the student
Be prepared to reset your devices that you’re using to interview with
Have an interview buddy (preferably the mentor) or back-up interviewer to help continue the interview without you
What if I’m running late on my interviews?
Please keep in mind when planning for your interview that these are only 30 minutes long, and we like to allow some time for students to ask questions. This most likely means that the student may only get through one technical/whiteboarding problem during the course of the interview. Be prepared to do a hard stop for the technical/whiteboarding problem.
There is a 10 minute break between interviews as a buffer if you begin to run behind between interviews
Please communicate with the rest of the students you are interviewing if you are running late via email
Why do I need to share my pronouns or use gender neutral language?
Ada Developers Academy is a non-profit, tuition-free coding school for women and gender expansive adults. We prioritize serving Black, Latine, Indigenous American, Hawaiian & Pacific Islander, LGBTQIA+, and low-income people. Here at Ada, we’ve chosen to use the term “gender expansive” to represent as large a range of gender identities as possible. We acknowledge that this vocabulary is inherently imperfect, and is continually evolving. Our community includes people who also identify as trans, non-binary, gender queer, gender fluid, and gender non-conforming.
While you’re conducting interviews, please use gender neutral terminology and use proper pronouns for your interviewees. Their perceived gender may be different from their gender expression. If you are not familiar with sharing and being asked for pronouns, please check out this resource about why pronouns are important.
We have some behavioral concerns about a student based on our interview experience with them.
If you have behavioral concerns about a student you interviewed, please contact us.
What kinds of questions can we expect students will ask?
Questions about your team (e.g. What representation is there on your team?)
Questions about intern project/tasks
Team culture and support
None of the students we interviewed passed our interview (i.e. received a numerical score of 3).
Ada students are not the same as computer science college interns, we focus on practical coding skills, and though we introduce our students to Computer Science Fundamentals, it is not our focus and your interview questions should reflect that.
Assuming your interview questions were within the scope of Ada’s curriculum, it's highly unlikely all 6 students you interviewed didn’t receive a passing interview score. If we see that none or only one or two students received a passing score from your interviews, we will review your interview feedback and follow-up with you to review your interviews. If you are unsure if your interview question is within the scope of Ada’s curriculum, please contact us and we can forward it to one of our instructors to provide feedback.
Start the interview off with introductions
Become familiar with the Ada Curriculum ahead of the interview
Let student complete their thoughts and hold your feedback until the feedback phase of the interview
Stay focused on the interviewee
Be mindful of time
Use correct pronouns
Test out the technology ahead of time, keep your camera on during the interview
Be prepared to troubleshoot common technical video conferencing issues