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

Tune Lead Scoring Bias-Variance

MediumMachine Learning00:00
Practice interviewer
In session
5 left
00:00

Whenever you're ready, walk me through how you'd approach this.

You need to log in / sign up to chat or submit.

Problem

Business Context

Salesforce wants to improve lead prioritization in Sales Cloud by predicting whether a newly created B2B lead will convert to an opportunity within 30 days. The sales operations team needs a model that generalizes well across regions and campaign types, not one that only fits historical noise.

Dataset

You are given a historical lead-conversion dataset extracted from Sales Cloud and Marketing Cloud engagement logs.

Feature GroupCountExamples
Lead attributes10industry, employee_count, country, lead_source, annual_revenue
Engagement features8email_opens_7d, form_submits_30d, web_visits_14d, campaign_click_rate
Sales activity6call_attempts_7d, email_touches_14d, days_to_first_contact
Derived behavioral features6engagement_trend_14d, touches_per_day, recency_score
  • Size: 240K leads over 18 months, 30 features
  • Target: Binary, converted to opportunity within 30 days
  • Class balance: 18% positive, 82% negative
  • Missing data: 12% missing in revenue/company fields, 6% missing in engagement fields for net-new leads

Success Criteria

A good solution should demonstrate the bias-variance tradeoff in practice by comparing at least one high-bias model and one high-variance model, then selecting a balanced approach that performs best on unseen data. Target performance is AUC-ROC >= 0.82, PR-AUC >= 0.50, and less than 3 percentage points gap between validation and test AUC-ROC.

Constraints

  • Predictions run in nightly batch scoring for ~500K active leads
  • Sales leadership wants interpretable drivers for why a lead is high priority
  • Retraining should be feasible monthly without expensive infrastructure

Deliverables

  1. Train and compare models that illustrate underfitting vs overfitting
  2. Explain the bias-variance tradeoff using train, validation, and test results
  3. Show how regularization, model complexity, and cross-validation affect generalization
  4. Recommend a final model for Sales Cloud deployment
  5. Provide evaluation metrics and feature importance or coefficient-based interpretation