Are there really ColdFusion jobs out there or are they teasing us?

As of today, I'm married 14 years. This means that I've been using ColdFusion for 14 years and 1 week. In those years I've done everything from create some of what is considered best practices to helping build a framework to consulting with Allaire and Macromedia on the development of the language. Basically, my resume is stacked with ColdFusion. So if this is the case, why can't I get a ColdFusion job?

Let me rephrase that. Why are there so many ColdFusion jobs out there that never seem to be filled even though qualified people post to them? I've seen jobs come up on job boards and I've seen people post to them (sometimes including myself). I've seen the same jobs come up again and again, week after week, even after resumes are sent in. So what's up? Are the resumes being ignored? Is there a sinister plot out there to make ColdFusion job hunters feel rejected?

Rather than suspect that people are against us, lets instead wonder if we're to blame. Most job postings request one or more of the following:

1. Job Requirements
2. Current Resume
3. Salary Requirements
4. Cover Letter
5. Code Sample

Job Requirements

Just about every job posting has requirements. It's not enough to be skilled in every requirement the job mentions, you have to explicitly state it and give examples. Do you know SQL? Then make sure one of your resume items mentions the SQL work you've done. Also, make sure your resume's skill set not only says SQL but mentions specific, high level features such as stored procedures. Assume that whoever is reading your resume can not make any assumptions.

Current Resume

Many of us have not updated our resume in a while. We may only list full time work we've done along with a vague "consulting" instead of detailing every contract. We may also list things that are outside of direct work, such as sites we do for free or as a community service. This isn't good enough. Every resume sent to a job has to be unique. Some past jobs should be removed. Others should be exemplified. The resume should read like it was written specifically for the job...because it was.
Oh, and if a job posting says to send your resume, send it. Don't include a link to is in Google Docs or on a site. If they're expecting an attached document, make sure it's there.

Salary Requirements

This tiny little feature is usually skipped by many job respondants. They either have no clue what to ask, are afraid of giving a number, or are too focused on the other parts of the job offer. My advice - Never skip this and never under bid. Judith just missed an editorial contract because she gave a realistic assessment of what the job would require and what it would be worth. The message she got back was that her offer was too low. If you're a professional then it's better to overbid than underbid. This shows them that you think your worth it and gives you room to negotiate. Just don't go too far over what you think is expected.

Cover Letter

This is where I usually fall down. What do you say in a cover letter? Hi, I want this job? Rather than hear me speak about it's requirements, let me have Judith tell you what she thinks.

Judith's words on Cover Letters

Cover letters are more important than most people realize. They are the best way to make a first impression and distinguish yourself from the job-seeking horde (your competitors for the job). A cover letter must pull your reader in and convince him or her that you are something special. It's your "elevator sales pitch". It should be short (no more than three paragraphs maximum) and targeted to the specific job. It should highlight what makes you, the job seeker, the best candidate for this job. It should make them want to read your resume. Many recruiters read the cover letter and don't even bother reading the resume if they're not impressed.

Code Sample

This is the one place where technical people fall down. They want to send some sweet code that just makes them look like God's own prophet. Well your holiness, think about it first. Does the code have anything to do with what the job post is about? Are they looking for a SQL guru and you're sending them the most perfect site scraping code around? As with the current resume above, make sure they're getting a code sample that fits exactly what you think they want. Take it one step further and try to make the code sample solve part of the job requirements. It'll make them think they're getting a bargan as you've already done the same type of work.

In Closing

This is just the tip of the iceberg when it comes to resumes and if you're looking for a job you should read up on how to write an effective one. And to paraphrase Chris Rock "If you have to give a friend a ride, get a white (collar) friend". You should never send off a resume without having someone else look at both the resume and the cover letter to make sure it fits the job. And finally, to quote Rodney Dangerfield "When you're using the name, don't give it a bad name". You're representing ColdFusion when you respond to a job. If you look bad, it reflects on ColdFusion and its users in general.