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
Indexing and Query Performance
00:00
5 left

Indexing and Query Performance

MediumSQL · PostgreSQL

Problem

Explain the importance of indexing in databases.

Use the provided PostgreSQL tickets table to demonstrate a selective lookup. Write a query that returns open tickets created on or after January 1, 2025, and briefly explain how an appropriate index could improve this query.

Output

  1. One row per matching ticket with columns ticket_id, status, priority, and created_at
  2. Exclude tickets that are not open or were created before the specified date
  3. Sort by newest created_at first, then ticket_id ascending

Schema

tickets
ColumnTypeDescription
ticket_idPKINTUnique ticket identifier
statusVARCHAR(20)Current ticket status
priorityVARCHAR(20)Ticket priority
created_atDATEDate the ticket was created
Tablestickets
Interviewer

Your question is Indexing and Query Performance. 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.