Hacker News Reader

Comment by doix | Hacker News Reader

> If you do put a "skills cloud" on it, be ready to talk about them all. If someone had a skills cloud I would immediately look for the most esoteric skills and dive deep on it in the interview (after Googling it myself) to see if you were BSing or not. If you really know that skill, you should know more than what I learned in five minutes of searching.

That's super important in my opinion. I try and write as little as possible on my resume because I don't want to get asked about stuff I don't remember. I keep it to 1 page, write as little as possible and hope that people recognize the default LaTeX font and interview me because my super concise CV makes me look interesting/mysterious.

It's worked well enough for me, but it's a small sample size and luck plays a huge role of course.

View on HN

Couldn't agree more. Not even just in the skills cloud section, don't put anything on your resume that you're not ready to talk about in an interview. It's baffling the amount of candidates that answer questions about their resumes with "Oh it was so long ago I don't remember" or "Oh it was just a quick 2 week R&D spike that was never shipped".

If something was a long time ago, just summarize it and keep it short and sweet. Nobody needs to read 8 bullet points on an internship you had 7 gigs ago which has no relevance to the job you're applying for. Contractors are particularly bad offenders here in my experience. No hiring manager will read through a 13 page resume for somebody with 6 years experience. As the TFA mentions, use that valuable space to highlight more recent, relevant experience and put your best foot forward. Everything else is just noise.

> Nobody needs to read 8 bullet points on an internship you had 7 gigs ago which has no relevance to the job you're applying for. Contractors are particularly bad offenders here in my experience. No hiring manager will read through a 13 page resume for somebody with 6 years experience.

The first bullet point for each one of those is:

* Followed the Software Development Lifecycle

The second bullet point is:

* Attended all required meetings and ceremonies for agile scrum

At the end of each contract is two lines of technologies used in the environment (though not necessarily by the candidate). For example, kuberentes will certainly be on that list. When asked about helm or kustomize or kubectl: "Oh, the build put an image out on docker hub and then the operations team did all the work to deploy it."

Maybe I should reduce some of my earlier entries. I've still got my entire work history on my CV. I worked on a specific CMS from 2004-2008, and I still get asked for gigs related to that CMS (even if the version I worked on is nothing like the current version). I worked on a PHP problem for 3 days once, and put it in mostly as an example that I can quickly adapt to new languages, but some people actually want to hire me for a pure PHP project.

The "this is everything that I've worked on, if this interests you, contact me" is different than a "this is the information relevant to the job that I am applying for."

If you've got a CV hosted somewhere with CMS and you still do CMS stuff and want to get hired to do CMS stuff... leave it on there. If you don't want to do CMS stuff, take it off.

If you are applying to a job that isn't doing CMS stuff, on your resume that you're sending to them don't have more than a single bullet point for that old job about CMS duties.

Reply on news.ycombinator.com