Data Scientist resume example

Data Scientist resume example: 7 years in insurance and energy, a churn model retaining $3.1M of premium a year, an A/B framework and models in production.

Cover letter for this role

Wei Zhang

Senior Data Scientist | Pricing, Churn and Forecasting Models in Production

Seattle, WA7 years of experience

Summary

Senior Data Scientist with 7 years building predictive models for insurance and energy companies. Takes projects from framing the business question to deployed models with monitoring. Strong in Python, SQL, gradient boosting and experiment design, and known for explaining model trade-offs clearly to actuaries, product leads and regulators.

Experience

Senior Data ScientistApr 2022 - Present

Harborline Insurance

  • Built a renewal churn model (LightGBM, AUC 0.81) that targets retention offers; lapse rate among targeted policyholders fell 2.4 points, worth about $3.1M in retained premium a year.
  • Designed the A/B test framework the pricing team now uses for all rate changes, with 14 experiments run since 2023.
  • Worked with actuaries to add telematics features to the auto pricing model, improving loss ratio prediction by 9% on holdout data.
  • Moved 6 models from notebooks to scheduled pipelines on Databricks with drift monitoring.
  • Mentor 2 junior data scientists.
Data ScientistAug 2019 - Mar 2022

Cascade Energy Analytics

  • Forecast hourly electricity demand for 4 utility clients, with mean absolute percentage error of 3.2% day-ahead.
  • Built an anomaly detection model on smart-meter data that flagged 1,100 likely meter faults in its first year.
  • Presented model results to utility regulators in 3 rate case filings.

Skills

  • Python (pandas, scikit-learn, LightGBM)
  • SQL
  • Machine Learning
  • Experiment Design and A/B Testing
  • Time Series Forecasting
  • Databricks and Spark
  • MLflow
  • Model Monitoring
  • Causal Inference
  • Data Storytelling

Education

MS in Statistics, University of Washington, 2019; BS in Mathematics, University of California, Davis, 2017

Fictional candidates and employers. Any resemblance to a real person or company is coincidental.

Now for your own experience and a real posting

Jobiko writes a resume and a cover letter from what you have actually done, for the posting you choose, and shows you both before anything is sent.

Build my resume →

What hiring managers check first

Business impact, not just accuracy

A model's AUC matters less than what it changed. Tie your work to revenue, cost or risk in dollars or percentage points.

Models in production

Hiring managers want people who ship. Mention pipelines, monitoring and deployment, not only notebooks.

Experiment design

Knowing how to prove a model works through A/B tests or causal methods separates senior candidates from junior ones.

Communication with non-technical partners

Working with actuaries, regulators or product teams shows you can make your work useful.

Keywords the applicant tracking system matches

  • Data Scientist
  • Machine Learning
  • Python
  • SQL
  • Predictive Modeling
  • A/B Testing
  • Churn Modeling
  • Pricing
  • Forecasting
  • Databricks
  • Spark
  • MLOps
  • Statistics

Use the ones that are true of you, in the words the posting uses.

Mistakes to avoid

  1. Listing every algorithm

    Recruiters do not need a catalogue of methods. Show the few you used and why they fit the problem.

  2. Accuracy without context

    'Achieved 95% accuracy' can mean little on imbalanced data. Give the metric that fits the problem and the business result.

  3. No mention of data engineering

    Real projects involve messy data and pipelines. One bullet on how you got data ready shows practical experience.

Questions

Do I need a PhD to be a data scientist?
No. Many industry roles prefer a master's degree or strong experience. A PhD helps most for research-heavy positions.
How long should a data scientist resume be?
One page up to about 5 years of experience, two pages for senior roles with publications or many deployed projects.
Should I include Kaggle or personal projects?
Early in your career, yes. With several years of industry work, one line is enough unless a project is highly relevant.