Data Analyst Resume: Rewrite Yours Line by Line, With Before and After Examples

By the end of this session you will have a rewritten summary, a skills section grouped by task, at least three rewritten bullets, one project entry and a version of your resume matched to one job posting. It takes about two hours. Keep a real posting open the whole time, because several steps ask you to check your wording against it. Work in a copy of your current resume so you can compare the old and new versions when you finish.

Step 1: Write a summary that says what your analysis is for

Instead of describing personality traits, use your summary to state three facts: what data you work with, which tools you use on it and who acts on what you produce. Write two sentences that answer all three. If you came to analytics from support, sales, operations or engineering, name that field, so the reader can see which business questions you already understand.

Before: "Detail-oriented, data-driven professional with strong analytical skills and a passion for turning data into actionable insights."

After: "Data analyst working in SQL, Python and Tableau on product and billing data at a B2B software company. I build the weekly retention dashboards and ad hoc analyses that product and finance use to set pricing and roadmap priorities."

Only one person could have written the after version. If your summary would fit on anyone's resume, keep editing. If you are changing careers, writing a CV for a career change shows how to describe the work you did before analytics.

Step 2: Group your skills by what you do with them

When every tool you have ever opened sits in one long list, the reader can't tell which ones you use every day. Sort your skills into three or four lines by task: getting data, analyzing it, presenting it and the methods you apply. In each line, put the posting's required tools first. Cut anything you couldn't talk about for five minutes in an interview. Move soft skills into your bullets, where you can show them in action. If you're unsure what belongs in each group, O*NET OnLine has detailed descriptions of more than 900 occupations, and its Software Skills search finds occupations that use specific programs and applications for work tasks.

• Before: "Skills: Excel, SQL, Python, R, Tableau, Power BI, Looker, Jira, Agile, Communication, Teamwork, Machine Learning"
• After: "Querying and modeling: SQL (Snowflake, PostgreSQL), dbt. Analysis: Python (pandas), Excel. Reporting: Tableau, Looker. Methods: cohort analysis, A/B test readouts."

Step 3: Rewrite each bullet as question, method and result

Each experience bullet should answer three questions. What was the business question? What did you do, with which data and tools? What happened because of it? If you have no number, name the decision your work informed. A decision someone made is a result. Writing resume bullet points that get read covers this structure in more depth.

• Before: "Responsible for creating dashboards and reports for stakeholders."
• After: "Built a churn dashboard in Looker from Snowflake billing data that the customer success team uses each Monday to pick which 5 at-risk accounts to call first."
• Before: "Performed data cleaning and analysis using Python."
• After: "Wrote a Python script that removes duplicate trial signups across two CRMs, cutting manual cleanup for the weekly funnel report from about 4 hours to under 1."

Use only figures you can defend in an interview. If a time saving was an estimate, write "about" and be ready to explain how you measured it.

Step 4: Show one project from question to finding

If none of your job titles say analyst, a project section has to prove you can do the work. A reviewer learns more from one fully described project than from a list of course names or certificates. In two or three lines, state the question, the data source, what you did and what you found or recommended.

Before: "Capstone project: Analyzed e-commerce dataset using SQL and Tableau."

After: "Support ticket analysis (personal project): Pulled 6 months of public issue data from an open-source project through the GitHub API, sorted issues into categories with Python and found that installation problems were the largest category. Published a Tableau Public dashboard and a 1-page recommendation for a setup checklist."

Link to the repository or dashboard only if it is tidy and has a short README. A reviewer who clicks through should find the same story, told in the same order.

Step 5: Match your wording to one posting

Pick one real posting and underline its required tools and phrases. Where your experience truly matches, use their words. If they say "product analytics" and you wrote "business intelligence," switch to their term. The guide to tailoring a resume to a job description walks through this for each application.

For example, say the posting asks for product analytics, Amplitude and experimentation, and you have done all three.

• Before: "Experience with BI tools and stakeholder reporting."
• After: "Product analytics in Looker and Amplitude: defined activation metrics with the product team, ran experimentation readouts for 3 onboarding tests and reported feature adoption weekly."

As you edit, keep the layout easy for software to read: one column, standard section headings and no text inside images or charts. ATS-friendly resume formatting lists the layout choices that break parsing.

Check your work

• Does your summary name your tools, the data you work with and who uses your output?
• Does every tool in your skills section show up in at least one bullet or in your project?
• Do at least half of your bullets end in a number, a decision or a changed process?
• Would a reviewer understand your project from its entry alone, without clicking the link?
• Do the posting's required tools appear in your bullets, written the way the posting writes them?

Frequently asked questions

Sources

• U.S. Bureau of Labor Statistics, Occupational Outlook Handbook
• O*NET OnLine, occupation tasks and technology skills
• CareerOneStop, salary and career information