Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan
Build Subscription Status Timeline
00:00
5 left

Build Subscription Status Timeline

MediumSQL · PostgreSQL

Problem

Given a table of user subscription changes, write a query to construct a historical timeline of each user's subscription status.

Use subscription_changes; when multiple changes share a user and timestamp, the greatest change_id is authoritative. Consecutive records with the same status represent one interval.

Output

  1. One row per status interval, with user_id, status, effective_from, effective_to, and is_current.
  2. effective_to is NULL for the current interval.
  3. Order by user_id, then effective_from, then change_id.

Schema

subscription_changes
ColumnTypeDescription
change_idPKINTUnique identifier for the subscription change
user_idINTIdentifier of the user
changed_atTIMESTAMPTimestamp when the subscription status changed
subscription_statusVARCHAR(30)Status recorded by the change event
change_sourceVARCHAR(30)System or workflow that recorded the change
Tablessubscription_changes
Interviewer

Your question is Build Subscription Status Timeline. Start with the requirements and the one table in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.