| Less generic crap (is genericism a word?). I get that this isn't always possible but the way most job descriptions seem to be written make effectively searching for what I want difficult sometimes. Let's say I want to work with blub in my next job. I search for "blub developer" in my job-board of choice, but I'm met with a lot of noise like this > Software Developer > Required Experience: > Experience with a programming language (i.e. Java, C++, Pascal, Modula-3, PL/I, Brainfuck, Blub) Where the position isn't working with blub, but its been listed under some generic requirement to have programmed in some programming language. Please stop listing stuff like this. Another version of this thats typically bad with enterprise-type positions is dumping every damn Java EE or Microsoft related technology as required or preferred experience whether or not you'll ever use them. Also I'd like to know what id be working on. Often this is stated, but many times its not, typically with an even less descriptive "Software Engineer" title. Id at least like to know what sort of product in working on and if you can ahead of time tell me exactly what the product is thats even better. Some have mentioned thebsalary range and while its great to see that (and a huge time saver) thats probably a pipe dream. I digress for a moment to note one last thing. That the worst part of job searching isn't even these sort of descriptions, but the job boards themselves that seem to ignore search terms in favor of "promoted" positions that match my above complaints. |