Meta
Analytics Reporting Track · Medium · 25 min
Severity-One Resolution Pace
Reliability engineering wants to compare how quickly teams resolve the most urgent incidents. Return team_name, critical_incidents, and avg_resolution_hours ...
Company labels are directional practice context, not official interview guidance.
Objective
Practice query basics through a Meta-tagged business scenario.
Approach
Use this track to train on SQL that mirrors day-to-day analytics workflows and recurring reporting asks.
Company context
Company labels are directional practice context, not official interview guidance.
Reliability engineering wants to compare how quickly teams resolve the most urgent incidents. Return team_name, critical_incidents, and avg_resolution_hours rounded to two decimals for severity = 1 incidents. Sort by team_name.
incidents
| incident_id | team_name | |||
|---|---|---|---|---|
| 1 | Ads Infra | 1 | 2024-08-01 01:00:00 | 2024-08-01 03:30:00 |
| 2 | Ads Infra | 2 | 2024-08-02 10:00:00 | 2024-08-02 14:00:00 |
| 3 | Core Feed | 1 | 2024-08-03 06:00:00 | 2024-08-03 09:00:00 |
| 4 | Core Feed | 1 | 2024-08-04 12:00:00 | 2024-08-04 14:30:00 |
| 5 | Messaging | 1 | 2024-08-05 08:00:00 | 2024-08-05 10:00:00 |
SQL workspace
Run queries against the protected question data, then submit once the result shape looks right.
Sign in to run SQL
Create a free account or sign in before running queries against protected question data.