data/team.yml

@@ -3251,6 +3251,21 @@
   story:  |
           Jessica is the HR Business Partner supporting Development & Product.  Before joining Gitlab she was held various HR roles at Cisco for 15 years and 2 years at SailPoint as a HRBP.  She currently lives in Austin, TX with her family and enjoys, scuba diving, hiking and eating Italian food.
+- name: Paul E. Duffy
+  locality: Boston, MA  
+  country: USA
+  role: <a href="about.gitlab.com/jobs/strategic-account-leader">Strategic Account Leader</a>
+  reports_to: Regional Sales Director - US East Coast
+  picture: paulduffy.jpg
+  twitter: pauleduffy
+  gitlab: paulduffy
+  departments:
+    - Sales
+  story:  |
+          Paul has spent the last 17 years helping clients implement and adopt 
+          new technology solutions that help drive business value. In his spare time he 
+          loves playing with his two young children, excercising and cheering on The Patriots!
+
 - name: B.W.
   locality:
   country:
@@ -3479,6 +3494,45 @@
   story:  |
           Joining January 15th
+- name: D.T.
+  locality:
+  country:
+  role: <a href="https://about.gitlab.com/jobs/frontend-engineer/">Senior Frontend Engineer</a>
+  reports_to: Frontend Engineering Manager
+  picture: ../gitlab-logo-extra-whitespace.png
+  twitter:
+  gitlab:
+  departments:
+    - Engineering
+  story:  |
+          Joining January 15th
+
+- name: S.K.
+  locality:
+  country:
+  role: <a href="https://about.gitlab.com/jobs/recruiting-director/">Recruiting Director</a>
+  reports_to: Chief Culture Officer
+  picture: ../gitlab-logo-extra-whitespace.png
+  twitter:
+  gitlab:
+  departments:
+    - People Operations
+  story:  |
+          Joining January 15th
+
+- name: A.B.
+  locality:
+  country:
+  role: <a href="https://about.gitlab.com/jobs/specialist/database/">Senior Database Engineer</a>
+  reports_to: VP of Engineering
+  picture: ../gitlab-logo-extra-whitespace.png
+  twitter:
+  gitlab:
+  departments:
+    - Engineering
+  story:  |
+          Joining January 29th
+
 - name: Ernst (interim)
   placeholder: true
   locality:

source/courses/index.html.md

@@ -135,6 +135,9 @@ If you have any language courses you would like to recommend or links to website
 - CST204 [GitLab Maintenance and Support](https://www.youtube.com/watch?v=X8jsj59b4vk&index=4&list=PLFGfElNsQthbFw3QxWjoTsDMoLmZx1SbP)
 - CST205 [We already use JIRA, so shouldn't we go with BitBucket?](https://www.youtube.com/watch?v=-JRab22h9Dg&index=5&list=PLFGfElNsQthbFw3QxWjoTsDMoLmZx1SbP)
 - CST206 [Traditional DevOps Dasiy Chain](https://www.youtube.com/watch?v=YHznYB275Mg)
+- CST207 [Automate to Accelerate](https://www.youtube.com/watch?v=dvayJWwzfPY&t=465s)
+- CST208 [Installing GitLab on GKE](https://www.youtube.com/watch?v=HLNNFS8b_aw&t=1s)
+- CST209 [Connecting GitLab.com to your private cloud on GCP](https://www.youtube.com/watch?v=j6HRDquF0mQ)
 ### Finance (FIN) courses

source/handbook/benefits/index.html.md

@@ -64,13 +64,13 @@ For the avoidance of doubt, the benefits listed below in the General Benefits se
       * For US based employees of GitLab Inc., this benefit is replaced by the
         [Basic Life Insurance](/handbook/benefits/inc-benefits-us/#basic-life-insurance-and-add) that is offered through TriNet.
       * For all other GitLabbers, the following conditions apply:
-         * The team member must be either an employee or direct contractor,
+         * The team member must be either an employee or direct contractor.
          * The team member must have indicated in writing to whom the money
            should be transferred. To do this you must complete this [expression of wishes](https://docs.google.com/document/d/1bBX6Mn5JhYuQpCXgM4mkx1BbTit59l0hD2WQiY7Or9E/edit?usp=sharing) form, email to People Ops, who will then file in BambooHR.
          * For part-time GitLabbers, the lump sum is calculated pro-rata, so
            for example for a team member that works for GitLab 50% of the time,
            the lump sum would be $10,000.
-1. [Paid time off policy](https://about.gitlab.com/handbook/paid-time-off).
+1. [Paid time off policy](https://about.gitlab.com/handbook/paid-time-off)
 1. [Tuition Reimbursement](https://about.gitlab.com/handbook/people-operations/#tuition-reimbursement)
 1. [GitLab Summit](https://about.gitlab.com/culture/summits)
    * Every nine months or so GitLabbers gather at an exciting new location to [stay connected](https://about.gitlab.com/2016/12/05/how-we-stay-connected-as-a-remote-company/), at what we like to call a GitLab Summit. It is important to spend time face to face to get to know your team and, if possible, meet everyone who has also [bought into the company vision](http://www.excitingrole.com/how-to-do-startup-due-diligence/#.h/). There are fun activities planned by our GitLab Summit Experts, work time, and presentations from different functional groups to make this an experience that you are unlikely to forget! Attendance is optional, but encouraged. For more information and compilations of our past summits check out our [summits page](https://about.gitlab.com/culture/summits).
@@ -200,7 +200,7 @@ The mother may opt to share some of her 52 week maternity leave with her spouse/
 Employees accrue all benefits during leave and must have documentation for risk assessment when notifying the company of pregnancy.
 Once an employee notifies GitLab of the pregnancy, People Ops will conduct:
-1. [Risk Assessment](https://docs.google.com/document/d/1qHdbaeFSnqdwkQDTEurHD5QMbLPLuZGBQO_CBnRkpiE/edit) – carry out a risk assessment of her work environment within 1-3 days of notification. This still applies if the employee works from home. The purpose of the assessment is to make the employee aware of any hazards or “risks” to her in the work place/home office to reduce potential injury to her or her baby.
+1. [Risk Assessment](https://docs.google.com/document/d/1qHdbaeFSnqdwkQDTEurHD5QMbLPLuZGBQO_CBnRkpiE/edit) – Carry out a risk assessment of her work environment within 1-3 days of notification. This still applies if the employee works from home. The purpose of the assessment is to make the employee aware of any hazards or “risks” to her in the work place/home office to reduce potential injury to her or her baby.
 1. Notify the employee of the statutory rules/company practice regarding leave, pay, notifications etc with a link to this section of the handbook.
 People Ops will consult with Vistra to ensure that the statute is met.

source/handbook/hiring/interviewing/index.html.md

@@ -41,7 +41,7 @@ depending on the outcome of the screening call, the employment team or manager c
 1. **References**: The hiring manager will conduct [references](#reference-check-process) for promising candidates. The references will be collected at the application stage, but they will not be contacted until later on in the process. This should happen before an offer is made. Three references will be asked for but at minimum two references should be completed - at least one should be a manager, the others to a colleague. The Recruiting team will move the candidate to the "Reference Call" stage in Lever.
 1. **Hiring package**: After reference calls are completed successfully, the employment team submits the [employee approval package](#hiring-package) to the CEO and Hiring Manager.
 1. When the manager or CEO makes the **offer**, this can be done verbally during the call with the applicant, but is always followed quickly with the written offer by the Recruiting team as described in [the section on preparing offers and contracts](#prep-contracts). At this point the candidate is moved to the "Offer" stage by the Recruiting team.
-1. People Ops will verify the candidate is not on any known [Denied Party List](https://www.export.gov/csl-search). 
+1. People Ops will verify the candidate is not on any known [Denied Party List](https://www.export.gov/csl-search).
 1. People Ops will draft and stage a contract based upon the written offer that was extended.
 1. Manager follows up to ensure that the offer is accepted, and that the contract is signed.
 1. People Ops [starts the background check process](/handbook/people-operations/#background-checks) if applicable for the role.
@@ -250,7 +250,9 @@ As part of our hiring process we will ask applicants to provide us with three re
 - What can they improve upon?
 - What advice would you give their next hiring manager?
-You can also elaborate further and ask follow-up questions if the opportunity arises. You should not ask any questions about the person's race, gender, sexual preference, disabilities or health, political affiliations, religion, family (children).
+You can also elaborate further and ask follow-up questions if the opportunity arises. The hiring team will be adding engineering questions into Lever so that all engineering hiring managers have access to the same questions. Additionally, the hiring team will work with each function to identify any other specific questions hiring managers would like to add to Lever for their team.  
+
+You should not ask any questions about the person's race, gender, sexual preference, disabilities or health, political affiliations, religion, family (children).
 All reference check feedback should be entered into Lever using the Reference Checks form. To add this form, go to the candidate's profile, click the three dots "..." next to the notes section, click "Add Form", and choose "Reference Checks".

source/handbook/paid-time-off/index.html.md

@@ -81,10 +81,10 @@ in a long time, look closer at their behaviours.
 * Make sure you let your team members know they can talk to you about their challenges.
 Other [tips to avoid burnout](http://www.mayoclinic.org/healthy-lifestyle/adult-health/in-depth/burnout/art-20046642?pg=2) include:
-* Assess and pursue your interests, skills and passions
+* Assess and pursue your interests, skills and passions.
 * Take breaks during the day to eat healthy foods and stretch your legs. [Timeout app](http://dejal.com/timeout/) can help with that.
-* Make time each day to increase blood and oxygen circulation which improves brain activity and functionality
-* Get plenty of restful sleep
+* Make time each day to increase blood and oxygen circulation which improves brain activity and functionality.
+* Get plenty of restful sleep.
 * Meditate to take your mind away from work. [Headspace](https://www.headspace.com/science) and [Calm](https://www.calm.com/meditate) are good tools for creating meditation
 habits.
 * Don't start with work as soon as you wake up. Take your time doing your morning routine.

source/sdlc/index.html.md

@@ -27,13 +27,13 @@ Below we've listed the [stages of the DevOps toolchain](https://en.wikipedia.org
 | Stage     | Product category         | GitLab                    | GitHub             | Atlassian self hosted / SaaS   | Legacy Open Source |
 |-----------|--------------------------|---------------------------|--------------------|--------------------------------|--------------------|
+| Plan      | Portfolio management     | GitLab Portfolio management | n/a.             | n/a                            | n/a                |
 | Plan      | Issue tracking           | GitLab Issues             | GitHub Issues      | JIRA / Trello                  | Redmine            |
-| Plan      | Kanban boards            | GitLab Boards             | ZenHub             | JIRA / Trello                  | Kanboards          |
 | Create    | Version control          | GitLab SCM                | GitHub             | BitBucket Server/.org          | SVN                |
-| Create    | Code review              | GitLab SCM                | GitHub             | Crucible/BitBucket.org          | Gerrit             |
+| Create    | Code review              | GitLab SCM                | GitHub             | Crucible/BitBucket.org         | Gerrit             |
 | Verify    | Continuous integration   | GitLab CI                 | Travis CI          | Bamboo / BitBucket CI          | Jenkins CI         |
 | Verify    | Security testing         | GitLab SAST               | Gemnasium          | n/a                            | SonarQube          |
-| Package   | Container registry       | GitLab Container Registry | Docker Trusted Registry | n/a                            | Jfrog Artifactory  |
+| Package   | Container registry       | GitLab Container Registry | Docker Trusted Registry | n/a                       | Jfrog Artifactory  |
 | Release   | CD/Release automation    | GitLab CD                 | Codefresh          | Bamboo / BitBucket Deployments | Jenkins Pipeline   |
 | Configure | Configuration management | GitLab Secret variables   | n/a                | n/a / Environment variables    | Puppet             |
 | Monitor   | Monitoring               | GitLab Metrics            | Sentry             | n/a                            | Nagios             |