Skip to content
JobreachGet started

How to cold email for a data analyst job

Data analyst posts list tools, but the person hiring wants to know whether you can turn a messy question into an answer someone acts on. Lead with one analysis: the question, the data, the tool, and what changed because of it.

Updated

What data analyst posts ask for

The titles vary (data analyst, business analyst, MIS analyst, product analyst), but the posts ask for much the same things:

  • SQL, usually named first: joins, group by and, for many roles, window functions.
  • Excel or Google Sheets at a working level: pivot tables, lookups and cleaning data.
  • A dashboard tool, most often Power BI or Tableau, sometimes Looker Studio or Metabase.
  • Python with pandas for some roles, especially at tech companies.
  • Basic statistics: averages that mislead, cohorts and, for product roles, A/B tests.
  • “Business understanding” and “stakeholder communication”: explaining a number to someone who isn’t an analyst.
  • Often a domain, such as e-commerce, fintech, logistics or healthcare. Knowing the domain can matter more than one more tool.

Your proof as a fresher

As a fresher, the strongest proof is an analysis that looks like work, not like an exercise:

  • A project on a real, messy public dataset (government open data, a city’s transport data, real e-commerce orders), with the SQL on GitHub and the dashboard published online.
  • An internship where someone used your report: who used it, and for what.
  • A case competition or analytics hackathon: what you recommended and how it placed.
  • A college project with a real stakeholder: a fest’s ticket sales, a canteen’s orders, a department’s results.

Write each one as question, method, finding. “Built a sales dashboard” says little; “found which three stores caused most of the late deliveries” says what you can do.

Your proof if you are switching in

Switching from operations, sales, finance, support or HR? You have probably been doing analyst work already, in Excel and under another title. Lead with that:

  • The MIS report or tracker you built and own: who reads it, how often, and what decision it feeds.
  • A manual report you automated, with the hours it saves each week.
  • A finding of yours that changed something: a process, a target, a vendor, a staffing plan.
  • Then the new skills on top: the SQL or Power BI you have learned, shown on your own work (with the data anonymised) or on a public dataset.

Your domain is an advantage. Someone from operations applying to a logistics company’s analyst role already knows what the numbers mean; say so.

Your proof in two sentences

Sentence one: the question, and the data (how much, from where). Sentence two: the tool, what you found, and what someone did with it.

Fresher

Using two years of a city’s public bus ridership data, I cleaned and joined the trip tables in SQL and built a Power BI dashboard of load by route and hour. It showed four routes running nearly empty at midday and overflowing at 9 AM, and I wrote up a timetable change for them.

Switching from sales

As a sales coordinator I built the weekly pipeline sheet our twelve-person team reviews every Monday, from our CRM export, with pivot tables and lookups. It showed that leads called on their first day closed far more often, and the team now calls every new lead the same day.

Both are made-up examples. The numbers in yours must be your own, and ones you can explain in an interview.

An example email

Meera, an analytics lead at a quick-commerce startup, posts for a data analyst with 1 to 3 years, SQL and Power BI, and asks for resumes by email. Pooja has three years in operations at a logistics company. This is the whole email.

To
meera@zipcart.example
Subject
Data Analyst (SQL, Power BI): Pooja Nair, 3 years in operations

Hi Meera,

I saw your post for the Data Analyst role at Zipcart. I have spent three years in operations at a logistics company, where most of my work has become analysis: I build the reports our city managers run their day on.

I moved our daily delivery report from a manual Excel sheet to a SQL query that feeds a Power BI dashboard for 40 delivery hubs. It saves the team about six hours a week, and it showed that two hubs caused most of our late deliveries, which led to new shift timings there.

Quick commerce runs on the same numbers I work with every day, which is why your post caught my eye. My resume is attached, and I’d be glad to walk you through the dashboard on a short call.

Pooja Nair
+91 98xxx xxxxx
linkedin.com/in/poojanair-example

A made-up example: Pooja, Meera and Zipcart are fictional. Every claim in the email comes from Pooja’s own resume.

What makes it work:

  • It treats three years in operations as analysis experience, which it is, instead of apologising for the title.
  • One finding with a consequence (new shift timings), not a list of tools.
  • The two tools the post names, SQL and Power BI, appear inside the proof itself.
  • The ask is to see the dashboard: the easiest next step for an analytics lead.

The subject line

The role, the two tools the post names first, your name and your stage.

  • Data Analyst (SQL, Power BI): Pooja Nair, 3 years in operations
  • Data Analyst Intern: Kabir Mehta, B.Com 2026, SQL and Tableau
  • Business Analyst: Farah Khan, MBA 2026, ex-sales operations

Avoid subjects like “Job application” or “Resume”. The person who posted may have several openings, and the role first tells them which one.

Mistakes to avoid

  • Every tool you have touched: Excel, SQL, Python, R, Tableau, Power BI, SAS, SPSS. Name the two or three the post asks for, and show them in use.
  • The Titanic, Iris or IPL dataset as your lead project. Reviewers have seen them many times; a messier dataset with a real question stands out.
  • A dashboard screenshot with no finding. Say what the dashboard told you.
  • Calling yourself a data scientist for an analyst role, or the other way round. Use the post’s title.
  • A certificate as your first line. The course belongs on the resume; your analysis belongs in the email.
  • Your current employer’s internal numbers in a public portfolio. Anonymise them, or use a public dataset.

And the ones that hurt in every role: a guessed address, a generic resume, and an email longer than a phone screen. More in how to email a recruiter about a LinkedIn hiring post.

Where data analyst posts appear

  • LinkedIn posts by analytics managers and founders at fintech, e-commerce, quick-commerce and D2C startups.
  • Other titles for the same work: business analyst, MIS analyst or executive, product analyst, reporting analyst.
  • Company job boards on Greenhouse, Lever and Ashby, where analyst roles sit under data, business or operations teams.
  • If you are switching, your own company. A move into its analytics team is often the shortest path.

A LinkedIn post search to start from (search Posts, sorted by Latest):

Analyst posts for freshers

("data analyst" OR "business analyst" OR MIS) ("share your resume" OR "send your resume") fresher

3 of 5 ORs and ANDs

Switching with a few years behind you? Drop fresher, and add your city: (Pune OR Mumbai) uses one more OR. LinkedIn finds nothing at all once a search has more than five ORs and ANDs: see how to find hiring posts on LinkedIn. If there is no reply in about a week, follow up once.

Guides for other roles

All of them, with what to lead with for each: cold email by role.