Ada’s vision is a tech industry where Black and brown women & gender-expansive people are proportionally represented in software development careers and leadership roles, creating an equitable distribution of power and capital in an industry-shaping our future.
An important component of intern success is that the manager and the team care deeply about developing junior talent from non-traditional and underrepresented backgrounds.
Ada's interns have not been studying computer science full-time for multiple years. There will be gaps in some areas of their knowledge compared to an intern from a Computer Science major. They are eager to learn and, instead, bring their diversity of professional, educational, and personal experiences to your organization.
In order to set our students up for success, we have created these guidelines for choosing managers and other supporters of the Ada intern. Successful teams would ideally have all of the resources described below or equivalent supports.
An ideal internship is one that offers students a progressively challenging work experience supported by an organization and team that provides consistent training, supervision, and feedback.
Support from manager, mentor, and team
Weekly 1:1s between manager and intern
Frequently opportunities to connect with a designated mentor
Clear expectations for how and when to ask for support
Effective communication
Frequent, actionable feedback, grounded in the learning experience
Participate in Ada provided trainings and reviews
Explain organizational norms, team culture, and the tech sector
Clear expectations
Progressive goals and milestones
Defined metrics of success, such as:
The intern is hireable as a junior developer
The intern has an area of code that they feel ownership over
The intern can write tests for the things they have implemented
The intern can critically review existing code for potential improvements
The intern can use internal tools and resources
The intern can comment on others' code
The intern is an welcomed, productive member of their team
The manager would ideally manage one team of individual contributors, not multiple teams and would ideally not be a manager of managers
The manager would ideally be able to commit to at least one hour a week of meetings with the intern
Managers that have not previously had an Ada intern are strongly encouraged to participate in the Manager & Mentor Orientation by Ada that discusses inclusive management practices.
Managers are strongly encouraged to get familiar with the Ada program and understand the difference between taking on an Ada intern and a traditional college CS intern so that they may appropriately provide the additional support an Ada intern will need.
The manager would ideally appropriately scope work for an intern aligned with our Ada Intern Project Guidelines. For example, using the SDE1 guidelines to create a project that is broken down into small, understandable pieces and allows ramp up time for the intern.
We value managers who have successfully mentored an Ada intern before.
We value managers who are involved in Ada in other ways, including as a volunteer.
The team would ideally be sized between 5-12 people.
The team would ideally be an established team, not a brand new team (e.g. has worked together for at least a year).
The most successful teams typically have at least one SDE on the team who will be designated as the intern’s mentor. This person would ideally be able to dedicate the time, bandwidth, interest, and technical background to mentor the intern consistently and check in with their intern at least once daily about their work.
We value teams that have had an Ada intern before or if there are Ada alums on the team.
We value teams that represent diversity of race and gender.
A mentor is another member of the team who has been selected to oversee intern learning development and progress. The mentor selected must have adequate experience to oversee and assist an intern in their transition to employment.
Mentor bandwidth is critical. Without mentorship, ramp-up can take much longer. During the internship, students are transitioning from theory to practice in their work environment. To create a stable, focused transition, the new interns will need a strong mentor who can guide them through the best practices your team has developed.
Mentor Location
A mentor that is located in the same timezone as your intern is ideal, two hours difference max.
Mentor Bandwidth Capacity
The amount of time a mentor spends with their intern varies, however more bandwidth capacity is needed at the beginning of the internship and then gradually declines. Expect in the first month, that 25-40% of the mentor's bandwidth will be needed for interns.
What will mentors be doing?
Although these items would vary between teams and interns, here are some examples of things mentors will be doing:
Weekly 1:1’s
Daily check-ins
Provide ongoing feedback
Code Reviews
Pair Programming and screen sharing
Adapt to intern’s learning style
Teach processes
Introducing them to new software and tools
Provides guidance and constructive feedback. This is one of the key responsibilities of a good mentor. The mentee grows by identifying their strengths and weaknesses and learning how to use these to make themselves successful. A good mentor is able to adjust their communication style to the personality style of the mentee. A good mentor provides challenges that foster professional development and a feeling of accomplishment in learning.
Is willing to share skills, knowledge, and expertise. A good mentor is patient, available, and understands that good mentoring requires time and commitment to ensure that the mentee is successfully ramped up.
Is prepared and understands the mentee's areas of expertise so that both the mentor's and mentee's time is well spent.
Explains why. Don't focus so much on the “you should do X” but on the “why is X better.” Whether it's code reviews, your particular favorite bash shortcut, or some design pattern you're teaching your mentee, don't just tell them how but tell them why
Listens and asks the right questions. A good mentor is knowledgeable and possesses the attributes of a trainer.
Encourages mentees to ask questions. The mentee should feel comfortable approaching the mentor with any questions.
Introduces mentees to other people. Help ensure your mentee's first few weeks at the organization, learning about extracurriculars: take them to lunch; tell them about resource groups, affinity groups
Asks mentees for feedback about their onboarding experience.
Onboarding Buddies
Interns are most successful when they have more than one person that they can get support from. An onboarding buddy is another team member or employee, besides the manager and mentor, who is assigned to your Ada intern during the first half of internship and can help the Ada intern navigate the onboarding experience, answer day-to-day questions, and offer advice and encouragement.
Connects with the intern in onboarding (ie. Month 1-3), and can pause buddy duties when the intern is “ramped up” or no longer needs the buddy system
Can answer questions about the team culture, workplace expectations, corporate communications, company resources, or other common “new employee” questions
Hosts 1+ introduction meeting to build rapport, then transitioning to being available within reason but mainly meeting or messaging when the intern reaches out
Does not need to have any direct involvement in the intern’s assigned project/work
Lower time commitment (mentors work with the intern for the entire internship, and connect with the intern daily, via 1:1s or messaging, for 4-6+ hours weekly)
Less technical knowledge and coaching needed (mentors need both the expertise and desire to coach the intern in their technical learning)
Assigning an Onboarding Buddy
We recommend that as you consider who to assign as an onboarding buddy, to please look for the following qualities:
Empathy for the new intern experience, which can be confusing and overwhelming
Desire to help the Adie intern feel increased safety and confidence
Has been on the team for long enough to comfortably answer general “new employee” questions and guide the intern to common resources
Tips & Best Practices
Scope the onboarding buddy’s purpose with intention. If you have never assigned an onboarding buddy for an intern or Adie before, consider asking yourself:
Can you clearly explain the differences between how your intern should engage with their onboarding buddy vs. with their mentor?
Is the intern’s assigned mentor already doing or planning to do any of the things an onboarding buddy would do? If yes/no, what could be the benefit of adding a buddy?
For example, it could help increase the productivity of mentor/intern meetings and allow them to focus on more technical training.
What is the context of your team? How can an onboarding buddy help your intern become more familiar or confident with the larger team, workplace, and company?
For example, if the team or company is very large, the buddy could encourage the intern to reach out for coffee chats or give advice on how to best work with other roles.
Remember that it can be hard to ask questions. When the onboarding buddy’s responses are constructive, actionable, and non-judgmental, that increases the likelihood of your intern asking questions, and helps them better discern who and how to ask for each question/issue – thus, getting better faster at asking strategic, relevant questions.
Adie interns come from a wide spectrum of backgrounds and work experiences. Some Ada interns have never worked in a corporate or tech workplace before, while others have many years of experience in office-based roles. This means your intern might ask the buddy some questions that are surprising, or not ask some questions the buddy is expecting them to. For example, someone might never have had manager 1:1 meetings before, while another person has supervised teams and hosted 1:1s for years.
Consider how being an onboarding buddy can be a growth opportunity for the employee assigned. For example, is it a chance for them to showcase communication or leadership skills, or improve onboarding documentation for future interns?
External Resources