SQL Take-Home Interview Simulation

Practice a timed support-operations case with event cleanup, reporting-cutoff logic and independently checked solutions.

Sold individually. This product is not included in the existing toolkits or Ultimate Bundle.

### 01. Source quality (10 points)

Return raw event rows, exact duplicate rows, orphan rows, pre-creation rows, future rows, and conflicting event IDs. These diagnostics can overlap. Audit the raw events table.

### 02. August intake (10 points)

Count tickets created in August through the reporting cutoff by priority. Return priority and opened_tickets, sorted by priority.

### 03. Open-ticket snapshot (15 points)

Return every open ticket at the cutoff with ticket_id, priority and age_days. Age is the difference between calendar dates. Use lifecycle events, not the most recent reply. Sort by ticket_id.

### 04. Open backlog aging (10 points)

Count open tickets in 0–7, 8–14, 15–30 and 31+ calendar-day bands. Return all four bands in that order, including zero counts.

What you can do with it

• Eight assignments with a 100-point scoring rubric
• 120 fictional tickets, lifecycle events, agents and policies
• Standard and edge-case fixtures with expected CSV outputs
• Candidate starter SQL, explained solutions and a verification script

What is included

Version 1.0 · one ZIP download · 27 KB

How to use it

1. Read ASSIGNMENT.md before looking at the solution folder. Use the supplied reporting cutoff and definitions.
2. Follow START-HERE.md to create the disposable SQLite database. Work in the candidate SQL files and allow yourself 90 minutes.
3. Submit query outputs and a short explanation of the reporting grain, event exclusions and limits.

The included guide continues with definitions, review steps and product-specific limits.

Before you choose

This is a new support-operations case, separate from the Career Pack’s 18-exercise interview lab and portfolio projects.

The assignment defines the cutoff, first human response, eligible SLA cohort, reopenings and closure activity. Follow those definitions rather than assuming a generic ticket metric.