Is it a good idea to take an MS Cert Exam?

Question

I am a beginning programmer (been doing it for about a year) and learnt by reading books on C# and getting experience at a family's software dev company. I also spend a lot of time coding in my own time.

I am quite a fervent developer and I love .NET.

I want to get a job in C# software development.

Is it a good idea to first get some more experience in C# and then take MS exams or the other way around?

EDIT:

From current answers, it seems experience is quite an important factor. So taking part in Open Source projects and doing some hobby-time projects would be a good factor in getting a job and showing my enthusiasm for programming?

Answer 1

You're going to need both.

Unfortunately there are some shops in my experience that rely on exclusively one or the other, so your mileage may vary.

I tend to think my certifications may distinguish me from other resumes, but I have in the past left them off.

I would advise that you join or start an Open Source project instead to demonstrate your abilities and interest. Certifications can come later.

Answer 2

If you don't have job experience in .NET, a certification will certainly help get your foot in the door, for some shops. Once you have a couple of years of experience, the certification matters less. It was very worthwhile for me, but at this point in my career, it's not worth keeping it up-to-date.

Answer 3

I took couple of MCPD certifications this year. It was beneficial for me in way because in preparing for it I was exposed to various aspects of .NET arena. In term of job scene not much. It just occupies a couple of lines in my resume and I am not sure employers care much for it compared to actual experience.

I would say any pet projects or open source participation will be better.

Answer 4

Whenever I see a resume, I completely ignore all certifications and focus on experience only. I would rather talk about some awesome program you wrote in your free time, even if it has no monetary or business value, than to talk about what you learned in some certification course.

Answer 5

A certification shows you've at least put some effort into learning the technology and have been evaluated to meet minimum proficiencies. My problem with most all computer related certifications is they almost universally require no continuing education (as opposed to certifications in other fields). Without ConEd it is difficult to determine how "fresh" your knowledge is.

If you're participating in projects, you've had to at least learn the technology, learn how to work with others, and stay relatively current in the technology.

I'm far more likely to take a new hire who has actively participated in projects either personal or open source over someone who just has a certification.

Answer 6

I think they're fine if you're just starting out. Without a lot of experience, you need something to distinguish yourself from others who are in the same boat. If nothing else, the certification at least shows that you're serious about it.

They may also help keep you focused and motivated as you work your way through learning a new technology.

Overall, I agree with the consensus that certs hold less and less value over time. After a few years, it's really your experience and reputation that matter. If you've been developing for 10 years and still need to point to a certification to land a job, something's very wrong.

Answer 7

When I review applicants for development position I look for experience or records that show the applicant is working to improve their skills (IE studying or working in OS projects). I also like to see some CS or CIS in their background. I don't pay close attention to a certification, except for it shows growth in the technology. I personally feel certifications are expensive, and they become stagnate after a few years.

-Jay