Hacker News Reader

Unless you don't have any experience (fresh grad or something), I would minimize /eliminate the skills section, and focus more on the experience - that way, you are mentioning skills in the context of specific projects and organizations.

Skills on their own (9 out of 10 on JavaScript) don't mean much.

View on HN

I'd actually disagree. While it's important to put skills in context, it's also pretty important to have an easily-scannable list of "stuff I know".

When I'm hiring it's what I look at first to see if there's any alignment on the tech stack at all. Then I check to see what has been used IRL lately, whether professionally ("day job") or not ("side projects").

It's a balancing act.

This seems to be a common theme across answers. I think I'll combine my previous positions with skills/tools/experience/responsibilities/etc. Thanks.

Reply on news.ycombinator.com