Certifications in software development

Jose Salvatierra
School of Code
Published in
2 min readJul 14, 2015

Java is a very popular language to learn, and sadly it is also one with a lot of certifications that you can take (and pay for). Every new learner eventually asks the question, “is this certificate worth it?”.

And the answer usually is: no.

In many industries, certifications are extremely valuable. In others, they hold some value. In software development, certifications hold very little value, because employers are looking for what you know, and certifications don’t guarantee knowledge.

You don’t become an expert in Agile by doing a two-day course and then a 15-minute test, in the same way that doing a multiple choice Java certification doesn’t guarantee that you know any Java.

This is why certifications may actually hurt your resume. It is seen as though you’ve put them there because you think you know the topics covered. You may or may not know them, but chances are you haven’t become an expert from taking a course and doing an exam. You’d be better off creating a project that uses the technology, or by showing you have experience through a job or an interview. Then, put those in your resume.

So what about MOOCs?

You wouldn’t put MOOCs in your resume, unless they are directly related to the job you are applying to. Even then, having real experience would be much more valuable for your employer.

It is not all about getting to the job interview, or even getting the job. It is about learning new things, and acquiring new skills.

Shorter online courses, such as private courses in Udemy or Udacity, are also great for this very reason. To start acquiring a new skill, but they won’t replace actual experience, and, whenever possible, you should try to use these skills in a work environment. Then they become truly useful!

What can you do instead?

The most valuable thing for an employer: work experience. Where have you worked, what did you do that brought value, how did you solve problems and overcome challenges?

Next up: projects, preferably related to the job you’re applying to. Don’t put unfinished or unpolished projects in your resume, as that will look unprofessional. Make projects, and make them well. Then, put them in your resume if they are related or if they are particularly impressive.

Finally: there’s no space left, because your resume should be short (1–2 pages max).

What should you take from this

Certifications are often not very valued. Don’t put much focus on them, except where required. Think about whether your employer is placing value in the things that are actually valuable, if they require you to have a specific certification, or if they just want a piece of paper.

--

--