Hacker News new | ask | show | jobs
by purpleidea 2066 days ago
Personally I've found certifications are a good way to show you're good at passing certifications, and nothing else.

I have nothing against people who show up with their resumes filled with them, but it's not a valuable indicator in my opinion. I'd rather see what they've built. Show me some useful things on your github or blog. That I can see value in.

Obviously we're talking about software-related certs, not pilots licenses, etc...

2 comments

When recruiting, I usually take certifications as a token of the lack of skills rather than a demonstration of skills
Exactly. If someone wants to demonstrate that they can use Github the best way is for their personal Github to be full of well-structured projects.
This gets repeated every time, but it's worth repeating: You've just discounted many skilled people working at companies which don't allow public personal projects, and people who are not interested in working on personal projects. There's a significant number of them.
I should rephrase -- having stuff in your Github is the best way to show you know your way around Github.

Not discounting the fact that you may have lots of other skills and nothing in your Github.

In general if someone has enough other skills and worked at companies that have a high bar, it's likely they can pick up Github fast enough even if they haven't used it that it shouldn't be a hiring concern.

Like for example, if someone is fluent in C++ or some such, I wouldn't doubt their ability to learn how to use git.

What if you have both certifications and skills?
> Personally I've found certifications are a good way to show you're good at passing certifications, and nothing else.

Some are good. I did AWS Solution Architect Pro, and this one was tough, one needs years of hands on to pass. Anyone with this one will get an instant plus in my book. I did not bother renewing it though, after 3yrs expired :)

Being difficult != good. It can take years to prep and pass a CCIE as well but it’s not really a good indicator of being a good network engineer, despite the esoteric protocol details you have to memorize.
> Being difficult != good.

I did not say that. I said some are good, and named one.

I spent some time last year getting some "beginner" AWS certifications and those are definitely worth it; I spent a few dozen hours following online courses (A Cloud Guru is pretty good, and if you have the time you only need to subscribe for a month or so) and feel like I went from superficial knowledge (like sorta knowing what AWS, EC2, RDS etc are) to having err, certified superficial knowledge. TL;DR I know more about AWS now without actually having worked in it.

That said, I wouldn't go for any of the other certifications without actually working / having worked professionally in AWS. Or anything you can get certified for, for that matter.

I mean iirc I've got some cisco certifications as well but I and everyone else cheated on the exam and don't remember anything of it.