Skip to content
Back to challenges
Grain and Fact TypesConcept Challengeintermediate25 min

Recruiting pipeline lifecycle

Use an accumulating snapshot to track one candidate application through hiring milestones.

How this preview works
Preview this problem before signing in. Sign in to save progress and submit work.

Concept

fact-table-grain

The primary modeling idea this problem reinforces.

Requirements

5

Business needs the model must satisfy.

Read the concept guide: Fact table grain
Scenario

A recruiting operations team wants time-to-hire by department, source channel, and candidate segment. Each application can pass through applied, screen, onsite, offer, and hired or rejected milestones.

Why this matters

Hiring funnels are workflow processes. A purely event-shaped model can count stage changes, but the operations question is often how long a specific application takes to move through the pipeline.

Requirements
  • Create a recruiting pipeline fact where one row represents one candidate application for one requisition.
  • Keep the application id queryable on the fact.
  • Add applied, onsite, and hired milestone timestamps.
  • Add a duration measure such as days_to_hire.
  • Connect candidate and requisition dimensions through explicit N:1 relationships.
Read-only starter workspace
Inspect the authored starting ERD, then open the workspace to edit and run the checks. Saving your progress needs a free account.

Template

Recruiting pipeline starter workspace

The model users start from in the full workspace.

Entities

2

Seeded tables visible in the public preview.

Dialect

postgresql

Generated SQL target for this starter model.

Mini Map

This preview is read-only. Open the workspace to edit and verify; saving needs a free account.

Open workspace

Try the question first.

The discussion has other people's approaches and solutions. Give it a real attempt before you read them.