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
SQL Join for Total Paid
00:00
5 left

SQL Join for Total Paid

EasySQL · PostgreSQL

Problem

Kabbage Business Insights needs a customer-level view of payments recorded for Kabbage Funding accounts. Using the funding_payments reporting table, write a PostgreSQL query that calculates the total amount successfully paid by each customer.

Requirements

  1. Include only rows where payment_status is paid.
  2. Exclude payments without a customer_id, group the remaining rows by customer, and return customers ordered from highest to lowest total paid.

Schema

funding_payments
ColumnTypeDescription
payment_idPKINTUnique payment identifier
customer_idINTKabbage customer identifier
amountNUMERIC(12,2)Payment amount
payment_statusVARCHAR(20)Current payment state
Tablesfunding_payments
Interviewer

Your question is SQL Join for Total Paid. 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.