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
BigQuery Query Optimization for Revenue Aggregation
00:00
5 left

BigQuery Query Optimization for Revenue Aggregation

MediumSQL · PostgreSQL

Problem

Can you explain your approach to optimizing queries within the BigQuery environment?

For this practical exercise, write a PostgreSQL query that returns customer revenue from qualifying 2025 orders. Apply a performance-conscious approach by limiting data to the required period and status before producing the final customer-level results.

Output

  1. One row per customer with at least 100.00 in qualifying revenue.
  2. Columns: customer_id, customer_name, region, total_revenue, and completed_orders.
  3. Sort by total_revenue descending, then customer_id ascending.

Output details

  • Restrict order dates to >= DATE '2025-01-01' and < DATE '2026-01-01'.
  • Include only orders whose status equals completed.
  • Include only order items with quantity greater than 0.
  • Calculate revenue as quantity * unit_price for each qualifying order item.
  • Count each qualifying order once in completed_orders, regardless of its number of items.

Schema

customers
ColumnTypeDescription
customer_idPKINTUnique customer identifier
customer_nameVARCHAR(100)Customer display name
regionVARCHAR(50)Customer state or territory
orders
ColumnTypeDescription
order_idPKINTUnique order identifier
customer_idINTCustomer who placed the order
order_dateDATEOrder placement date
statusVARCHAR(20)Order processing status
order_items
ColumnTypeDescription
order_item_idPKINTUnique order-line identifier
order_idINTOrder containing the item
product_nameVARCHAR(120)Product description
quantityINTUnits ordered
unit_priceNUMERIC(10,2)Price per unit
Tablescustomersordersorder_items
Interviewer

Whenever you're ready, walk me through your approach or go straight to the code. The requirements and the three 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.