Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
www-gitlab-com
www-gitlab-com
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 1,548
    • Issues 1,548
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1,384
    • Merge Requests 1,384
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Packages
    • Packages
    • Container Registry
  • Analytics
    • Code Review
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.com
  • www-gitlab-comwww-gitlab-com
  • Issues
  • #5555

Closed
Open
Opened Oct 16, 2019 by Eric Johnson@edjdev
  • Report abuse
  • New issue
Report abuse New issue

WIP: Support Engineer Job family country-of-residence block

Edit as of 12-Nov-2018: This is still a discussion and there is no official policy confirming this yet. GitLab has posted an update and clarification of this policy on its blog here: https://about.gitlab.com/blog/2019/11/12/update-on-hiring/

All comments must remain within our Code of Conduct.


In e-group on Monday October 15, 2019 we took the decision to enable a "job family country-of-residence block" for team members who have access to customer data. This is at the expressed concern of several enterprise customers, and also what is becoming a common practice in our industry in the current geopolitical climate.

The countries involved are:

  • China
  • Russia

This issue is to track the addition of the process to the support handbook, and whatever recruiting processes need to be update to make certain that:

  1. We do not make offers to individuals residing in these countries
  2. Current team members are prevented from moving to these countries and remaining in a role that prohibits it.

We do not have a technical way, today, to handle this based on permissions. Doing so would also force us to confront the possibility of creating a "second class of citizens" on certain teams who cannot take part in 100% of their responsibilities, which is a dynamic some of us have experienced at other companies and found highly negative. As such we feel a country block is the most humane solution at this time--especially because it affects zero current employees.

We should look into the effort to do this on a permissions-basis. So everyone is clear what the effort would be, and roughly how long this would take.

Discussion in #job-family-country-blocks since there are multiple related issues open and content should be consistent, if not shared.

Note: In addition to Support, this also affects SREs in infra and SecOps & Anti-Abuse in Security (see related issue).

CC @sytses @mmcb @sunghaekim @rtakken @lmcnally1 @glopezfernandez

Edited Nov 13, 2019 by Todd Barr

Related issues

  • Discussion
  • Designs
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Nov 6, 2019
Due date
Nov 6, 2019
2
Labels
Engineering Management Support Department
Assign labels
  • View project labels
Reference: gitlab-com/www-gitlab-com#5555