LinkedIn headline and About section for data analysts: worked drafts

LinkedIn is different from a job portal in one way that matters: people read your profile after meeting you, seeing your comment, or receiving your message. So it has to work for search and for a human who is deciding whether to reply.

Three headline formulas and when to use each

Some rules apply to all three:

• Put the searchable nouns early. The start of the headline appears beside your name in comments and search results, and the rest may be truncated.
• Use the words recruiters type: "Data Analyst", "Business Analyst", "Power BI", "SQL". Creative titles like "Data Storyteller" are not what anyone searches.
• Avoid "Open to work" in the headline. LinkedIn has a separate setting for that, and you can choose whether it is visible to all members or only to recruiters.
• Do not claim a title you have not held. "Data Analyst" is fine if you are doing the work in your current job or have trained for it and label it "Aspiring" or "Trainee"; it is not fine to imply an employer gave you that designation when they did not.

Draft the About section in four blocks

LinkedIn shows only the opening lines of your About section before a "see more" link, so the first two sentences must carry the message.

Block 1, the opening claim. What you do, for whom, with what.

Block 2, the evidence. One or two specific pieces of work with a number that is true and a method.

Block 3, the tools list. A plain line that doubles as keywords.

Block 4, the ask. What you are looking for, and how to reach you.

Here is a filled example for a fictional analyst, Arjun, who works in a Noida logistics firm's MIS team.

I turn warehouse and delivery data into decisions that operations managers can act
on the same day. For the last two years I have owned the daily MIS for a regional
logistics team: 14 hubs, one report, and a lot of manual Excel.

Two pieces of work I am proud of:
- Rebuilt the daily hub report as SQL views feeding a Power BI dashboard, which cut
  preparation from about two hours to twenty minutes each morning.
- Found that most "late delivery" flags came from one hub recording scan times in
  the wrong time zone. Fixing the source removed a false problem from weekly reviews.

Tools: SQL (MySQL, SQL Server), Power BI and DAX, Advanced Excel, Power Query,
basic Python (pandas).

I am looking for data analyst roles in supply chain or e-commerce in Delhi NCR or
remote. Message me here or email arjun.example@email.com.

Why each line is there:

• "Same day" and "operations managers" tell a reader who the audience of the work is.
• "About two hours to twenty minutes" is a claim Arjun can explain in detail. Use your own real numbers; if you do not have one, describe the change qualitatively rather than inventing a percentage.
• The time-zone example is a small, specific story. It shows data-quality instinct, which is harder to fake than a tool list.
• The final line removes friction. Many people forget to say what they want.

A fresher version, with the same four blocks

I am a data analyst trainee who likes finding the question behind a messy
spreadsheet. I have a B.Sc. in Mathematics and have spent the last four months
building analysis projects in SQL and Power BI.

My most complete project analyses 50,000 synthetic food-delivery orders: I wrote
SQL for delivery-time percentiles by area, built a Power BI report, and wrote up
three recommendations with their limitations. The data is synthetic, and the
README explains how I generated it.

Tools: SQL, Excel (pivots, XLOOKUP, Power Query), Power BI, Python basics.

Looking for entry-level data analyst or MIS roles in Noida, Delhi or Gurugram, or
remote. Repository link is in Featured.

Saying "synthetic" up front protects you. An interviewer who discovers it later assumes you were hiding it.

Use Featured and Experience to back up the headline

• Featured: pin the project repository or a short write-up. One strong item beats five weak ones.
• Experience: each role should have two or three lines showing data work. For non-data roles, write what data you touched, as described in our guide on LinkedIn for career switchers.
• Skills: add the same tools that appear in your headline and About section, so the profile tells one consistent story.

Test the profile with two readers

Ask one person who works in data and one who does not to read only your headline and the visible opening lines of About for ten seconds, then tell you what job you want. If either gets it wrong, rewrite the first sentence. Then check your resume against the same target role using the free skill check, so profile and resume make the same claims.

If your tools list is still thin, the Data Analyst programme is built around project work in SQL, Excel and Power BI that you can pin in Featured.