Guides › Career
LinkedIn Profile for Freshers: A Section-by-Section Guide
Photo, headline, About, projects, skills, custom URL and "Open to work" — plus how to grow your network, post and ask for referrals the right way.
Recruiters search LinkedIn for freshers every day — for internships, off-campus roles and referrals. A complete, clear profile gets found; an empty one doesn't. You don't need experience to have a strong profile. This guide goes section by section, with examples you can adapt.
1. Profile photo and banner
- Photo: a clear, well-lit photo of your face, plain background, looking at the camera. Profiles with photos get far more views. No group photos, sunglasses or selfies from far away.
- Banner: the wide image behind your photo. Use something simple and relevant — a clean tech background, or your name + "Aspiring Software Engineer | Java · React". Canva has free LinkedIn banner templates.
2. Headline (the most important line)
The headline appears next to your name everywhere — in search results, comments and connection requests. "Student at XYZ College" wastes it.
Formula: Role you want | Main skills | Something that proves it
Examples:
- Aspiring Software Engineer | Java, DSA, Spring Boot | 300+ problems solved
- Final-year CSE student | MERN Stack Developer | Built a real-time chat app
- Data Analyst in the making | SQL, Python, Power BI | 2 dashboard projects
3. About section
3–5 short paragraphs, first person, plain English:
- Who you are and what you're looking for.
- What you've built or learned (with numbers).
- Your main skills.
- How to reach you.
Example:
I'm a final-year Computer Science student at XYZ College looking for software engineering roles and internships starting in 2026.
I enjoy building web applications. My recent project is a real-time chat app (React, Node.js, Socket.IO, MongoDB) used by 40 classmates. I've solved 300+ DSA problems and take part in weekly coding contests.
Skills: Java, JavaScript, React, Node.js, MongoDB, SQL, Git.
Open to connect — email me at name@email.com.
4. Experience
No job yet? You can still add:
- Internships (even short or unpaid ones)
- Freelance or college projects for a real client
- Technical roles in clubs (e.g. "Web Lead, Coding Club")
- Teaching assistant, open-source contributions
Write each one with action verbs and results: "Built the club's event registration site in React; 250 students registered through it."
5. Projects
Add 2–4 projects with:
- A one-line description of what it does
- The tech stack
- One result or interesting challenge
- Links to the live demo and GitHub repo
Not sure what to build? See project ideas and which projects suit which role.
6. Education, skills and certificates
- Education: degree, college, years, CGPA (if it's good), relevant coursework.
- Skills: add 10–15 real skills and pin the top 3 that match the job you want. Don't add things you can't discuss in an interview.
- Licenses & certifications: add verifiable certificates — for example, Codify roadmap certificates have a public verification link.
7. Custom URL and contact info
Change your profile URL from linkedin.com/in/rahul-sharma-8a7b3c21 to linkedin.com/in/rahulsharma-dev (Edit public profile & URL). Put this URL on your resume. Add your email and GitHub in Contact info.
8. Turn on "Open to work"
Set the roles (Software Engineer, Frontend Developer…), locations and job types (internship, full-time). You can show it to recruiters only, without the green frame, if you prefer.
Growing your network
- Connect with classmates, seniors, alumni from your college working in companies you like, and recruiters in your field.
- Always add a note when connecting with someone you don't know:
Hi Priya, I'm a final-year CSE student at XYZ and saw you work on the backend team at ABC. I'm preparing for SDE roles and would love to follow your work. Thanks!
- Aim for 300–500 relevant connections over a few months, not thousands of random ones.
Posting (even occasionally) helps
You don't need to post daily. Once or twice a month is enough:
- Finished a project? Post a short demo video and what you learned.
- Got a certificate or won a contest? Share it with one line of what was hard.
- Learned something? Write a 5-line tip.
Keep posts honest and specific. "Excited to share…" + a real screenshot + 3 lessons beats a long motivational post.
Asking for a referral
Once you've connected and the person knows who you are:
Hi Rahul, thanks for connecting! I saw ABC has an opening for SDE-1 (job ID 12345). I've built [project] with [stack] and solved 300+ DSA problems. Would you be comfortable referring me? I've attached my resume — happy to answer any questions.
Short, specific, with the job ID and resume. Thank them whatever they decide.
Checklist
- Clear photo and simple banner
- Headline with role + skills + proof
- About section with what you've built
- 2–4 projects with links
- Skills that match your target role
- Custom URL on your resume
- "Open to work" turned on
Pair this with a clean GitHub profile — recruiters often click from one to the other.
More guides
- How to Use Codify: A 7-Day Start Plan — New here? Pick a roadmap, make a study plan, start the DSA sheet, revise with notes, practise for placements and test yourself — one step a day, then a daily routine.
- Infosys Preparation Guide: Online Test, Pseudocode and Interview — Roles (SE, DSE, SP), what each section of the Infosys online test checks, how to crack pseudocode and reasoning, a 4-week plan and the interview.
- Wipro Elite NLTH Preparation: Aptitude, Essay and Coding — The Wipro fresher test round by round — quant, logical and verbal, the written essay, two coding problems — plus a 3-week plan and interview tips.
- Accenture Preparation Guide: Cognitive, Technical, Coding and Communication — Every Accenture round explained — cognitive, MS Office/networking/cloud technical MCQs, pseudocode, coding and the spoken-English test — with a 4-week plan.