Skip to content

Latest commit

 

History

History
28 lines (14 loc) · 4.29 KB

Onboarding.md

File metadata and controls

28 lines (14 loc) · 4.29 KB
Raw

Onboarding

Onboarding Philosophies and Planning

  • The Art and Science of OnBoarding - by Ted Tencza of finder.com.au. Takeaway: Ten questions to ask about your new developer hire onboarding program that will help focus and deliver better results.

  • Fostering Team Culture Through Better Onboarding: Lessons from My Failed Projects - by Spydergrrl. Takeaway: “[T]he teams I've been on with the strongest culture were those where a concerted effort was made not only to bring new members up to speed with the work, but with the ideas that underlie the work. Without saying so much, we infused them with the mission and vision of the project by spending the time to help them understand why we were doing what we were doing. Making sure that we weren't just explaining what they would be doing, but why and for whom.”

  • How Warby Parker Makes Every Point In Its Employee Lifecycle Extraordinary - by FirstRound. Takeaway: Lots of advice on setting up new employees to grow throughout their stay with your company, from emphasis on beign original in your onboarding practice to making new employees approachable.

  • How We Onboard New Employees Differently at Bizzabo - by Bizzabo. Takeaway: No deployments to production on your first day, but instead identify tools to make an impact. Most onboarding tasks are done solo, but "distracting" team members is okay. Also: All software/devstack setup is manual, so that people will know how to fix it when it breaks; and new hires are encouraged to give constructive feedback about the product.

  • How Your Company Can Support Junior Engineers - by Randall Kanna. Takeaway: An Eventbrite post on how strategy, clear expectations and training help.

  • The New Grad Rotation Program: Optimizing Team Fit And Enhancing Collaboration - by Judah Schvimver. Takeaway: why MongoDB starts new hires on a "rotation" through multiple teams, and how this enables them and the org to find the best fit and increase empathy.

  • Onboarding Plan - by Kate Heddleston. A four-week plan with exercises and more info.

  • Technical Onboarding, Training, and Mentoring (video) - a full onboarding curriculum by Kate Heddleston, from RailsConf 2014. Takeaway: Onboarding is taking someone from outside the team and making them productive (technical knowledge); independent/autonomous (company/process knowledge); reliably independent; and confident/believe they are valuable (personal development).

  • Thinking of the Next Developer - by David Nimmo. Takeaway: before moving on to the next coding problem, take the time to save hassle for the next person joining your team or working with your code.

  • Toast’s Engineering Team Doubled. Here’s How They Scaled Onboarding. - by Toast. Takeaway: "Ultimately, Toast’s engineering onboarding playbook is comprised of a mixture of background information transmitted through automated systems, coupled with direct in-person trainings. Team leads and onboarding buddies help fill in the gaps to get each and every person acclimated to life at Toast and ready to do their best work. The entire process is systematized and documented, so that everyone knows what to expect, and labor is divided between automated systems and people on the team, so that no one person is overburdened and nothing slips through the cracks."

Onboarding Decks

  • Welcome to Netflix - by Roy Rappaport of Netflix. After reading it you feel as if you know him personally and understand what it’ll be like to work with him.