^ That post is absolute TRUTH. Wow, great job! You hit the nail on the had with pretty much everything youâve said.
As a management-level person at my day job, I can definitely say thatâs basically how it is. But Iâd also like to add a few things too.
Like @runlinux.run mentioned, some people get certification after certification, and that alone doesnât add value. Training courses sell their services as if theyâre the secret weapon to success. At the end of the day, it depends on the hiring manager. If you nab a great paying job, it mightâve been because of your certifications, or maybe the hiring manager couldnât possibly care less about certifications and hired you because of your passion. And the thing is, often they wonât tell you why they hired you. And usually, a person will be so excited about the job they wonât even ask. Whether or not you should ask is a different debate altogether.
I like to think of certifications as two things - a metric, and a portfolio.
Using Certs as a Metric
As you learn and grow in IT, youâll reach individual âstagesâ. I like to think of it as kind of like leveling up in an RPG game. Lame example, but it works. As you get more experience, you gain more skills, and you reach the next level. At a certain point, you can take a certification exam as a personal test to gauge your knowledge. Be careful here though, because if you put too much emphasis on this, your certification exam will cause you to get discouraged. Always have the mindset âdust yourself off and try againâ if you fail.
But as a metric, you can use it to test your knowledge on a particular thing. An example use of this system might be:
- Study networking for a few months
- Take the CompTIA Network+ Exam
- Study server hardware for a few months
- Take the CompTIA Server+ Exam
- Study security concepts for a few months
- Take the Security+ Exam
- Study Linux for a while
- Attempt LPIC-1
- Study cloud concepts
- Take the AWS Cloud Practitioner exam (or similar entry-level cloud cert)
- Work with cloud for at least several months
- Take an AWS professional cert (or similar second-level cloud cert)
In that example, youâre using certifications as a way to measure yourself. If you fail a cert, take another 1-2 months and study your week areas. When you pass it, youâve âleveled upâ your knowledge another tier and start working on the next. The beauty of that system is that the new certs you get, typically ârenewâ the previous ones automatically, so you donât focus on renewing certs in-between, you keep your eyes on moving upward.
Will the hiring manager care about your certifications? Maybe, maybe not. Youâll never know. But the certs will still be of value to you either way.
Using Certs to fill a Portfolio
As a hiring manager myself, I wouldnât personally hire someone just because of a particular certification. Show me a portfolio. Show me what youâve done. Examples:
-
Use Github like crazy
As you study for your certs, using a system similar to the one above, put all of your code/scripts/notes in Github and make it public. Seriously, do not underestimate the value of this. Start early. Keep building it up. When itâs time for an interview, make sure you put your best scripts in your portfolio.
-
Be active in the community
Speaking for myself, you can impress me by fixing bugs. It doesnât have to be code, you can even just submit pull requests to other popular software projects to do simple things like fix spelling errors in the ReadMe files, update some documentation, it doesnât matter how difficult. Just fix something, even something as simple as removing an unneeded space. And keep doing it. If I see you active in the community around whatever youâre interviewing for, that impresses me. Put examples of this in your portfolio.
-
Use a similar Screen-name everywhere
Use the same screen-name in Github that you use on other career-related or IT-related services. Perhaps I can search for your Github handle, and that leads me to a stack overflow post where you solved a problem for someone. Or perhaps I search for your Github handle and I find that youâve been posting in a Linux (or similar) forum and youâve been helping people.
-
Be courteous
Avoid âRTFMâ responses. Avoid being rude online. Just like I mentioned it helps you if I search for your name or username and find all kinds of things youâve done and I see how active you are, if youâre rude to people then I wonât be as likely to hire you because I may be afraid youâd be rude to coworkers.
-
Create something
I donât care if itâs a simple script or an advanced GUI application. Create something, and maintain it during the entire time youâre studying for certs. You could create an awesome project on Github that a lot of people appreciate. It also demonstrates how you collaborate with others on a project.
Do certs matter?
To me, yes. If I see only certs and nothing else, that tells me you can pass a test. But if the certs are part of your portfolio, and your portfolio has other great things too, the certs definitely add value for sure. It shows you have a drive to study, read, and learn. And your involvement in the community shows me that your certs are not just filler, you are achieving them because youâre passionate.
Above all, have fun!
Donât let IT become a burden or a stress. Have fun with it. Recompile the Linux kernel. If it fails, donât get annoyed, have fun figuring out why. Install Linux on an extra laptop and/or server and make it do things. Install Linux on your toaster if you can, set up VMs on VirtualBox or Proxmox and try to customize subnets and VLANs. Practice locking down the servers so no one else can see them. Keep having fun, and document what you learn online in a public place, and make sure your scripts and contributions are public and easy to link back to you.