Let me preface this story with the confession that I collect certifications a lot like other people collect stamps or coins. From becoming the first Certified Professional Manufacturers representative in the plumbing industry to my latest WebOps Certified Developer, I enjoy the learning experience that comes with the process of becoming certified.

Why Become WebOps Certified?

Assuming you aren’t collecting certifications like I am, why would you want to become certified?

For most people, the reason is to have external validation of a skill or knowledge set. Just like going to college and getting a degree is a kind of certification, getting a topical certification is a way of showing mastery of a subject. Fortunately, professional certifications are a much more cost-effective way of achieving that validation.

A Venn diagram of an unscientific but largely accurate visualization of who gets certifications.
Looking at the Venn diagram that I cooked up myself, you can see the population of qualified developers for any given skill set is much larger than those who are certified. A lot of developers are either not aware of the certification, do not feel they need that validation, or have some impediment like language or financial resources.

Those who take the time to get certified signal to possible employers their willingness to grow professionally. Back when I was more directly involved in hiring decisions, being certified didn’t guarantee a job, but it did guarantee an interview. Not being certified puts more stress on a resume that communicates your qualifications. And more and more job postings that I see from recruiters include a requirement to be certified.

One final point on this diagram. While most certified developers are qualified, it is possible for some unqualified developers to successfully pass the certification exam. Fortunately, that is a very small percentage.