Add bazel-release stuff.

_data/experience.yaml

@@ -91,21 +91,42 @@ roles:
                           # Q3 2014 - but it hadn't gotten cold yet
     endDate: 2017-06-15 # did I truly ever stop working on the release process?
                         # however, this is around when it stopped being my job
-    description: "The long version is, I did so much freaking junk on this thing."
+    shortDescription: >
-    shortDescription: "The short version is, a lot."
+      Migrations, stability, and features for the internal release process of
+      Bazel (a.k.a. Blaze).
+    description: >
+      Local expert on Google-internal release and testing tools, primary expert
+      on the release process for the Google-internal version of Bazel (a.k.a.
+      Blaze).
     achievements:
+      - id: testability
+        description: >
+          Updated old release Bash scripts to allow for testing of changes
+          without risking the stability of the release.
+      - id: autorerun
+        description: >
+          Automated the rerunning of all tests across Google's continuous
+          builds, saving sheriffs the time and hassle of manually checking the
+          results and starting reruns.
+      - id: documentation
+        description: >
+          Thoroughly documented the existing release process and all changes
+          being made to it and presented this information at a team summit,
+          sharply reducing sheriff confusion.
+      - id: sheriff
+        description: >
+          Consulted with sheriffs and acted as a go-to backup sheriff during
+          especially difficult situations. Received 4 peer bonuses for different
+          key moments of help.
+      - id: redesign
+        description: >
+          Designed a new version of the release process using more modern
+          infrastructure, avoiding version desync problems and allowing better
+          testing.
       - id: mentor
         description: >
-          I taught Florian the secrets of releases.
+          Mentored a new team member in Python and internal release tools,
-      - id: teach
+          guided him through the implementation of the release process redesign.
-        description: >
-          I taught everyone else how to be sheriff.
-    # * Bazel release process fixing and documentation
-    # * Bazel release process overhaul design
-    # * PB: Sheriffing (x3)
-    # * PB: Diagnosed & wrote tool to fix bug in test, reenabling releases
-    # * Perf: Engineering conscientiousness (doing the right thing)
-    # * Perf: Energetic and invested
   - id: bazel-android
     image: jobs/google/bazel-old.png
     name: Software Engineer # II