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
SQL Joins in Scenarios
00:00
5 left

SQL Joins in Scenarios

MediumSQL · PostgreSQL

Problem

How would you approach scenario-based SQL questions involving joins?

Use the provided properties and edge_requests tables. Return metrics for successful requests from January 1 through January 7, 2025, while retaining properties with no qualifying requests.

Output

  1. One row per property, including properties with no qualifying requests.
  2. Columns: property_id, property_name, successful_request_count, and total_bytes.
  3. Treat missing totals as zero and order by property_id ascending.

Schema

properties
ColumnTypeDescription
property_idPKINTUnique property identifier
property_nameVARCHAR(100)Property display name
regionVARCHAR(20)Property operating region
is_activeBOOLEANWhether the property is active
edge_requests
ColumnTypeDescription
request_idPKINTUnique request identifier
property_idINTReferenced property identifier
occurred_atTIMESTAMPRequest timestamp
status_codeINTHTTP response status code
bytes_sentBIGINTResponse bytes sent
Tablespropertiesedge_requests
Interviewer

Your question is SQL Joins in Scenarios. Start with the requirements and the two 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.