This document provides a guide for senior developers on onboarding junior developers over an 8 week period. It involves preparing for their arrival, adjusting team processes, implementing a buddy system, conducting regular check-ins, and gradually increasing independence through pair programming, small group sessions, and team bonding activities while continuing to provide support. The goal is for juniors to feel comfortable, learn collaboratively, and be ready to work independently by the end of the 8 weeks.

3. HOWTO ONBOARD
JUNIOR DEVS
LIKE A BOSS
A Guide for Senior Developers
Izzi Bikun
@izzib76

4. PREPARING FOR
A JUNIOR
DEVELOPER
Before they arrive

5. PUTYOUR
EGO ASIDE
Onboarding
someone is NOT the
time to show off your
mad developer skillz

6. AdjustTeam
Processes
Determine a Pair Programming strategy
Schedule weekly Code Retro
Set up Code Reviews/Merge
Requests/Branching Strategy
Write down any implied processes

7. Code Reviews
Are
■ Does this code match agreed team
styles?
■ Have unit tests been written?
■ Is the acceptance criteria met?
■ Does the code match the team’s
agreed definition of “code
complete”?
Are NOT
■ “I would have done this differently”
■ “This isn’t how *I* write code”
■ “They did <this>?!?! I can’t believe it,
what a moron.”

8. Buddy System!!!!!!!!!!!!
Assign ONE PERSON to be their
mentor
First point of contact until they
are comfortable

9. Schedule 1:1 Meet and Greets
GO FOR AWALK TAKEA
COFFEE/SNACK BREAK
GETTO KNOW EACH
OTHER

10. JUNIOR
DEVELOPER
ARRIVES
Bright eyed, ready to learn, full of hope,
scared out of their minds.

11. Day 1: Pair
Programming
Narrate EVERYTHING
“I don’t know what
you don’t know”

12. Day 2: Senior
Dev Hands
off the
Keyboard!
Junior Devs should ALWAYS be
driving
TEACH them instead of DOING
for them

13. Week 1:
Small Groups
for Large
Topics
Create a “class” of junior developers
Set up a weekly meeting for the class
Deep dive into topics difficult to
explain
Let the class bond with each other

14. End ofWeek 1:
“How’s it going?”
■ What did you learn
this week?
■ What did you
struggle with this
week?
■ How can I help?

15. Week 2: More
of the same
■ Create structure
■ Let them know what to
expect

16. End ofWeek 2:
“How’s it going?”
■ Do you feel more
settled in?
■ What’s confusing
for you?
■ How can I help?

17. WEEK 3:TEAM
BONDING!

18. End ofWeek 3:
“How’s it going?”
■ What’s working
well?
■ What isn’t
working?
■ What can be
improved?
■ How can I help?

19. Week 4: Step Away from the Computer!
Teach Teach them to come to you when they’re stuck
Check in Check in periodically, make sure things are on track
Leave Leave Juniors alone at the computer

20. End ofWeek 4:
“How’s it going?”
■ “I’ve seen
improvement in
<topic>. Keep up
the good work!”
■ “What are you
struggling with?”
■ “How can I help?”

21. Week 5: Participation in Meetings
It’s super
rude.
Don’t
interrupt
people.
Seriously.
Don’t
interrupt
them
One voice
at a time

22. End ofWeek 5:
“How’s it going?”
■ “What’s your
favorite thing
you’ve worked on
so far?”
■ “What is your least
favorite thing to
work on/with?”
■ “How can I help?”

23. Week 6: Pair
JuniorsTogether
■ Fly free with a safety net
■ Teach them to pair
collaboratively
■ Have someone check in on
them

24. End ofWeek 6:
“How’s it going?”
■ “Who all have you
met?”
■ “What have you
been learning in
the small group
sessions?”
■ “How can I help?”

25. WEEK 7:
MORETEAM
BONDING!
Go nuts for donuts!

26. End ofWeek 7:
“How’s it going?”
■ “Do you feel ready
to be by yourself?”
■ “How can I help?”

27. WEEK 8: FLY
FREEYOUNG
PADAWAN
But still check in on occasion

28. THANKYOU! Izzi Bikun
@izzib76