Reliability Engineering

1. You are here:
2. Handbook
3. Engineering
4. Infrastructure
5. Team
6. Reliability Engineering

On this page

• On this page
• Common Links
• Mission
• Vision
  • Key Metrics
• Team
  • Team Members
    • Reliability Engineering, Secure & Defend
    • Reliability Engineering, CI/CD & Enablement
    • Reliability Engineering, Dev & Ops

Common Links

Workflow	How may we be of service?	GitLab.com Status	STATUS
Issue Trackers	Infrastructure: Milestones, OnCall	Production: Incidents, Changes, Deltas	Delivery
Slack Channels	#sre-lounge, #database	#alerts, #production	#g_delivery
Operations	Runbooks (please contribute!)	On-call: Handover Document, Reports

Mission

Reliability Engineering teams are the gatekeepers and primary caretakers of the operational environment hosting all of GitLab's user-facing services (most notably GitLab.com), focusing on their availability, performance and scalability through reliability considerations.

Vision

Reliability Engineering team are composed of DBREs and SREs. As the role titles indicate, they have different areas of specialty but focus on the reliability of the environment as the unifying goal.

Reliability Engineering teams own the following operational processes:

• change management
• incident management
• delta management

The teams' overarching goal with respect to these processes is to outdate them through automation.

Key Metrics

Key metrics related to this group include:

• Uptime: of the operational environment at large and of services, subsystems and components.
• Incidents: alerts (including false positives), count, length (elapsed time), outages, escalations
• Deployments: count, length (elapsed time), “good” vs “bad”
• Efficiencies: manual vs automated tasks, (unexpected) interrupts

Team

Each member of the Site Reliability Team is part of this vision:

• Each team member is able to work on all team projects
• The team is able to reach a conclusion independently all the time, consensus most of the time
• Career development paths are clear
• Team creates a database of knowledge through documentation, training sessions and outreach

Team Members

The following people are members of the Reliability Engineering Teams:

Reliability Engineering, Secure & Defend

Person	Role
Anthony Sandoval	Engineering Manager, Reliability Engineering, Secure & Defend
Andreas Brandl	Senior Database Reliability Engineer, Secure & Defend
Henri Philipps	Senior Site Reliability Engineer, Secure & Defend
Craig Barrett	Senior Site Reliability Engineer, Defend & Secure
Craig Miskell	Site Reliability Engineer
Matt Smiley	Senior Site Reliability Engineer

Reliability Engineering, CI/CD & Enablement

Person	Role
Dave Smith	Engineering Manager, Reliability Engineering, CI/CD & Enablement
Alejandro Rodríguez	Site Reliability Engineer, Gitaly & Distribution
Alex Hanselka	Site Reliability Engineer, Verify, Release, Fulfillment
Devin Sylva	Senior Site Reliability Engineer, Package, Geo
Cameron S McFarland	Senior Site Reliability Engineer, Package, Fulfillmnet, Distribution
Casey Allen Shobe	Senior Database Reliability Engineer, CI/CD & Enablement
Nels Nelson	Senior Site Reliability Engineer

Reliability Engineering, Dev & Ops

Person	Role
Jose Cores Finotto	Engineering Manager, Reliability Engineering, Dev & Ops
Ahmad Sherif	Site Reliability Engineer, Manage, Monitor & Configure
Amarbayar Amarsanaa	Senior Site Reliability Engineer, Create, Plan, Monitor
Yun Guo	Senior Database Reliability Engineer, Dev & Ops
Hendrik Meyer	Site Reliability Engineer, Dev & Ops
Michal Wasilewski	Site Reliability Engineer, Create & Plan
Craig Furman	Senior Site Reliability Engineer