Slide 1

Slide 1 text

How to Start On-Boarding of SRE Takeshi Kondo SRE at Quipper @chapsy / @chaspy_en #srecon19onboarding SRECon19 Asia/Pacific

Slide 2

Slide 2 text

2018/06/20 Joined Quipper as SRE 2019/06/14 Speaking at SRECon 2

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

Team side My side

Slide 6

Slide 6 text

Team side My side

Slide 7

Slide 7 text

No On-Boarding Mechanism

Slide 8

Slide 8 text

Team side My side

Slide 9

Slide 9 text

My side Technical Challenge Mental Problem

Slide 10

Slide 10 text

My side Technical Challenge Mental Problem

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

My side Technical Challenge Mental Problem

Slide 14

Slide 14 text

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

Slide 15

Slide 15 text

Why did I do on-boarding?

Slide 16

Slide 16 text

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

Slide 17

Slide 17 text

Should I do On-boarding?

Slide 18

Slide 18 text

“On-boarding works effectively even for senior engineers”

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

Achievement Me: ——————> 6 months No On-boarding process NextSRE: ——> 2 months With my On-boarding

Slide 23

Slide 23 text

Agenda • Back Ground • What is On-boarding? • How to start On-boading? • To apply beyond SRE • Takeaways

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

On-boarding is NOT an account creation nor just assigning tasks

Slide 26

Slide 26 text

On-boarding is Mechanism

Slide 27

Slide 27 text

For early strength of the new joiners

Slide 28

Slide 28 text

“On-boarding works effectively even for senior engineers”

Slide 29

Slide 29 text

What did I need?

Slide 30

Slide 30 text

My side Technical Challenge Mental Problem

Slide 31

Slide 31 text

Technical gap and Anxiety -> Less Outcome

Slide 32

Slide 32 text

KeyPoint • Reduce anxiety • Narrow the scope of thinking

Slide 33

Slide 33 text

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

Slide 34

Slide 34 text

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

Slide 35

Slide 35 text

How to start On-Boading? • Define the goal • Design the learning experience • Review through 1on1

Slide 36

Slide 36 text

To define the goal, let’s ask 3 simple questions

Slide 37

Slide 37 text

Questions to define the goal • What is your team’s • mission? • responsibility? • daily work?

Slide 38

Slide 38 text

Mission / Responsibility / Daily Work Mission Daily Work Responsibility Proactive action based on team values Goal for On-boarding

Slide 39

Slide 39 text

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

Slide 40

Slide 40 text

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

Slide 41

Slide 41 text

How to start On-Boading? • Define the goal • Design the learning experience • Review through 1on1

Slide 42

Slide 42 text

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

Slide 43

Slide 43 text

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

Slide 44

Slide 44 text

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?

Slide 45

Slide 45 text

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

Slide 46

Slide 46 text

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

Slide 47

Slide 47 text

Check List

Slide 48

Slide 48 text

SRE Handbook

Slide 49

Slide 49 text

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

Slide 50

Slide 50 text

Change an Infrastructure

Slide 51

Slide 51 text

Release release/

Slide 52

Slide 52 text

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

Slide 53

Slide 53 text

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

Slide 54

Slide 54 text

Review Pull-Request

Slide 55

Slide 55 text

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

Slide 56

Slide 56 text

Learn an alert

Slide 57

Slide 57 text

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

Slide 58

Slide 58 text

Take long-term task

Slide 59

Slide 59 text

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

Slide 60

Slide 60 text

How to start On-Boading? • Define the goal • Design the learning experience • Review through 1on1

Slide 61

Slide 61 text

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

Slide 62

Slide 62 text

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

Slide 63

Slide 63 text

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

Slide 64

Slide 64 text

Agenda • Background • What is On-Boarding? • How to start On-Boading? • To apply beyond SRE • Takeaways

Slide 65

Slide 65 text

Can also be used for teams other than SRE

Slide 66

Slide 66 text

Web Developer’s OnBoarding • Remove the fear of new joiner • Make a fixed task efficient • Improve continuously

Slide 67

Slide 67 text

Issue Template & Continuously improve For new joiner For mentor

Slide 68

Slide 68 text

To other product

Slide 69

Slide 69 text

Improve by new joiner

Slide 70

Slide 70 text

Future work

Slide 71

Slide 71 text

Agenda • Background • What is On-Boarding? • How to start On-Boading? • To apply beyond SRE • Takeaways

Slide 72

Slide 72 text

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

Slide 73

Slide 73 text

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?

Slide 74

Slide 74 text

Any question? Tweet me #srecon #srecon19onboarding @chaspy_ @chaspy_en [email protected]

Slide 75

Slide 75 text

Thank You! chaspy chaspy_ / chaspy_en Site Reliability Engineer at Quipper Takeshi Kondo