Skip to main content

Certified or Certifiable?

As a senior technology professional, I interview a lot of candidates. I also maintain solid relationships with other folks in the community. Frequently, the topic of certifications arises: A good investment? Valuable? A clear measurement of skill?

Consensus appears to draw the line related to one's seniority. If you're (for example) just out of school and looking for an instant creditability boost, by all means pursue a certification. Likely, this credential will assist you in overcoming the "junior" tag and likely land you more interviews and client roles. (Note: I'm going to use the terms senior and junior offense to either. Can't think of a better one word description. I was a junior once too.)

In stark contrast, the value of certifications drops off the table around the 2-3 year mark. Some in my circles even perceive certifications as a negative for the senior professional. They think, "If this guy is so solid, why is he wasting valuable time pursuing certifications? He should be out presenting, involving himself with the community, writing, and leading by creative means."

For the record, I have my MCSD (since 1997) and the RUP certification. Earlier in my career, I think they served me well. However, I haven't pursued certifications for some time--and these I pursued partially from a self-serving reason and partially to contribute to "number of certified professionals quotas" for vendor partner relationships (I've worked for Microsoft Gold Partners for much of my career). Quite honestly, I just have far better uses of my time (continuous learning, presenting, building new lines of business, recruiting, writing, mentoring, etc.) than pursuing certifications.

Admittedly, I do learn some things when preparing for an exam. Going back and drilling into the nitty-gritty helps me pick up on all the things I missed while self-teaching and the get-er-done processes we all follow during rapid learning. Further, certifications whisked me in the door for many client and full-time opportunities. They didn't, however, aid me in locking up positions--that was up to me.

I think we tend to look at certifications as a clear, quantitative manner in which to publicize and communicate, "Hey, I know my stuff!" to an otherwise less-than-captivated audience bothered by a lot of noise. It's an easy answer but don't believe it. For the most part, the greatest developers or technologists I've encountered were not certified. Not only were they not certified, they weren't even computer science majors.

These folks were artists. Plain and simple. They were creative craftspeople who were genuinely passionate and engaged in their pursuit of greatness. And they didn't need a certification to highlight their talents. You know these folks too. They just ooze with technology coolness. These are the guys and ladies you see at every conference and event: organizing, presenting, evangelizing, and providing energy.

With the exception of benefit and instant creditability for less-experienced staff, why do certifications even exist? (BTW, I truly believe certifications for the 1-2 year consulting staffer are no-brainers. Go out there and make a name for yourself. Other, larger opportunities will present themselves as a result).

Certifications exist for two reasons:

  • Proliferation of vendor 'wares
  • Industry attempt at lending creditability
  • Company feel-good about hiring decisions

Vendors love it when you get certified! We're so important--we have 50,000 certified TechnoCo professionals! I guess they figure it validates their market and gives them a way to assist companies to [incorrectly] assess candidates. (Full disclosure: I've done editing work for ReviewNet (assessment firm). I don't agree with a company leveraging these assessments but I do feel positive about helping ReviewNet to at least get the questions right.)

I think there's also an attempt from the technology industry to "professionalize" our industry. Attorneys must pass the Bar, medical doctors pass boards and fulfill residencies, and CPAs pass...well the CPA. I suppose this is good but does it simply serve as an artificial barrier to entry? Again, I know fantastic doctors, attorneys, and CPA--and I also know horrid ones. They're all "certified". Label me unimpressed.

Which brings me to my final point: companies typically do a poor job of interviewing and hiring staff. For every great interviewer--there are 9 horrid ones. Companies assessing candidates using certifications seek out some homogenous automaton whom they perceive can sling out code faster (note: not with better quality) than the next, uncertified candidate. I think it also creates a CYA of sorts: "well, Rich is certified...he must be good!" C'mon. That's just lazy. How passionate are they? Can they communicate? Can they solve problems? Can they learn? Can they teach?

So my advice is this:

  • Companies: stop giving more than about 2% weight to certifications
  • Juniors: get your certs but look beyond them very quickly
  • Seniors: don't even touch 'em. Substitute: blogging, presenting, community involvement, and mentoring

Please weigh in with your thoughts below!


muncman said…
I agree with your assessment. Very well put, I might add! One exception might be if a senior person is switching platforms. The exercise of studying for Microsoft certs (if not actually taking them) might be of benefit to a life-long Java dev, perhaps?
Jeff Hunsaker said…
@muncman Hadn't thought of that one. However, if a senior Java person flips to .Net, they'll have some instant creditability from me. The language isn't that far off and the concepts are very similar. Learning the surrounding technology would be the hurdle: struts, spring, etc. So, I'm not sure pursuing a cert would be the best use of time for that person.
Anonymous said…
I could not disagree with you more here. Blogging a substitute for certs? Most employers would laugh you out of the building here in the UK. Community involvement, mentoring, blogging are all good, but as a measure of actual valuable skills they dont mean a thing. Thats why certs exist: as an external validated measure of how good you ARE, not as how good you SAY you are. I'd rather hire an MCSD than someone with a page rank 4 any day of the week!
Jeff Hunsaker said…
@anonymous My argument isn't so much for or against certifications (remember, I'm an MCSD) but rather does it make sense for a senior professional (7+ years) to invest time pursuing certifications when there are other things s/he could be pursuing: presenting, improving relationship/networking skills, selling in new business, etc.

That said, I'm not convinced certifications are as quantifiable as we'd all like to think. I've seen MCSDs who couldn't tell me the difference between an interface and an abstract class. I'm just never going to give a lot of weight to certifications.

Good to grab if you're junior but IMO, not for senior folks.
Anonymous said…
I used to tech folks and the certs rarely were an indication of interest, passion or talent. Just because you can cram for a test doesn't mean you understand the concepts and apply them in creative and innovative ways. For me a certification is a great way to feel personal ownership over the technologies you're testing for. I'd say it's for the developer. If they love them, get them, if not then don't.

For the record--
Major: BFA in Musical Theater
Certs: None.

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i