Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
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 feedbackSuccess 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
Optimizing a Slow Query
00:00
5 left

Optimizing a Slow Query

MediumSQL · PostgreSQL

Problem

How would you optimize a slow-running query?

Using the provided PostgreSQL schema, write an optimized query that returns monthly metrics for active sites during January and February 2025. The query should avoid unnecessary rows and preserve sites with activity in either metric source.

Output

  1. One row per active site and month with activity
  2. Columns: site_id, site_name, month, pageviews, and revenue
  3. Include only January and February 2025 activity, sort by site_id, then month ascending, and return zero revenue when no non-null revenue exists

Schema

sites
ColumnTypeDescription
site_idPKINTUnique site identifier
site_nameVARCHAR(100)Display name of the site
is_activeBOOLEANWhether the site is currently active
page_views
ColumnTypeDescription
view_idPKINTUnique page-view identifier
site_idINTSite associated with the page view
viewed_atTIMESTAMPTimestamp when the page was viewed
ad_revenue
ColumnTypeDescription
revenue_idPKINTUnique revenue record identifier
site_idINTSite associated with the revenue
recorded_atTIMESTAMPTimestamp associated with the revenue record
revenue_amountNUMERIC(12,2)Revenue amount for the record
Tablessitespage_viewsad_revenue
Interviewer

Your question is Optimizing a Slow Query. 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.