A data scientist CV has a specific failure mode: it reads like a tech stack with a name attached. Python, SQL, TensorFlow, XGBoost, Spark, a dozen tools, and almost nothing about what any of them produced. Hiring managers for data roles have seen a thousand of those. What they're actually scanning for is whether you can turn data into a decision someone acted on.
Here's how to build a CV that answers that question.
Lead with outcomes, not models
The trap is describing the technique and stopping there. "Built a random forest model to predict customer churn" tells the reader what you did, not whether it mattered. The model is the means. The outcome is the point.
Rewrite every bullet so the business result is the subject. "Cut monthly churn 14% by deploying a churn model that flagged at-risk accounts for the retention team" leads with the number a VP cares about, then earns credibility by naming the method. The model is still there. It's just no longer pretending to be the achievement.
If a project never shipped or never changed a decision, it's a weaker bullet, and that's worth being honest with yourself about. A deployed model that moved a metric beats three notebooks that impressed nobody outside your team.
Quantify like a data person
You of all people should put numbers on your work, and the right numbers. Two kinds matter:
Business metrics: revenue, cost, churn, conversion, retention, hours saved. These are what non-technical decision-makers read.
Model and scale metrics: accuracy, precision/recall or AUC where it's meaningful, dataset size, latency, the number of models in production. These prove technical depth to the people who'll review your work.
Pair them when you can. "Improved fraud-detection recall from 0.71 to 0.88, reducing chargebacks by roughly $400k a year" speaks to both audiences in one line, the engineer and the executive.
Structure the CV for a fast scan
A strong layout for a data scientist:
- A two-line summary naming your domain (you're not just "a data scientist", you're a data scientist in fraud, or healthcare, or growth) and your strongest result.
- Experience, with outcome-led bullets as above.
- A projects section if your experience is thin, but only projects that reached a conclusion, not tutorials.
- A skills section, grouped, not a flat dump.
Group skills so they're readable: languages (Python, SQL), ML (scikit-learn, PyTorch), data tooling (Spark, dbt, Airflow), cloud (AWS, GCP). A grouped list lets a reviewer find what they need in a second; an alphabet soup of forty tools just signals you've touched a lot of things shallowly.
Keep it parseable
Data roles run through applicant tracking systems like any other, and a clever multi-column layout often parses into garbage. Use a single-column structure, standard section headings, and put your tools as plain text rather than inside a graphic skill-bar, because the parser can't read a picture of "Python: 90%". The same formatting discipline that keeps any CV ATS-readable applies here, and it matters more for data roles because so many candidates over-design their CVs.
Recruiters for data roles don't reward the longest tool list. They reward the clearest line from your work to a number the business moved. Write for that line.
Show the part of the job that isn't modeling
Real data work is mostly not modeling. It's defining the question, cleaning the data nobody wanted to clean, and convincing a stakeholder to trust the result. A CV that shows only modeling reads as junior, because senior data scientists know the model is the easy part.
Work in a bullet or two about scoping a problem with a business owner, building a data pipeline that others now rely on, or presenting findings that changed a roadmap. That communication and judgment is often what separates the candidate who gets hired from the one with marginally better Kaggle scores.
When you pull a CV together from your LinkedIn and project history, a tool like Postulit gives you the structure quickly, but the impact framing is yours to write. Go through each role and ask: what decision did my work change, and by how much? The CV that answers that, in plain numbers, is the one that gets the call.