The Govern engineering groups are responsible for the Govern Stage of the product.
Help users manage security vulnerabilities, policies, and compliance across their organization.
| Person | Role |
|---|---|
| Nathan Rosandich | Fullstack Engineering Manager, Govern:Compliance |
| Aaron Huntsman | Senior Backend Engineer, Govern:Compliance |
| Harsimar Sandhu | Backend Engineer, Govern:Compliance |
| Hitesh Raghuvanshi | Senior Backend Engineer, Govern:Compliance |
| Huzaifa Iftikhar | Senior Backend Engineer, Govern:Compliance |
| Illya Klymov | Senior Frontend Engineer, Govern:Compliance |
| Jay Montal | Fullstack Engineer, Govern:Compliance |
| Sam Figueroa | Fullstack Engineer, Govern:Compliance |
| Michael Becker | Senior Backend Engineer, Govern:Compliance |
The following members of other functional teams are our stable counterparts:
| Person | Role |
|---|---|
| Alana Bellucci | Senior Product Manager, Govern:Threat Insights |
| Derek Ferguson | Senior Product Manager, Govern:Compliance and Secure:Dynamic Analysis |
| Grant Hickman | Senior Product Manager, Govern:Security Policies |
| Evan Read | Senior Technical Writer, Govern:Compliance, Manage:Import and Integrate, Systems:Distribution, Systems:Gitaly |
| Harsha Muralidhar | Senior Software Engineer in Test, Govern:Threat Insights |
| Mark Lapierre | Senior Software Engineer in Test, Govern:Compliance |
| Ottilia Westerlund | Security Engineer, Fulfillment (Fulfillment Platform, Billing and Subscription Management), Govern (Security Policies, Threat Insights), Monitor (Observability), Plan (Product Planning) |
| Joseph Longo | Manager, Governance and Field Security |
Because we have a wide range of domains to cover, it requires a lot of different expertise and skills:
| Technology skills | Areas of interest |
|---|---|
| Ruby on Rails | Backend development |
| Go | Backend development |
| Vue, Vuex | Frontend development |
| GraphQL | Various |
| SQL (PostgreSQL) | Various |
| Docker/Kubernetes | Threat Detection |
We also track our backlog of issues, including past due security and infradev issues, and total open SUS-impacting issues and bugs.
MR Type labels help us report what we're working on to industry analysts in a way that's consistent across the engineering department. The dashboard below shows the trend of MR Types over time and a list of merged MRs.
We meet bi-weekly synchronously to discuss stage and group wide topics. We primarily try to use Epics/Issues to intiate discussions and maintian transparency. We use the Anti-abuse-govern-growth-sub-dept Board to better organize our discussions.
The following table lists the Govern Stage management team members who will cover in the event that one or more are unable to work due to unforeseen circumstances.
| Team Member | Covered by | Escalation |
|---|---|---|
| Phil Calder | Wayne Haber | Christopher Lefelhocz |
| Alan (Maciej) Paruszewski | Nathan Rosandich | Phil Calder |
| Nathan Rosandich | Alan (Maciej) Paruszewski | Phil Calder |
| Thiago Figueiró | Neil McCorrison | Phil Calder |
| Neil McCorrison | Thiago Figueiró | Phil Calder |
Team members should contact any Govern Engineering Manager by mentioning in #sd_govern_engineering if they need management support for a problem that arises, such as a production incident or feature change lock, when their direct manager is not available. The Govern manager can provide guidance and coordination to ensure that the team member receives the appropriate help.
The Engineering Manager will allocate open issues and merge requests to another engineer, ideally in the same group, if an engineer is absent.
Some people management tasks, including Workday and Navan Expense, may require for escalation or delegation.
In the event that one or more team members become unavailable for any reason, this can serve as the foundation for a business continuity plan (BCP) and serve as a basic guide for Managing Engineering continuity.
gitlab-org/governgitlab.com_ed6207uel78de0j1849vjjnb3k@group.calendar.google.com