Data Analyst Job Application Email: 4 Samples and What to Highlight

The 4 samples

Each one is under 200 words, names the posting's tools, and carries one project in two lines. Names, companies and figures are made up; the shape is what to copy.

Sample 1: Fresher with a portfolio (SQL, Excel, Tableau)

Subject: Junior Data Analyst — Pooja Agarwal | SQL, Excel, Tableau

Hello Ms. Sharma,

I'm applying for the Junior Data Analyst role at Saffron Retail (Job ID DA-0931) that I saw on your careers page. I completed my B.Sc in Statistics from a college in Jaipur in June 2026, and I've spent the last year building a small portfolio in SQL, Excel and Tableau, which are the three tools the posting lists.

The project closest to your work: I analysed a public online-retail dataset of about 50,000 orders in SQL and built a Tableau reorder view by SKU and month. The finding was that 18% of SKUs produced 71% of revenue, and the dashboard turns that into a weekly reorder list with a stock-out flag. The dashboard is on Tableau Public (link below) and the SQL is on GitHub with a short write-up. In Excel I'm comfortable with pivots, XLOOKUP and Power Query, and I completed the Google Data Analytics certificate in March.

I can join immediately and I'm based in Jaipur, open to relocating to Gurugram. My résumé is attached as a PDF. I'd be glad to walk you through the dashboard on a call.

Thank you,
Pooja Agarwal
+91 98765 43210
public.tableau.com/app/profile/poojaagarwal

What to change: the job ID and where you found it, your degree and year, the three tools (only the ones the posting names and you have used), the project's two lines (data and tool; finding and number), the Excel specifics, the certificate if you have one, your city, and the portfolio link.

Hinglish mein: Data analyst ki mail mein sabse pehle tools likhein jo posting mein hain aur jo aapne sach mein use kiye hain — SQL lagbhag hamesha pehle. Phir ek project do line mein: pehli line mein kaunsa data aur kaunsa tool, doosri line mein kya pata chala aur number kya tha. Dashboard ka link dein jo bina login khule; .pbix ya Excel file kabhi attach mat karein. Resume ek page ka PDF, apne naam se.

Sample 2: Career switcher (accounts or MIS to data analyst)

Subject: Junior Data Analyst — Nikhil Gupta | 3 yrs MIS, Power BI

Hello Mr. Verma,

I'm applying for the Junior Data Analyst role at Brightwave Technologies. I'll say the switch up front: I've spent three years in the accounts and MIS team at a textile firm in Surat, and for the last year most of my work has been analysis rather than accounting, which is why I'm moving.

In that year I replaced the fourteen monthly Excel reports our management received with one Power BI dashboard, fed by Power Query from our ERP exports, which cut month-end reporting from three days to a morning. I learned SQL on the way, first through a course and then on our SQL Server with the IT team's help; the dashboard's refresh now runs off six queries I wrote. The one finding that mattered: dyeing-unit downtime was costing us about 9% of monthly output, which the plant head had assumed was closer to 3%.

I'm based in Surat and open to Ahmedabad or remote, with a 30-day notice period. My résumé is attached, and the link below has screenshots of the dashboard with the numbers masked.

Thank you,
Nikhil Gupta
+91 91234 56780

What to change: your current field and why you are moving (one honest sentence), the analysis you already did in the old job with its before-and-after, how you learned SQL and what you have run it on, the one finding with a number, and the masked screenshots link. Apply to junior or associate roles where your domain knowledge is an asset, and say so if the company is in your old industry.

Sample 3: Two to three years of experience

Subject: Data Analyst — Ankita Roy | 2.5 yrs SQL, Python, Looker

Hello Ms. Nair,

I'm applying for the Data Analyst role on the growth team at Veda Learning (GA-118). I'm an analyst with two and a half years at an ed-tech in Pune, working mostly in SQL on BigQuery, Python with pandas, and Looker Studio.

The posting asks for retention analysis and self-serve dashboards, which is my current work. I built the retention and cohort dashboard our product team uses every Monday, and the analysis behind it found that students who finished two live classes in their first week retained at roughly twice the rate of those who finished one, which turned into the onboarding nudge the team shipped in June. I also moved our weekly reporting from hand-built sheets to scheduled queries, which cut the preparation time from about two days to two hours and removed the copy-paste errors we used to find on Tuesdays.

My notice period is 30 days. I'm in Pune and open to hybrid in Bengaluru. My résumé is attached; I'd be glad to walk through the cohort analysis on a call.

Best regards,
Ankita Roy
+91 98765 43210
linkedin.com/in/ankitaroy

What to change: the job ID, your stack line in the posting's words, the one analysis with a finding and the decision it led to, the second proof (automation, time saved, errors removed), the notice period and city. With experience, the finding and the decision it caused matter more than the tool list.

Sample 4: Internship

Subject: Data Analyst Intern (6 months) — Ishaan Verma, B.Tech 2027

Hello Mr. Pillai,

I'm applying for the six-month Data Analyst internship at Trident Logistics starting January 2027, which I found through my college placement cell. I'm in the final year of B.Tech in Nagpur, and I can work full time from January to June.

For a course project I took the public bus-route and ridership data for our city (about 1.2 lakh trips) and used Python and SQL to find the twelve routes where buses ran under 30% full after 8 pm; a two-page summary went to a student committee that works with the transport office. On the side, I keep a Kaggle notebook on an e-commerce dataset where I practise SQL joins and pandas groupbys, and I'm comfortable with Excel pivots and Power BI basics.

I'm in Nagpur and can relocate to your Mumbai office for the internship. My résumé is attached as a PDF, and both projects are linked below. I'd welcome a short call.

Thank you,
Ishaan Verma
+91 91234 56780
github.com/ishaanverma

What to change: where you found it, your dates, the one project on real or public data with a number, the practice work (be honest that it is practice), the tools, and the links. For an internship, showing that you finish things matters more than scale.

What to highlight

Analyst emails are read by a hiring manager who has one question: can this person take a messy table and come back with something I can act on? Four things answer it.

Tools, in the posting's words. SQL first, almost always. Then Excel with specifics (pivots, XLOOKUP, Power Query), then one BI tool (Power BI or Tableau; Looker Studio for smaller teams). Python or R only if the posting asks or you have really used it. Do not pad the list with Hadoop, Spark or SAS from a syllabus.

One project in two lines. This is the heart of the email, and the formula is simple:

• Line one: what data (how much, from where), what you built, with which tool.
• Line two: the finding, with a number, and what changed because of it.

Three examples at different levels:

• "Analysed about 50,000 retail orders in SQL and built a Tableau reorder view by SKU. Found that 18% of SKUs produced 71% of revenue, which became the weekly reorder list."
• "Replaced fourteen monthly Excel reports with one Power BI dashboard fed by Power Query. Month-end reporting went from three days to a morning, and it surfaced a 9% downtime loss nobody had measured."
• "Built the cohort retention dashboard in Looker Studio off BigQuery. Students finishing two live classes in week one retained at about twice the rate, which became the onboarding nudge shipped in June."

The business question. Each example starts from a question someone needed answered. A project that starts from a dataset and ends with a chart is a tutorial; a project that starts from a question and ends with a decision is analysis.

Plain communication. One sentence that shows you can explain a finding to a non-technical person, such as "the two-page summary went to the transport committee." Managers hire analysts to be understood.

Your degree, certificates and CGPA go in the last paragraph or the résumé. A Google or IBM certificate is a fine supporting line; it is not the project.

Subject lines for analyst roles

All under 60 characters: the role, your name, the tools or years as the hook.

• Junior Data Analyst — Pooja Agarwal | SQL, Excel, Tableau
• Data Analyst — Ankita Roy | 2.5 yrs SQL, Python, Looker
• Junior Data Analyst — Nikhil Gupta | 3 yrs MIS, Power BI
• Data Analyst Intern (6 months) — Ishaan Verma, B.Tech 2027
• Business Analyst (Job ID BA-2271) — Rohan Deshmukh
• Re: Data Analyst — Pooja Agarwal | Portfolio link added

More patterns, with the rules behind them, in 50 job application email subject lines.

Attachments, file names and timing

• The résumé: one PDF, one page for freshers, named Pooja-Agarwal-Resume-Data-Analyst.pdf. Run it once through the free ATS résumé checker to catch tool keywords you forgot; analyst postings are filtered on them more than most.
• The portfolio: a link, not a file. Tableau Public, a Power BI publish-to-web link, a GitHub repo with a README, or a Google Drive folder set to anyone with the link can view. If a link is impossible, a two or three page PDF of dashboard screenshots with one caption each.
• Never attach: .pbix, .twbx, .xlsx or .csv files, the dataset, a Jupyter notebook export, or a project report over three pages. They need software to open, they trip security filters, and nobody opens them.
• Mask client data in any screenshot from a real job: blur the numbers, keep the structure.
• Timing: a weekday morning. Reply to a recruiter's screening questions within a day; many analyst roles send a short SQL or Excel test first, and a prompt reply moves you up the list.
• Follow up once after 7 to 10 days, on the same thread, and add the portfolio link again in that follow-up; it is the thing they are most likely to click on the second read.

Mistakes that get analyst emails ignored

• Fifteen tools, no project. The tool list is a claim; the project is the proof.
• "Proficient in Excel" with no specifics. Say pivots, XLOOKUP, Power Query, or say nothing.
• A tutorial dataset presented as client work. Public data is fine and expected for freshers; just say it is public.
• No number anywhere. An analyst email without a figure in it is a contradiction.
• Attaching the .pbix file or a 40 MB Excel workbook.
• Skipping SQL because you did everything in Excel. Learn enough SQL to write joins and group-bys before you apply; most screens test it.
• Mixing up the role. Describing machine-learning ambitions in a data analyst application tells the manager you want a different job.
• Hiding a career switch. Say it in the first line and let the MIS work prove you were already analysing.
• A Tableau Public link that goes to an empty profile because you forgot to publish.
• The whole project in six paragraphs. Two lines in the email; the write-up lives at the link.

If you are a fresher applying to many roles, the fuller set of first-job emails is in job application email for freshers, and the cover letter generator will draft a version from your résumé that you can cut down to the two-line formula.

Where Hireoo fits

Hireoo is an AI job agent for India. You describe the role you want in one sentence, in English or Hinglish, for example "junior data analyst, SQL and Power BI, Jaipur or remote"; it finds fresh hiring posts from across the web, matches them to your résumé with a fit percentage and reasons, writes a tailored application email for each one, and sends it from your own Gmail with send-only access. You review the email before anything goes out, or let it auto-apply to the results you pick. Starter is ₹0 with 10 job results a day. It does not send follow-ups or track replies; those stay with you, as does the portfolio. Start free.