Microsoft Certified Solution Developer

Microsoft Certified Solution Developer, or MCSD, is the premier MicrosoftCertifiedProfessional credential for software developers. According to Microsoft, it is "the top-level certification for advanced developers who design and develop leading-edge enterprise solutions".

There are currently two "tracks" for MCSD: one for Visual Studio 6.0 developers, and one for Visual Studio .NET developers. The 6.0 track requires passage of four exams; the .NET track requires five exams. The 6.0 track is, of course, being phased out.


Having recently obtained this certification, I thought I'd share my experience and opinions.

I got the MCSD certification for .NET. I've been trying to find contract jobs for the past year, and despite ten years of experience with a variety of operating systems and programming languages, nobody will hire me because I don't have 3+ years of professional Java experience or twelve months of .NET. It is too late to jump on the crowded Java bandwagon, so I went for the MCSD.NET certification hoping it would help me get in on an early .NET job.

The benefits of holding an MCSD are pretty meager. I never had any recruiter or interviewer say "Oh, you are an MCSD? That's great!" The only person who mentioned my certification at all simply said that he didn't think much of it, but wouldn't hold it against me.

Of course, I did get a nice lapel pin and a handsome certificate suitable for framing.

The lack of respect for MCSD is well founded, in my opinion. For the most part, it represents one's ability to absorb documentation and regurgitate it during the exam. While studying, I did learn some things that I probably wouldn't have if I didn't have a goal to pursue, but the exams are really nothing more than trivia contests. The exams were not as easy as some claim, but they do little to test one's competence as a developer.

The best that can be said is that a holder of an MCSD has demonstrated familiarity with the features of Microsoft's development tools, and knows how to use them as Microsoft intends. So it is strong evidence that someone has done more than spend a couple of weekends going through the VS.NET tutorials before declaring himself or herself to be a .NET expert. But I would never consider it to be evidence that one is a "top-level ... advanced developer" as Microsoft claims.

It's a little like a driver's license. One must pass a test of minimum competence, not of extraordinary ability. It indicates that the holder is familiar with traffic laws, knows how to use the turn signals, and is capable of driving competently through the cones on a closed course. It cannot guarantee that the holder won't do a lot of stupid things out on the open road, and does not indicate that the holder is ready to be a professional driver.

As a job seeker, I will continue to put MCSD on my resume in the hope it will trigger a favorable response from somebody somewhere. However, if I was hiring somebody, I would probably ignore an MCSD certification (or any other MS certification), except maybe as a tie-breaker when considering candidates who have little real-world experience.

For anyone going after the MCSD for .NET, I offer these tips:

-- KrisJohnson, MCSD


See also SoftwareCertificationDiscussion


CategoryMicrosoft


EditText of this page (last edited November 7, 2005) or FindPage with title or text search