Diversity & Inclusion
Technical Onboarding, Training, and Mentoring

Summarized using AI

Technical Onboarding, Training, and Mentoring

Kate Heddleston • September 19, 2014 • Earth

In her talk titled 'Technical Onboarding, Training, and Mentoring', Kate Heddleston discusses the crucial aspects of onboarding junior engineers. With the rise of code academies, many companies face challenges incorporating junior engineers into their teams due to inadequate resources for training. Heddleston emphasizes that effective onboarding is vital for turning these junior engineers into autonomous and productive members of engineering teams.

Key Points:

- Importance of Autonomy: Autonomy is essential for motivation and stability, as illustrated by anecdotes from prison systems and nursing homes, where individuals with choice make better decisions and thrive longer.

- Significance of Confidence: Confidence affects performance, exemplified by the 'stereotype threat', which shows that beliefs about capability can influence individuals' success.

- Onboarding as a Priority: Onboarding should be prioritized to reap immediate benefits, and its absence can lead to significant costs, as losing engineers incurs costs up to 2 times their salary.

- Team Dynamics: New hires introduce fresh perspectives and change team dynamics, necessitating clear communication of team values and procedures.

- Investment in Onboarding: Treat onboarding similarly to automation processes; the initial investment leads to substantial returns in productivity and team integration over time.

- Diversity Considerations: Effective onboarding should include diverse perspectives and abilities, as this diversity enriches team dynamics.

- Shared Responsibility: Onboarding is a collective responsibility involving all team members, including new hires assisting in the process.

- Structured Onboarding Plan: Establish a structured plan involving phases for technical training, cultural integration, and personal development to support long-term independence.

- Progress Assessment: Regular assessment during and post-onboarding through feedback cultivates a growth mindset among engineers.

Conclusions: Heddleston emphasizes that a robust onboarding process enhances productivity and confidence for new engineers, fostering long-term benefits for individuals, teams, and companies. The process promotes a sense of belonging while supporting diversity and individuality in the workforce. Overall, onboarding is an ongoing journey starting from the acceptance of the job offer, and a well-structured approach can make the transition seamless for new hires.

Technical Onboarding, Training, and Mentoring
Kate Heddleston • September 19, 2014 • Earth

By, Kate Heddleston
With the increase of code academies training new engineers there is an increase in junior engineers on the market. A lot of companies are hesitant to hire too many young engineers because they lack sufficient resources to train them. This is a talk about how to make junior engineers into independent and productive members of your engineering team faster and cheaper by outlining a plan for how to onboard engineers effectively based on data and anecdotes gathered from companies in San Francisco.

Help us caption & translate this video!

http://amara.org/v/FUGT/

GoGaRuCo 2014

00:00:13.440 Hello, my name is Kate Heddleston. This talk is called 'Technical Onboarding, Training, and Mentoring', and it was originally written and co-presented at PyCon with Nicole Zuckerman, who is not here today. She is a software engineer at Eventbrite. I usually work at very small early-stage startups, and have never joined one larger than 12 people. I join companies that typically don’t have structured onboarding processes.
00:00:27.519 This talk focuses primarily on junior engineers. Although many of the concepts can be adapted for mid-level or senior engineers, we specifically address junior engineers due to the numerous code academies training new engineers. Companies are having difficulties integrating these junior engineers into their organizations. Onboarding is the process of transitioning someone from outside the company to becoming a confident, independent, and productive member of your team.
00:01:10.080 I believe autonomy, independence, and confidence are crucial for new engineers. Autonomy is a major motivator. I have two somewhat depressing anecdotes that highlight its significance. The first example comes from prison systems. Researchers discovered that allowing inmates to make small decisions, like choosing a TV channel or rearranging their furniture, significantly reduced prison riots. This demonstrates how autonomy contributes to stability and peace.
00:02:08.720 The second anecdote is about nursing homes, where individuals often lose autonomy in the name of providing good care. Studies have shown that residents with choices—such as what to eat or performing small chores—live significantly longer than those with no choices. Autonomy not only enhances motivation but is also vital for well-being and happiness.
00:03:01.840 Next, let's discuss confidence. Confidence is fundamentally the belief that you are valuable. There's a well-documented phenomenon called 'stereotype threat,' where individuals tend to perform according to the stereotypes associated with their group. For example, studies have shown that if male students are reminded that boys are better at math before taking a test, they perform better. Conversely, if reminded that females are better at math, females outperform males.
00:04:45.680 This highlights how belief in capability influences performance, regardless of the accuracy of the stereotype. Therefore, I want to emphasize that onboarding should not be postponed—it should be prioritized now. The benefits of effective onboarding can be immediate and substantial.
00:05:11.760 There are four major categories to consider when discussing the importance of onboarding: the individual, the company, the immediate team, and diversity. For individuals, acquiring skills and confidence is essential for their professional growth. Additionally, companies incur significant costs when losing an engineer, which can be up to 1.5 to 2 times their annual salary.
00:06:18.880 If engineers are not productive due to lack of onboarding, it results in lost revenue. Companies must ensure that adding new team members does not hinder overall productivity. Effective onboarding positively influences the bottom line, allowing new hires to contribute effectively from the start.
00:07:01.200 The dynamics within a team are vital as well. When new members join, they introduce fresh perspectives. Each addition changes the makeup of the team, making it essential to share team values and procedures. This ongoing communication is necessary as the team scales. Good onboarding contributes to a shared understanding, ensuring that every member is aligned in their goals and direction.
00:08:15.920 Treat onboarding similarly to automation processes—it requires initial investment but pays off exponentially over time. The sooner it is implemented, the more seamless future integration becomes. It’s better to build up training incrementally rather than attempting a major overhaul later. My favorite metaphor for this principle involves the idea that teamwork can achieve success in ways that individual talent alone cannot.
00:09:44.000 As a bonus category, we must also consider diversity. Using Dr. Seuss's story about the Sneetches as an allegory, diversity encompasses various dimensions beyond just race and gender. Introverts and extroverts, or people with varying interests, also contribute to team dynamics. Solid onboarding processes are essential to integrating diverse talents and perspectives, allowing all members to feel included and valued.
00:11:50.880 Everyone should engage in the onboarding process. It’s a shared responsibility; even those who just joined the team can contribute meaningfully in guiding new hires. The mentor-mentee relationship should be supportive, emphasizing that even less experienced members can provide valuable insights.
00:12:28.720 Onboarding is a continuous process beginning from the moment an offer is accepted and carries on until the new hire can operate independently. This varies by role; junior engineers might take six months to become fully acclimated, while seniors may adjust quickly. The core of onboarding is to support new hires in becoming reliably independent.
00:13:42.240 Establish a structured onboarding plan, which should include various phases focusing on technical knowledge, cultural integration, and personal development. Each phase can be customized to meet the unique needs of the team and the individual, ensuring that all aspects of the onboarding experience are addressed.
00:15:21.120 The onboarding plan should cover setting up the development environment, shipping code, and establishing a social connection with coworkers. Ensuring that new hires can ship code quickly instills confidence and demonstrates the feasibility of their new role. Social interactions help to create a comfortable environment, easing integration into the team.
00:16:22.160 After shipping initial code and getting acquainted with coworkers, it is crucial for new employees to start engaging with the team more deeply. Understanding the company’s history, their team structure, and participating in collaborative projects further fosters a sense of belonging.
00:17:01.920 Finally, as new hires grow more comfortable, it’s important to encourage their personal development and self-direction regarding their career paths. Providing resources for goal setting and feedback sessions helps new engineers chart their course within the company and develop professionally.
00:18:49.120 Assessing the progress during and after onboarding is equally crucial. Creating a culture of open feedback—both positive and constructive—will help engineers understand their strengths and areas of improvement, ultimately fostering a growth mindset.
00:19:41.760 In summary, effective onboarding focuses on making individuals productive, independent, and confident, creating long-term benefits for every stakeholder—employees, companies, and teams. Diversity and contributions from all team members enrich the onboarding experience.
00:20:30.079 Finally, I work for a company called RunScope, which produces development tools that assist users in monitoring APIs. If you're interested in our cool t-shirts, feel free to reach out. Thank you for your attention, and if time permits, I’d love to address any questions you may have.
Explore all talks recorded at GoGaRuCo 2014
+14