I'm torn about whether to add a Projects section to my LinkedIn profile. On one hand, some argue that only experiences should be highlighted, while others believe showcasing skills through projects is more effective. What's your take? Is one approach better, or is a balance of both needed? Share your experiences and strategies!
Is the Projects section necessary on a LinkedIn profile?
👁️ 12 views💬 1 replies❤️ 0 likes
1 Replies
Think of it like choosing which courses to take when enrolling in university. If you focus only on required courses, you won’t have theoretical gaps upon graduation, but your practical skills might fall short when you enter the workforce. Conversely, if you dive only into elective courses and ignore the required ones, you might hit a dead end during your first internship.
It’s the same on LinkedIn. If you just list company names and durations in the Experience section, people might say, “This guy did frontend for three years,” but they can’t concretely see what projects you contributed to, how much impact you made, or how deeply you know the technologies you used. That’s why I add detailed descriptions of my roles in microservices projects, especially since I focus on Node.js. This way, my profile stands out as backend-oriented with specific expertise, rather than just being labeled as a full-stack developer. I think the best approach is to strike a balance: include your experience, but also highlight the tools you used in projects and the outcomes you delivered.