It depends on the kind of job you're after, but for most jobs, certifications are close to meaningless.
A certification says little to nothing about your practical programming skills; the way it usually works is that you sit through some coursework, and then take a multiple-choice exam. Obviously, such an exam mostly tests factual knowledge, that is, things you can easily learn by heart given enough time - but actual problem solving skills aren't required to pass such an exam. If anything, a certification attests that you can remember and accurately reproduce large numbers of arbitrary facts. Or, put differently, a certification is about those parts of a programmer's skill set that are easy to acquire, quickly outdated, and usually available within 10 seconds of googling.
What employers (at least the better ones) are really looking for is the tricky part of the skill set: problem solving, analytical thinking, juggling abstractions, a flexible mindset, good intuition about what directions a project might take, communication skills and some insight about how the human mind ticks. And there are enough much better ways to check for those - experience, code samples, technical writing samples, on-site programming tests, in-person interviews, forum posts, etc. So if you want to impress prospective employers, better work on those fronts.
That said, there are exceptions to the rule. Some companies have a policy of having all employees certified, and there are situations where certification is even required, either by law, or as part of a licensing agreement. When this is the case, a candidate who already has the required certification might enjoy a slight preference over someone who doesn't. This is not something I'd spend a lot of thought on though, unless you already know that you really want to work at a particular company that has such rules.