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
Advanced SQL for Fraud Metrics
00:00
5 left

Advanced SQL for Fraud Metrics

HardSQL · PostgreSQL

Problem

Tell me about a time you worked on SQL questions involving if-else logic, window functions, and fraud detection KPIs like recall and precision.

Use the provided transaction and fraud score data to calculate fraud KPIs for every available model threshold. Select the best threshold for each model using F1 score, with precision and recall as supporting metrics.

Output

  1. One row per model's best threshold.
  2. Columns: model_name, threshold, precision, recall, f1_score, and threshold_rank.
  3. Include only the top-ranked threshold per model, ordered by model_name.

Schema

transactions
ColumnTypeDescription
transaction_idPKINTUnique transaction identifier
customer_idINTCustomer associated with the transaction
transaction_amountDECIMAL(12,2)Transaction amount
actual_fraudBOOLEANConfirmed fraud label; NULL means not labeled
fraud_scores
ColumnTypeDescription
score_idPKINTUnique model score identifier
transaction_idINTTransaction scored by the model
model_nameVARCHAR(50)Fraud model name
fraud_scoreDECIMAL(4,2)Model fraud probability score
Tablestransactionsfraud_scores
Interviewer

Your question is Advanced SQL for Fraud Metrics. 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.