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
ExperiencesCoaching
New
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
Get started
Handle Nulls in Large Joins
00:00
5 left

Handle Nulls in Large Joins

MediumSQL · PostgreSQL

Problem

How would you handle null values when performing a join between two large tables?

Using the supplied orders and customer_accounts tables, write a query that preserves every order, avoids matching NULL customer keys, substitutes readable values for missing account attributes, and classifies each order's match status.

Output

  1. One row per order with order_id, customer_id, customer_name, segment, and join_status.
  2. Include matched orders, orders with NULL customer IDs, and orders with non-matching customer IDs.
  3. Sort by order_id ascending.

Schema

orders
ColumnTypeDescription
order_idPKINTUnique order identifier
customer_idINTCustomer account identifier, when available
order_amountDECIMAL(10,2)Order value
order_channelVARCHAR(30)Channel through which the order was placed
customer_accounts
ColumnTypeDescription
customer_idPKINTUnique customer account identifier
customer_nameVARCHAR(100)Customer display name
segmentVARCHAR(40)Customer segment
account_statusVARCHAR(20)Current account status
Tablesorderscustomer_accounts
Interviewer

Whenever you're ready, walk me through your approach or go straight to the code. The requirements and the two tables are in the Question tab.

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.