Zero to SRE

Zero to SRE

Being able to transform a junior engineer into an excellent mid, then senior engineer is a competitive advantage for any company. Unfortunately, there aren’t many entry-level SRE job postings, and if your company hasn’t hired juniors before, you’ll need to make changes in order to create an environment where they can thrive.

This talk is the story of a junior Web Developer turned SRE. I’ve been able to successfully transition into my role because my company has embraced junior engineers by creating a ‘Culture of Error,’ encouraging all engineers to be mentors, and ensuring that all employees take time during the day to learn new skills. We’ve made some mistakes, too, but we’ve learned a lot in the process.

By end of this talk, I’ll share the specific details of how to support junior engineers during their first day, month, 90 days and year, including:
* How to create a learning plan with your junior engineer on their first day
* Strategies for getting your new engineer to contribute to your code base or infrastructure during their first week
* A description of the company-wide attitudes and mindsets that have allowed these practices to flourish

Videos:
https://www.youtube.com/watch?v=2wiTfNh9pnY&list=PL3xK3UeH8dyZsM56-bYQlbLwXbtKSulca

04c8d2026273e27d74b003c18c3b8261?s=128

Kim Schlesinger

April 29, 2019
Tweet

Transcript

  1. 2.
  2. 9.

    Agenda 1. Your company's culture 2. Prepare for the junior

    SRE's day one 3. Provide them personalized resources and ongoing support @kimschles
  3. 18.

    Guarantee 20% Time for Learning Create a Culture of Error

    Leverage teams, not individuals @kimschles
  4. 30.

    Novice Is not yet ready to undertake work for a

    client. Should pass through this level quickly. Advanced Beginner Able to work as a junior engineer on a client team with more or less help from senior Trussel on team. truss.works @kimschles
  5. 32.

    Attempts to characterize and resolve roadblocks through 5-15 min Google

    searching before reporting. truss.works @kimschles
  6. 33.

    Breaks moderately-sized tasks down into smaller units of work upon

    request and reviews break- down with senior engineers. truss.works @kimschles
  7. 36.

    Prepare a technical learning plan that is aligned with the

    day-to- day work of your engineers. @kimschles
  8. 37.

    Example Topics for the Learning Plan: • git and linux

    commands • yaml • VPC with AWS and GCP • Docker and Kubernetes @kimschles
  9. 38.

    Your junior engineer should independently complete large and small projects

    as part of their technical learning plan. @kimschles
  10. 43.

    Be explicit about your desired timeline for the junior SRE's

    first independent contribution. @kimschles
  11. 48.

    Concrete kubectl get services -n kube-system kubectl get pods -n

    kube-system kubectl get pods -n kube-system -o wide @kimschles
  12. 62.
  13. 63.

    Agenda 1. Your company's culture 2. Prepare for the junior

    SRE's day one 3. Provide them personalized resources and ongoing support @kimschles
  14. 64.

    Credits • Photos by WOCinTech Chat • Culture of Error

    by Doug Lemov • Steve Kinney • Kyle Coberly • Truss Leveling • ReactiveOps Apprentice Learning Plan @kimschles