Over at my nonprofit tech jobs listserv at NTEN, when I look at certain tech jobs posted, I'm always interested in the way that they are structured: like, "we want a web designer and developer" which, to me, is like asking for a "plumber electrician".
I think we as a community can do our part to educate the outside world on the different functions related to the web-based information-sharing process and to understand that there are different job descriptions based on different parts of the process.
A) one job is a "communicator" or "web editor" or "content provider" --> someone who can create content, write, research, connect with people, network, and who can be basically someone who creates new content that matches your org's marketing and/or communications department. This is like a public-facing role.
B) another job is "data entry" for someone who is simply converting Word documents into CSS or who is doing copy and paste into your existing content management system--- they can be somebody who just does CSS/HTML and they don't need to be able to do new research or writing.
C) a web manager (or webmaster, or what have you) would be someone who can make your system function as a whole and who can either assign or who can manage different requests ---> turn them into pages and posts. This person may or may not be a public-facing person ---> in general, I think they are more of a "techie" type person meaning they would prefer to be on the computer not on the phone.
D) your web programmer/coder/developer is someone who lives, eats, breathes code. They definitely want to be left alone to deal with the issues related to your overall content structure and they want to deal with new programming problems and solutions. Not good with rote work or routine--> good with a new challenge or idea or function to enable. They would prefer not to go into Photoshop and create a new button for you.
F) your web themer is like the in-between from the designer to the coder ---> the themer convert the design into a theme which can then be used on the live site. The designer sometimes but not always is also a themer. The themer can do PHP and understands how functionality and available options are related to your specific needs, but they may not be able to cope with creating advanced functionality on your site.
G) your web hosting technical support speaks LAMP and can help you troubleshoot issues related to permissions, file access to your server, and configuration and security issues. They can answer your question if you have all your details ready, like what prompted the error, what browser and platform you're using, what you were doing when you got the error, and if you have a screenshot.
H) your social marketing person speaks RSS, Facebook, and Twitter. They now how to set up automated systems to publish to your existing channels. They can also help you organize a plan on how to integrate your site with your social networking profiles. They may or may not be able to do any of the above.
Any other ideas on this?
I just mention because personally, as a web *coder*/developer, I don't do design at all anymore (which is a good thing for you, believe me). Plus, I can't really answer specific questions about your font or your gradient or background image. I *can* make a site function the way it's functionally specified, but I can't physically or mentally come up with an artistic version of the site. That's why I work with web designers and themers.
So when I see a job description that says "we need a web designer who can also create articles" or "we need a web coder who will also do design", etc. I think that someone is definitely going to have a hard time filling that particular position.