Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Whether you're a student or a CTO, it's worth taking a moment to consider the transition from student to professional. The Junior Jump will explore strategies that will help you become or mentor a confident junior developer. We'll discuss how candidates and employers can use the interview stage to set a foundation for a productive transition, how to figure out what kind of mentorship/pairing model will work best with the resources available at your company and examples of projects that are challenging and appropriate for developers transitioning into their first jobs. I'll draw on my own experience working on the DMCA claim system at Kickstarter, as well as interviews with experienced software leads and developers currently in their first jobs. We will hear anecdotes from developers from university, bootcamp and self-taught backgrounds and as well as engineers experienced in mentoring junior devs at very diverse companies.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled 'The Junior Jump: from Student to Team Member' by Rebecca Poulson focuses on the transition from being a student or new developer to becoming a professional engineer in a supportive work environment. Poulson emphasizes the critical role of effective onboarding processes for junior engineers, structured around three main concepts—planning, projects, and pairing. **Key Points Discussed:** - **Planning:** The onboarding process should start with careful planning. Poulson recalls her job search experiences, highlighting the importance of candidates being self-aware of how they learn best and voicing their needs. This approach encourages a dialogue between candidates and employers during interviews about successful resources for development. - **Projects:** Candidates should be assigned a first project that strikes a balance between challenge and independence. It's essential for this project to be manageable yet impactful, motivating junior engineers to own their work and contribute meaningfully to the team. Poulson shares her own experience of working on a tool for automating DMCA claims, illustrating how a manageable project can facilitate a stronger learning experience. - **Pairing/Mentorship:** Establishing a mentorship model is crucial. Juniors benefit greatly from having a mentor who helps ease their transition into a production environment. Poulson suggests forming a mentorship structure within teams, likening it to a band where each member has a distinct but supportive role. The mentor should be a guide for the new engineer, while other team members can provide additional support and an encouraging environment. Throughout the talk, Poulson includes valuable anecdotes from both junior developers and seasoned engineers, showcasing the significance of tailored mentorship and the satisfaction that arises from helping others develop professionally. The conclusion emphasizes that investing in junior engineers not only benefits them but also contributes to a thriving engineering community. Companies should actively engage in structured onboarding to support new talent and ensure that their integration into the workplace is both productive and enriching.
Suggest modifications
Cancel
