Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to Start On-Boarding of SRE

How to Start On-Boarding of SRE

93c80c388fe9d8f9df7d030549a0ff0b?s=128

Takeshi Kondo

June 14, 2019
Tweet

Transcript

  1. How to Start On-Boarding of SRE Takeshi Kondo SRE at

    Quipper @chapsy / @chaspy_en #srecon19onboarding SRECon19 Asia/Pacific  
  2. 2018/06/20 Joined Quipper as SRE 2019/06/14 Speaking at SRECon 2

  3. 2018/06/20 Joined Quipper as SRE 2018/12/xx I started working independently

    2019/06/14 Speaking at SRECon Half year 3
  4. 2018/06/20 Joined Quipper as SRE 2018/12/xx I started working independently

    2019/06/14 Speaking at SRECon Half year Why? 4
  5. Team side My side

  6. Team side My side

  7. No On-Boarding Mechanism

  8. Team side My side

  9. My side Technical Challenge Mental Problem

  10. My side Technical Challenge Mental Problem

  11. Technical Challenge Previous Job Quipper Product Provide IaaS as a

    cloud provider Providing educational services as SaaS Role Software Engineer SRE Operation No (Not DevOps) Yes Environment On-premiss Cloud
  12. Technical Challenge Former Job Quipper Product Provide IaaS as a

    cloud provider Providing educational services as SaaS Role Software Engineer SRE Operation No (Not DevOps) Yes Environment On-premiss Cloud Big challenge to me
  13. My side Technical Challenge Mental Problem

  14. Negative Loop Technical Gap Takes time to work Feel anxiety

    Feel anxiety Takes time to work Feel anxiety Takes time to work Feel anxiety
  15. Why did I do on-boarding?

  16. 2018/06/20 Joined Quipper as SRE 2018/12/xx I started working independently

    2018/12/xx Next SRE joined 2019/06/14 Speaking at SRECon
  17. Should I do On-boarding?

  18. “On-boarding works effectively even for senior engineers”

  19. 2018/06/20 Joined Quipper as SRE 2018/12/xx I started working independently

    2018/12/xx Next SRE joined 2019/02/xx He finished my On-boarding 2019/06/14 Speaking at SRECon
  20. 2018/06/20 Joined Quipper as SRE 2018/12/xx I started working independently

    2018/12/xx Next SRE joined 2019/02/xx He finished my On-boarding 2 month
  21. 2018/06/20 Joined Quipper as SRE 2018/12/xx I started working independently

    2018/12/xx Next SRE joined 2019/02/xx He finished my On-boarding 2 month Definition of finishing On-boarding =>To Be able to work independently
  22. Achievement Me: ——————> 6 months No On-boarding process NextSRE: ——>

    2 months With my On-boarding
  23. Agenda • Back Ground • What is On-boarding? • How

    to start On-boading? • To apply beyond SRE • Takeaways
  24. Agenda • Background • What is On-boarding? • How to

    start On-boading? • To apply beyond SRE • Takeaways
  25. On-boarding is NOT an account creation nor just assigning tasks

  26. On-boarding is Mechanism

  27. For early strength of the new joiners

  28. “On-boarding works effectively even for senior engineers”

  29. What did I need?

  30. My side Technical Challenge Mental Problem

  31. Technical gap and Anxiety -> Less Outcome

  32. KeyPoint • Reduce anxiety • Narrow the scope of thinking

  33. Agenda • Background • What is On-boarding? • How to

    start On-boading? • To apply beyond SRE • Takeaways
  34. Agenda • Background • What is On-boarding? • How to

    start On-boading? • Define the goal • Design the learning experience • Review through 1on1 • To apply beyond SRE • Takeaways
  35. How to start On-Boading? • Define the goal • Design

    the learning experience • Review through 1on1
  36. To define the goal, let’s ask 3 simple questions

  37. Questions to define the goal • What is your team’s

    • mission? • responsibility? • daily work?
  38. Mission / Responsibility / Daily Work Mission Daily Work Responsibility

    Proactive action based on team values Goal for On-boarding
  39. In the case of Quipper SRE Mission Daily Work Responsibility

    Make it reliable and stable our services Proactive approach for stability Fixes server instability / failure Response to @sre Change an infrastructure with code React an alert Review Pull-Request Take long-term task
  40. In the case of Quipper SRE Mission Daily Work Responsibility

    Make it reliable and stable our services Proactive approach for stability Fixes server instability / failure Response to @sre Change an infrastructure with code React an alert Review Pull-Request Take long-term task The goal of on-boarding is to be able to do these task by themselves
  41. How to start On-Boading? • Define the goal • Design

    the learning experience • Review through 1on1
  42. “Concrete learning experiences should happen for the entire time leading

    up to the SRE going on- call.” IUUQTMBOEJOHHPPHMFDPNTSFTSFCPPLDIBQUFSTBDDFMFSBUJOHTSFPODBMM
  43. “Concrete learning experiences should happen for the entire time leading

    up to the SRE going on- call.” IUUQTMBOEJOHHPPHMFDPNTSFTSFCPPLDIBQUFSTBDDFMFSBUJOHTSFPODBMM
  44. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task How should they learn to achieve the goal?
  45. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task Preparation Change an Infrastructure Review Pull-Request Learn / React an alert Take long-term task
  46. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task Preparation Change an Infrastructure Review Pull-Request Learn / React an alert Take long-term task
  47. Check List

  48. SRE Handbook

  49. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task Preparation Change an Infrastructure Review Pull-Request Learn / React an alert Take long-term task
  50. Change an Infrastructure

  51. Release release/<role name>

  52. FMPRT First Meaningful Pull Request Time https://scrapbox.io/ohbarye/First_Meaningful_Pull_Request_Time (In Japanese)

  53. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task Preparation Change an Infrastructure Review Pull-Request Learn / React an alert Take long-term task
  54. Review Pull-Request

  55. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task Preparation Change an Infrastructure Review Pull-Request Learn / React an alert Take long-term task
  56. Learn an alert

  57. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task Preparation Change an Infrastructure Review Pull-Request Learn / React an alert Take long-term task
  58. Take long-term task

  59. Design the learning experience Goal Change an infrastructure with code

    React an alert Review Pull-Request Take long-term task Preparation Change an Infrastructure Review Pull-Request Learn / React an alert Take long-term task
  60. How to start On-Boading? • Define the goal • Design

    the learning experience • Review through 1on1
  61. Review weekly through 1on1: 3 questions • What do you

    do recently? • What are you plan for the next week? • Are you in any trouble?
  62. Review weekly through 1on1 • What do you do recently?

    • What are you plan for the next week? • Are you in any trouble?
  63. Review weekly with 1on1: How close you are to goal?

    Change an infrastructure with code Review Pull-Request React an alert Take mid/long term task Need some more time… ✅ Need some more time… ✅ Goal for On-boarding
  64. Agenda • Background • What is On-Boarding? • How to

    start On-Boading? • To apply beyond SRE • Takeaways
  65. Can also be used for teams other than SRE

  66. Web Developer’s OnBoarding • Remove the fear of new joiner

    • Make a fixed task efficient • Improve continuously
  67. Issue Template & Continuously improve For new joiner For mentor

  68. To other product

  69. Improve by new joiner

  70. Future work

  71. Agenda • Background • What is On-Boarding? • How to

    start On-Boading? • To apply beyond SRE • Takeaways
  72. Takeaways What's important for On-boarding? • Getting rid of the

    anxiety • Narrow the scope of thinking How To start on-Boarding? 1. Define the goal • From Mission / Responsibility / Daily Work of your team 2. Design the learning experience • Should be concrete and ordered to achieve the goal 3. Review through 1on1 • Check the reach of Goal and get rid of troubles
  73. Let’s begin from simple 3 questions • What is your

    team’s mission? • What is your team’s responsibility? • What is your team’s daily work?
  74. Any question? Tweet me #srecon #srecon19onboarding @chaspy_ @chaspy_en take.she12@gmail.com

  75. Thank You! chaspy chaspy_ / chaspy_en Site Reliability Engineer at

    Quipper Takeshi Kondo