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
Optimize Large Historical Aggregation
00:00
5 left

Optimize Large Historical Aggregation

HardSQL · PostgreSQL

Problem

Optimize a slow-running query that aggregates millions of historical home price records at Redfin.

Using the provided schema, return monthly statistics for valid single-family home price records from 2024. The query should avoid unnecessary processing and include the previous available monthly average for each market.

Output

  1. One row per market and month, with market_name, month_start, average_price, record_count, previous_month_average, and percent_change
  2. Include only valid records from 2024 and markets with matching properties
  3. Sort by market_name, then month_start ascending

Schema

home_price_history
ColumnTypeDescription
price_record_idPKINTUnique historical price record identifier
property_idINTProperty associated with the price record
recorded_atDATEDate when the historical price was recorded
sale_priceNUMERIC(12,2)Recorded home sale price
properties
ColumnTypeDescription
property_idPKINTUnique property identifier
market_idINTMarket containing the property
property_typeVARCHAR(30)Property classification
bedroomsINTNumber of bedrooms
markets
ColumnTypeDescription
market_idPKINTUnique market identifier
market_nameVARCHAR(80)Redfin market name
state_codeVARCHAR(2)Two-letter state code
Tableshome_price_historypropertiesmarkets
Interviewer

Your question is Optimize Large Historical Aggregation. Start with the requirements and the three tables 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.