So I looked it up and Google is offering certifications in various fields through Coursera, and they claim it’ll help one get a good paying IT job.
People have made videos on Youtube talking about them with varying answers and in the comments, people often discuss using them as a springboard to get CompTIA certs.
But are these certifications actually worth the money financially? Do people actually get hired if that’s all an employee has? Don’t employers want people with degrees too?
For software development at least, they can help prove you know a concept, but they aren’t going to do everything for you. So if it’s on your resume it may help an HR/hiring manager see that you’re willing to put your money where your mouth is to prove it, but they’re still going to look for experience and other stuff too.
So, I guess what I’m saying, it’ll help - but it won’t do anything like replace a college degree either. They’re good, but don’t believe their marketing hype either.
If someone wanted to get into IT but was unable to get a degree for whatever reason, how would they do it?
Get an entry level helldesk job and learn all you can from your peers. After you become comfortable start asking the senior engineers for harder tasks.
There are plenty of skills that are in demand but have no certs. Scripting with Bash and python for Linux systems or PowerShell for windows are some examples.
Automation like Terraform or Ansible are also good to learn but have no official certs.Help desk is the answer. The key is to work towards understanding the industry you’re doing support in. A ton of companies love support members because they end up knowing the product, the use cases, and the clients better than most other folks in the company.
This is the way. If you can’t find a way into a company you know you want to work for, start in Support. Shine, and move up and out.
I’ve been in IT for a few decades now with no degree. Just got a raise, I’m officially pulling in 12K a month pre-tax.
Here’s how I did it:
-
Work a series of crappy non-tech jobs where I became “the computer guy” because nobody else knew anything.
-
Tear a calf muscle and have to get a desk job.
-
Get a phone monkey job answering tech questions. That job had an opportunity to start training other people.
-
Took the training skills and got a job teaching at a for profit tech school. They wanted me to teach their A+, Microsoft and Linux classes so paid for my certs.
-
School folded after 9/11, so I took the certs and became a system administrator. Windows, Mac, Linux, Unix phone systems.
-
After about a decade of that, had a bad experience, burned out, went back to a phone monkey gig for a tiny start up company.
-
Got IPO shares. Paid for my kids college.
-
Got bought by a GIANT tech company. Not FAANG level, but a few steps below that.
Now…
My KID… went to college, got his Computer Science Degree. Interned at Intel, had his first paying job at Intel, jumped ship to Oracle, and is now out engineering those AI systems that have everyone creeped out.
After getting a 4 year degree, he went from making the same money I did more or less immediately to making 3x what I do in less than 5 years.
-
As a software engineer that is involved in hiring decisions, they are not worth anything with respect to software development jobs.
I look for, in order of importance:
- demonstrated experience - this is your work history
- academic achievement - this is college degree. I do not include certs
- additional skills - this tends to be a skills section - I expect people to not lie and will ask about this section explicitly in interviews
- external factors - previous job - circumstances around leaving
And that’s it. Certs don’t ever even get considered.
Conversely, as a system engineer that is involved in the hiring process for software development in addition to various types of platform and cloud engineering jobs.
I look for, in order of importance:
- demonstrated experience
- additional skills
That’s it. College degree isn’t even considered, but if you got relevant experience in college that can count.
Most of my interview time is spent digging into technical details to see if you can back up your resume claims. The rest is getting an idea of how you approach challenges and think about things.
As far as certifications, they’re often required to get in the door due to qualification regulations. Especially security certs. If you list them, I’ll ask a few questions just to make sure you actually know what’s up.
Why?
Good for getting your foot in the door. And their content can often be useful if you intend to work on the topic. For instance, I learned some things by reading the Security+ materials without having any intention of getting the cert.
Don’t employers want people with degrees too?
This all varies for the job and the cert or degree, but degrees are good. Certs might be good enough. Basically an employer wants to know you can do the job. Degrees and certs are ways they can verify that. Between you saying “I know how to replace a CPU” and some other schlub saying “I have an A+”, it’s easier to take CompTIA’s word than yours.
And experience trumps all, usually.
