LinkedIn for Engineers: The 6 Fields That Matter

Foundationseasy10 min
Ask Cairnly about this lesson
On this page

What you will learn

  • Optimize the 6 LinkedIn fields that recruiters actually filter by
  • Write a headline and About section that rank in recruiter search
  • Avoid the common cringe patterns that hurt Indian CS profiles

Why this matters

LinkedIn is how 80%+ of tech recruiters in India source candidates. When a Flipkart recruiter searches "React Node.js 2027 graduate Bangalore," your profile either shows up or it doesn't. The difference is usually 6 fields — not your post frequency, not your endorsements, not your connections count.

The 6 fields that drive recruiter search results

1. Headline (120 characters)

This is the single highest-impact field. It appears in search results, connection requests, and comments. Do not waste it on "Aspiring Software Engineer."

Formula: [Role you want] | [Top 2-3 skills] | [College] '[Grad year]

Examples:

  • SDE Intern @ Razorpay | React, Node.js, PostgreSQL | IIIT-H '27
  • Backend Engineer | Python, FastAPI, Redis | Building AI retrieval systems | VIT '27
  • CS Undergrad | Full-Stack + LLM Engineering | NIT Trichy '28

2. About section (first 3 lines are everything)

LinkedIn shows only the first 3 lines before "see more." Front-load:

text
I build full-stack web apps and AI pipelines. Currently an SDE intern
at [Company] working on [specific thing]. Graduating from [College]
in [Year] — looking for full-time SDE roles starting [Month].

Projects:
• [Project 1]: [one-line description] — github.com/you/repo
• [Project 2]: [one-line description] — github.com/you/repo

Tech I work with daily: Python, TypeScript, React, FastAPI, PostgreSQL

3. Experience section

Add internships, freelance work, open-source contributions, and teaching/TA roles. Each entry needs:

  • Company/org name (LinkedIn auto-links recognized companies)
  • Specific title (not just "Intern" — use "Backend Engineering Intern")
  • 2-3 bullet points with outcomes, not duties

4. Education

Add your college, degree, CGPA (if above 8.0), and relevant coursework only if it's unusual (e.g., "Graduate-level NLP" as an undergrad). Add clubs/positions only if they show leadership.

5. Skills section (recruiter filter)

LinkedIn recruiters filter by skills. Add your actual technical skills — the ones on your resume. Get endorsed for your top 3 by classmates. Skill endorsements affect search ranking more than most people realize.

Add these (if truthful): Python, JavaScript, React.js, Node.js, SQL, Git, Docker, REST APIs, Machine Learning

Do not add: "Problem Solving," "Team Player," "Quick Learner" — these are not searchable technical skills.

Pin 2-3 items:

  • A link to your best GitHub project
  • A link to a deployed project or demo video
  • A blog post or technical write-up (if you have one)

What NOT to do on LinkedIn

  • Do not post "Day X of #100DaysOfCode" — recruiters do not read these
  • Do not use "Open to Work" banner — mixed signal; use the private "Open to Work" setting instead
  • Do not list 15 certifications from free courses — one or two meaningful ones (AWS, GCP, or a respected MOOC) are fine
  • Do not write in third person — "Rahul is a passionate developer" reads as bizarre
  • Do not add 500+ random connections — connection count is irrelevant; relevant connections matter

The 20-minute LinkedIn overhaul

  1. Rewrite your headline using the formula above (2 min)
  2. Rewrite the first 3 lines of your About section (5 min)
  3. Add/update 2-3 Experience entries with bullet points (5 min)
  4. Add 10 relevant technical skills (3 min)
  5. Pin 2 items in Featured (3 min)
  6. Set a professional photo (2 min)

Quick quiz

Q: A recruiter at a Bangalore startup searches LinkedIn for "React PostgreSQL 2027 graduate." Which profile element determines if your profile appears?

How to explain it in an interview

"I treat LinkedIn as a searchable index, not a social feed. My headline has my target role, core tech stack, and graduation year — the three things recruiters filter by. My About section leads with what I build and links to my best GitHub repos. I keep the skills section limited to technologies I can actually code in."