LinkedIn profile: headline, about and projects
30 min · Beginner
Need help? Ask a tutor on WhatsApp (opens in a new tab)A recruiter opens your resume, then your LinkedIn within minutes. If the headline is vague or the titles differ, trust drops before the interview even starts.
Headline formula with examples
A headline is the line under your name on LinkedIn. It shows in search results, comments and connection requests, so it should name your target role, key skills and one proof or status.
By default LinkedIn may fill the headline with "Student at ABC College", which tells a recruiter nothing. Here are weak headlines and strong ones.
Example 1 · Headlines: weak and strong
Student at ABC Institute of TechnologySeeking job opportunities | Hard-working | Passionate | FresherPython | C | C++ | SQL | HTML | CSS | JS | React | Node | AWS | ML | AIAspiring Python Developer | Python, SQL, MySQL | B.Tech CSE 2026 Python Developer (Fresher) | Built Online Store API with MySQL and 45 pytest tests | 350+ DSA problems Python Developer Intern at Pixel Apps | Python, SQL | Final-year CSE
What this code does
- Each strong headline names a target role, the main skills a recruiter searches for and one status or proof point.
- The weak ones are either empty of skills, full of adjectives, or a list of every technology, which signals no focus.
Example 2 · Checking headline and note lengths
HEADLINE_LIMIT = 220NOTE_LIMIT = 300VISIBLE = 70
def check_headline(headline): status = "TOO LONG" if len(headline) > HEADLINE_LIMIT else "ok" print(f"Headline length {len(headline)}/{HEADLINE_LIMIT} {status}") shown = headline[:VISIBLE] + "..." if len(headline) > VISIBLE else headline print(f'Seen in search: "{shown}"')
check_headline("Aspiring Python Developer | Python, SQL, MySQL, pytest | B.Tech CSE 2026 | Built Online Store API")note = ( "Hi Kavya, I am a final-year CSE student at ABC Institute (your alma mater). " "I saw your post about joining the backend team at Zeta. I am preparing for Python developer roles " "and would value one tip on how you prepared for the technical rounds. Thank you, Ananya")status = "TOO LONG" if len(note) > NOTE_LIMIT else "ok"print(f"Note length {len(note)}/{NOTE_LIMIT} {status}")Headline length 97/220 ok Seen in search: "Aspiring Python Developer | Python, SQL, MySQL, pytest | B.Tech CSE 20..." Note length 261/300 ok
What this code does
- The limits used (220 for the headline, 300 for a connection note) are LinkedIn's current limits and may change; check in the app if a text is cut off.
- The visible part is an approximation: on phones and in search results only the start of the headline shows, so the role and main skill must come first.
A strong fresher headline follows target role + key skills + proof or status: "Aspiring Python Developer | Python, SQL, MySQL | B.Tech CSE 2026". Keep it truthful and readable; the headline limit is currently 220 characters, but the first 60-80 are what most people see.
How to build it:
- Use words recruiters search for: Python, SQL, MySQL, Developer.
- Add one proof point if you have it: "Built Online Store API", "Hackathon finalist".
- Avoid: "Seeking opportunities", "Hard-working", emoji strings, titles you do not hold ("CEO of my startup" for a club page).
About-section template for a Python fresher
The About section is a short first-person summary on your LinkedIn profile: what you do and want, what you have built, what you are good at and how to reach you. Only its first lines show before "see more".
The About section follows a five-line template. Below is the template, then the same template filled in for a Python fresher.
Example 3 · About section template, filled in
[Line 1] What I do + what I want[Line 2] Proof: main project with tech and result[Line 3] Other evidence: internship, contests, hackathon, club[Line 4] Core strengths: DSA, DBMS, OS, testing habits[Line 5] How to reach meI am a final-year Computer Science student who builds Python projects with clean, tested code, and I am looking for a Python developer role from 2026. My main project, Online Store API, is a Python service for an online store with 20+ operations, customer and admin roles, MySQL storage and 45 automated pytest tests. The code and setup steps are on my GitHub. I interned at Pixel Apps, where I fixed 12 bugs in a Python attendance service and added pagination to large reports. I have solved 350+ data structure problems and was a finalist in our college 24-hour hackathon. I enjoy clean, tested code and explaining things simply; I ran Python workshops for 150+ juniors as coding club lead. Email: ananya.rao.dev@gmail.com | GitHub: github.com/ananya-rao
What this code does
- The first two lines carry the role, main skills and proof, because they are visible before "see more".
- It is in the first person and uses the same facts and numbers as the resume. Replace every fact with your own.
Write it like you speak in an interview, not like a resume: "I build backend services in Python and SQL." Aim for 3 to 5 short paragraphs or about 150 to 250 words, and put the most important lines first, because only the first two or three lines show before "see more".
Featured and Projects sections linked to GitHub
Featured is the area at the top of your LinkedIn profile where you pin a few items: your best GitHub repository, a project demo video, a blog post or a certificate that proves your work.
A Projects entry reuses the facts from your resume and links to the GitHub repository. Here is one for Online Store API.
Example 4 · A Projects entry linked to GitHub
Project name: Online Store API - orders and stock serviceDates: Jan 2026 - Apr 2026Skills: Python, MySQL, pytest, Git, GitHub ActionsLink: github.com/ananya-rao/online-store-apiFeatured: the repository link + a 2-minute demo videoOnline Store API - orders and stock service (Jan 2026 - Apr 2026) A Python service for products, categories, customers and orders. - 20+ operations with input validation and clear error messages - Customer and admin roles; passwords stored as salted hashes - 45 pytest tests run on GitHub Actions; MySQL storage with stock checks Skills: Python, MySQL, pytest, Git, GitHub Actions Repository: github.com/ananya-rao/online-store-api
What this code does
- The description reuses the resume bullets, so both tell the same story, and the skills are tagged so the project shows up in skill searches.
- A short demo video in Featured lets a recruiter see the project working without cloning the code.
The Projects section lists each project with a description, dates, skills and a link. Link every project to its GitHub repository (and a live demo if you have one). The repository must have a good README, because a recruiter who clicks will judge it in seconds. Add the same 2-3 projects as on your resume, described with the same facts.
Revise: Writing professional README files and using .gitignore (opens in a new tab) covers the README a recruiter sees after clicking your link.
Connecting with alumni and recruiters politely
A connection note is the short message (up to 300 characters) sent with a connection request. It says who you are, why you chose this person and makes one small, easy request.
A blank or pushy request is easy to ignore. Compare a poor message with a polite one, first to an alumna and then to a recruiter.
Example 5 · Connection messages: poor and polite
To an alumna (blank request or):"Hi mam pls refer me for any job in your company. I am fresher. Resume attached."To a recruiter:"Sir any openings?? Please check my profile."To an alumna (note, under 300 characters): "Hi Kavya, I am a final-year CSE student at ABC Institute, your alma mater. I saw you joined the backend team at Zeta. I am preparing for Python developer roles; could I ask one question about how you prepared for the technical rounds? Thank you, Ananya" To a recruiter (after applying): "Hello Mr. Menon, I applied for the Graduate Python Developer opening (job ID 4521) today. I have built a Python project with MySQL and 45 tests (link in my profile). I would be glad to share anything else you need. Regards, Ananya Rao"
What this code does
- The polite notes say who you are, why this person, and make one small, specific request. They use the person's name and no slang.
- Referral requests come later, after a real conversation and only for a specific opening you fit. Names, company and job ID here are examples.
A request with a note is more likely to be accepted than a blank one. Free accounts may have a monthly limit on notes. Never ask a stranger for a job or a referral in the first message. Ask a small question, such as how they prepared for a company's technical round. After they reply, thank them, and only later, if the conversation goes well, ask whether they would be comfortable referring you to a specific opening.
Who to approach and how:
- Alumni from your college are the most likely to reply; search "company + your college".
- Recruiters: follow their posts, apply through the official link, and message once with your fit for a specific opening.
- Do not send the same copy-paste message to 100 people or follow up more than once.
Keeping the profile consistent with the resume
Consistency means your resume, LinkedIn and GitHub tell the same story: the same degree, project names, dates and job titles. LinkedIn may add detail, but it must never contradict the resume.
This program compares resume and LinkedIn facts and lists the mismatches.
Example 6 · Resume and LinkedIn consistency check
resume = { "cgpa": "8.1/10", "degree": "B.Tech CSE, 2026", "internship": "Python Developer Intern, Pixel Apps, May-Jul 2025", "project1": "Online Store API - orders and stock service",}linkedin = { "cgpa": "8.3/10", "degree": "B.Tech CSE, 2026", "internship": "Software Engineer, Pixel Apps, May-Aug 2025", "project1": "Online Store API - orders and stock service",}
mismatches = 0for key in sorted(resume): if resume[key] != linkedin[key]: mismatches += 1 print(f'MISMATCH {key}: resume "{resume[key]}" vs LinkedIn "{linkedin[key]}"')print("Consistent" if mismatches == 0 else f"{mismatches} fields to fix today")MISMATCH cgpa: resume "8.1/10" vs LinkedIn "8.3/10" MISMATCH internship: resume "Python Developer Intern, Pixel Apps, May-Jul 2025" vs LinkedIn "Software Engineer, Pixel Apps, May-Aug 2025" 2 fields to fix today
What this code does
- The CGPA and the internship title and dates differ. A title upgraded from "Intern" to "Software Engineer" is the kind of mismatch that background checks catch.
- Fix the profile to match the true facts on the resume, and update both whenever a fact changes.
Recruiters often open LinkedIn after reading a resume, and mismatches look careless or dishonest. LinkedIn can hold more detail than the resume, such as extra projects, posts and recommendations, but it must never contradict it. Update all three on the same day whenever something changes.
Next step
Check your understanding
12 quick questions