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
Optimizing Slow SQL Queries
00:00
5 left

Optimizing Slow SQL Queries

HardSQL · PostgreSQL

Problem

Explain the process of optimizing a slow-running SQL query at Pinterest.

Using the provided PostgreSQL schema, explain how you would investigate and improve the query, then provide the optimized query. Address execution plans, filtering, joins, aggregation, and relevant indexing decisions.

Output

  1. One row per qualifying creator with creator_id, creator_name, and qualifying_saves
  2. Include only published pins with saves from January 2025 and at least two qualifying saves
  3. Order by qualifying_saves descending, then creator_id ascending

Schema

creators
ColumnTypeDescription
creator_idPKINTUnique Pinterest creator identifier
creator_nameVARCHAR(100)Display name of the creator
pins
ColumnTypeDescription
pin_idPKINTUnique pin identifier
creator_idINTCreator who published the pin
statusVARCHAR(20)Current pin publication status
pin_saves
ColumnTypeDescription
save_idPKINTUnique save event identifier
pin_idINTPin that was saved
saved_atTIMESTAMPTimestamp when the pin was saved
Tablescreatorspinspin_saves
Interviewer

Your question is Optimizing Slow SQL Queries. 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.