Skip to content

Remove CSE and CSE Manager roles from Mandatory Roles for Secure Coding Training

Christopher Guitarte requested to merge remove-cse-cse-manager-roles into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

I am removing the CSE and CSE Manager roles from the mandatory roles included for secure coding training.

A Customer Success Engineer at GitLab is not really creating/reviewing real code on a regular basis that would be considered usable for production. I think that we might have gotten lumped into all of the roles that were identified to be assigned the training because we have engineer in our job title. Surprisingly I did not see the Solutions Architects assigned which is what I think our role is closest to in terms of the technical experience required and the day-to-day duties when speaking with customers or working with our product.

CC @scale-cses / @taylorlund / @gitlab-com/gl-security/appsec

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Christopher Guitarte

Merge request reports