Onboarding Junior Developers

Hiring junior developers is a brilliant way to bulster your team without the high-cost of experienced developers.

Many developers dread hiring and working with junior developers, how do you know if they have the right skills? What should your expectations be?

Once you've found the right person, how do you make sure they are getting the support they need?

Maybe you're terrified of lots of hand-holding, or maybe you're excited because you get to pass on your experience.

Either way, it's in everyone's best interest that they succeed. This talk is perfect for both junior developers joining a new team and developers who work with (or will) junior developers.

Transcript

1. Onboarding junior developers @MPOram | @IOAcademyUK
2. About Me. Software dev ~15 years @MPOram @IOAcademyUK
3. About Me. Software dev ~15 years iO Academy Director @MPOram @IOAcademyUK
4. About Me. Software dev ~15 years iO Academy Director Trained over 200 junior developers @MPOram @IOAcademyUK
5. About Me. Software dev ~15 years iO Academy Director Trained over 200 junior developers Work with >80 companies across the world @MPOram @IOAcademyUK
6. @MPOram @IOAcademyUK ➔ Recruitment Everything starts here
7. @MPOram @IOAcademyUK ➔ Recruitment Everything starts here ➔ Before day one Preparing for their arrival
8. ➔ On the job Supporting staff when they join you @MPOram @IOAcademyUK ➔ Recruitment Everything starts here ➔ Before day one Preparing for their arrival
9. ➔ On the job Supporting staff when they join you ➔ Next steps What else can you do @MPOram @IOAcademyUK ➔ Recruitment Everything starts here ➔ Before day one Preparing for their arrival
10. Recruitment. @MPOram @IOAcademyUK Tip Applying for jobs is stressful. Make the process as transparent as possible.
11. Recruitment. Put everything in the job ad. @MPOram @IOAcademyUK Tip Applying for jobs is stressful. Make the process as transparent as possible.
12. Recruitment. Put everything in the job ad. @MPOram @IOAcademyUK ➔ Salary (25k) Tip Applying for jobs is stressful. Make the process as transparent as possible.
13. Recruitment. Put everything in the job ad. @MPOram @IOAcademyUK ➔ Salary (25k) ➔ What tech do you use ➔ What skills do you need Tip Applying for jobs is stressful. Make the process as transparent as possible.
14. Recruitment. Put everything in the job ad. @MPOram @IOAcademyUK ➔ Salary (25k) ➔ Recruitment process Tip Applying for jobs is stressful. Make the process as transparent as possible.
15. Recruitment. Put everything in the job ad. @MPOram @IOAcademyUK ➔ Salary (25k) ➔ Recruitment process ➔ What tech do you use Tip Applying for jobs is stressful. Make the process as transparent as possible.
16. Recruitment. Put everything in the job ad. @MPOram @IOAcademyUK ➔ Salary (25k) ➔ Recruitment process ➔ What tech do you use ➔ What skills do you need Tip Applying for jobs is stressful. Make the process as transparent as possible.
17. Recruitment. Assess required skills. @MPOram @IOAcademyUK Tip Applying for jobs is stressful. Make the process as transparent as possible.
18. Recruitment. Assess required skills. @MPOram @IOAcademyUK ➔ Real problem-solving Tip Applying for jobs is stressful. Make the process as transparent as possible.
19. Recruitment. Assess required skills. @MPOram @IOAcademyUK ➔ Real problem-solving Tip Applying for jobs is stressful. Make the process as transparent as possible.
20. Recruitment. Assess required skills. @MPOram @IOAcademyUK ➔ Real problem-solving ➔ Do they really need a degree? Tip Applying for jobs is stressful. Make the process as transparent as possible.
21. Recruitment. Assess required skills. @MPOram @IOAcademyUK ➔ Real problem-solving ➔ Do they really need a degree? ➔ Interpersonal skills Tip Applying for jobs is stressful. Make the process as transparent as possible.
22. Recruitment. Assess required skills. @MPOram @IOAcademyUK ➔ Real problem-solving ➔ Do they really need a degree? ➔ Interpersonal skills ➔ Values Tip Applying for jobs is stressful. Make the process as transparent as possible.
23. Before day one. Tip Remember, this role is a big deal for your new recruit. It could be their first ever job, or at least their first developer role. @MPOram @IOAcademyUK
24. Before day one. Don’t ghost them. @MPOram @IOAcademyUK Tip Remember, this role is a big deal for your new recruit. It could be their first ever job, or at least their first developer role.
25. Before day one. Don’t ghost them. @MPOram @IOAcademyUK ➔ Confirm the first day as early as possible Tip Remember, this role is a big deal for your new recruit. It could be their first ever job, or at least their first developer role.
26. Before day one. Don’t ghost them. @MPOram @IOAcademyUK ➔ Confirm the first day as early as possible ➔ Have kit prepared Tip Remember, this role is a big deal for your new recruit. It could be their first ever job, or at least their first developer role.
27. Before day one. Don’t ghost them. @MPOram @IOAcademyUK ➔ Confirm the first day as early as possible ➔ Have kit prepared ➔ Know which team they are joining Tip Remember, this role is a big deal for your new recruit. It could be their first ever job, or at least their first developer role.
28. Before day one. Don’t ghost them. @MPOram @IOAcademyUK ➔ Confirm the first day as early as possible ➔ Have kit prepared ➔ Know which team they are joining ➔ Account set-up Tip Remember, this role is a big deal for your new recruit. It could be their first ever job, or at least their first developer role.
29. On the job. @MPOram @IOAcademyUK Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
30. On the job. Have a plan. @MPOram @IOAcademyUK Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
31. On the job. Have a plan. @MPOram @IOAcademyUK ➔ Day 1, week 1, month 1 Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
32. On the job. Have a plan. @MPOram @IOAcademyUK ➔ Day 1, week 1, month 1 ➔ Who can they ask for technical help Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
33. On the job. Have a plan. @MPOram @IOAcademyUK ➔ Day 1, week 1, month 1 ➔ Who can they ask for technical help ➔ Assign a buddy Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
34. On the job. Have a plan. @MPOram @IOAcademyUK ➔ Day 1, week 1, month 1 ➔ Who can they ask for technical help ➔ Assign a buddy ➔ First task(s) Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
35. On the job. Set expectations. @MPOram @IOAcademyUK Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
36. On the job. Set expectations. @MPOram @IOAcademyUK ➔ When should they be adding to productivity Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
37. On the job. Set expectations. @MPOram @IOAcademyUK ➔ When should they be adding to productivity ➔ How much time to complete tasks Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
38. On the job. Set expectations. @MPOram @IOAcademyUK ➔ When should they be adding to productivity ➔ How much time to complete tasks ➔ Invite them to meetings Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
39. On the job. Set expectations. @MPOram @IOAcademyUK ➔ When should they be adding to productivity ➔ How much time to complete tasks ➔ Invite them to meetings ➔ Company / team traditions Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
40. On the job. Provide training resources. @MPOram @IOAcademyUK Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
41. On the job. Provide training resources. @MPOram @IOAcademyUK ➔ Ask what they need Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
42. On the job. Provide training resources. @MPOram @IOAcademyUK ➔ Ask what they need ➔ Dedicated learning time Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
43. On the job. Provide training resources. @MPOram @IOAcademyUK ➔ Ask what they need ➔ Dedicated learning time ➔ Set expectations Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
44. On the job. Provide training resources. @MPOram @IOAcademyUK ➔ Ask what they need ➔ Dedicated learning time ➔ Set expectations ➔ Encourage exploration Tip Day one is always information overload. Document as much as you can and tell people where they can find the information later.
45. Next steps. @MPOram @IOAcademyUK Tip Remember: Years of experience does not equal skill level
46. Next steps. Expect turnover. @MPOram @IOAcademyUK Tip Remember: Years of experience does not equal skill level
47. Next steps. Expect turnover. @MPOram @IOAcademyUK ➔ Not all development is for everyone Tip Remember: Years of experience does not equal skill level
48. Next steps. Expect turnover. @MPOram @IOAcademyUK ➔ Not all development is for everyone ➔ Open communication Tip Remember: Years of experience does not equal skill level
49. Next steps. Expect turnover. @MPOram @IOAcademyUK ➔ Not all development is for everyone ➔ Open communication ➔ First 12 months Tip Remember: Years of experience does not equal skill level
50. Next steps. Expect turnover. @MPOram @IOAcademyUK ➔ Not all development is for everyone ➔ Open communication ➔ First 12 months ➔ Ask what they want Tip Remember: Years of experience does not equal skill level
51. Next steps. Make progression clear. @MPOram @IOAcademyUK Tip Remember: Years of experience does not equal skill level
52. Next steps. Make progression clear. @MPOram @IOAcademyUK ➔ How can they add more value Tip Remember: Years of experience does not equal skill level
53. Next steps. Make progression clear. @MPOram @IOAcademyUK ➔ How can they add more value ➔ Job title Tip Remember: Years of experience does not equal skill level
54. Next steps. Make progression clear. @MPOram @IOAcademyUK ➔ How can they add more value ➔ Job title ➔ Salary Tip Remember: Years of experience does not equal skill level
55. Next steps. Make progression clear. @MPOram @IOAcademyUK ➔ How can they add more value ➔ Job title ➔ Salary ➔ Teams or technical Tip Remember: Years of experience does not equal skill level
56. To summarise Open and frequent communication. Transparency throughout, from job ad to day one and beyond. Set your expectations. @MPOram @IOAcademyUK
57. Questions? @MPOram @IOAcademyUK Tip Come find me at the conference, I love talking about this stuff and I am mostly friendly!