One-page or two-page resume for data roles: a decision table
In this article (6 sections)
Related programme: the Data Science course (6 months; ₹1,30,000 (inclusive of GST) · EMI from ₹5,000/month).
For most data roles, use one page if you have under about five years of relevant experience, and consider two pages only when the second page contains evidence a hiring manager for that specific role would want, such as distinct projects, publications or deployed systems. The rule is not length but density: every line must earn its space.
The decision table
| Your situation | Pages | Why |
|---|---|---|
| Fresher or final-year student | 1 | Two or three projects and education fill a page; more is padding |
| 1-4 years in data | 1 | Recent roles and one or two projects fit; older detail can go |
| Switcher with 5+ years outside data | 1, sometimes 2 | Page one must carry the data story; page two only for relevant older work |
| 5-10 years in data, several distinct systems shipped | 2 | Reviewers want to see scope across roles |
| Research-heavy DS roles with publications | 2 | Publications list is expected and can run long |
| Senior or principal, 10+ years | 2 | Scope, leadership and system detail |
If you are between rows, choose one page and make the case for two only if a line audit (below) shows you cannot cut without losing real evidence.
What reviewers actually do with page two
A first read is often short. Page one gets the most attention, and page two is read only if page one convinced the reader. So page two is never the place for your best project. If you have two pages, the strongest evidence for the target role belongs on page one, regardless of chronology.
The line audit: cutting a 1.4-page draft to one page
Print the draft. For each line, answer three questions and give one point per yes:
- 1Does it relate to a requirement in the posting?
- 2Does it contain a specific tool, method, scale or result?
- 3Could you talk about it for two minutes?
Lines scoring 0 or 1 are candidates for cutting. A worked example for a fictional data scientist with three years' experience:
| Line | Relevant | Specific | Can discuss | Score | Action |
|---|---|---|---|---|---|
| Built churn model with survival analysis | Yes | Yes | Yes | 3 | Keep |
| Attended weekly team meetings | No | No | No | 0 | Cut |
| Created Excel reports for sales team (2021) | No | No | Yes | 1 | Cut |
| Proficient in MS Office | No | No | No | 0 | Cut |
| Reduced model scoring time by moving batch job to SQL | Yes | Yes | Yes | 3 | Keep |
| Hobbies: reading, travelling | No | No | Yes | 1 | Cut |
| Class X marks | No | No | No | 0 | Cut unless asked |
| Kaggle competition, top-half finish | Maybe | Yes | Yes | 2 | Keep if space |
Cutting the zeros and ones recovered about 12 lines, which was the whole overflow.
Formatting changes that are not cheating
If the audit leaves you a few lines over, these are fair:
- Margins down to about 1.5-2 cm; smaller than that looks cramped when printed.
- Body font at 10-11 pt in a standard font. Below 10 pt becomes hard to read.
- Merge a short skills section into one or two grouped lines.
- Remove the "References available on request" line; it is assumed.
Not fair: shrinking to 8 pt, removing all white space, or pushing text into a second column that breaks parsing (see the ATS myths guide).
If you go to two pages
- Put your name and a page number on page two, in the body text rather than only in the header, so a separated printout is identifiable.
- Fill at least half of page two. A single orphaned section on an otherwise empty page looks like a formatting accident.
- Order by relevance within each section. Your strongest work stays on page one.
Keep a long version anyway
Maintain a master resume of any length with every project and bullet, then produce the one- or two-page version per application. This is the approach used in our worked example of tailoring a resume line by line, and it makes the page decision a matter of selection rather than rewriting.
For data science applicants still building the projects that belong on page one, the Data Science programme produces evaluated, written-up project work of the kind that survives this audit.
Pankit Kumar has 10 years in Data Science & AI, building and shipping production systems in regulated pharma and clinical environments. He is a freelance trainer at Boston Institute of Analytics, AnalytixLabs and Scaler, and has taught this material to thousands of working professionals.
This article is part of our Data Science programme — 6 months. From data foundations to machine learning, deep learning and deployment.
Explore Data Science