Things I wish people who write job postings would stop writing
- Random words that adds nothing: 'professional', 'talented', 'passionate', 'awesome'. "hmm, maybe I'm not awesome enough for this position" - said nobody ever
- Describing your company like it just cured AIDS (if you company actually just cured AIDS, I will allow it). I only want to know what your company _actually_ does.
- Explicitly writing that the hired person will have to work a lot. "let's hire someone to do nothing most of the time" - said no company ever
What you should write and you are (probably) not writing:
- What are some real tasks / problems I might work with on a daily basis? I find it hard to be interested on positions that only mentions "you'll develop stuff". There's a lot of stuff out there, please be clear.
- In case of remote positions, is the employee supposed to live near the company or can she be on the other side of the planet?
108 comments
[ 3.0 ms ] story [ 229 ms ] threadIt is quite cruel that the name of the employer is usually not provided: "We are a hot startup in the cloudspace" rather than "Example.com is a hot startup in the cloudspace". This has the result that I apply to a lot more companies than I otherwise would, because there is no way I can learn more about the company _before_ apply.
See if you can find a recording of the original Apple Computer radio ad. It was on their very first developer CD - "You can change the world!"
Well I expect Apple did, but now everyone says they're going to.
I've gotten to the point that when I see an ad seeking a "rockstar coder" I just don't apply.
How about a job posting that's looking for someone with more than ten years experience?
Someone whose products got reviews in the trade press, or sold well?
There's a workaround for this. Take a few sentences from the job description - some of the non-standard ones - and google for them. Frequently, you'll see the company's job page in the results as the first hit. From there, you can usually even contact them directly, and skip the recruiter middleman.
In my (a few years out of date) experience, it got me hits about 50% of the time.
Actually I used to do that for my own web pages, to find scraper sites. Funny it didn't occur to me.
I'm struggling with these decisions currently, as I see the same position posted by multiple middle men, as well as the "final client" directly, and sometimes it's difficult to figure out the best way to handle it.
I've only worked for one company large enough to have a dedicated HR team, and they don't seem clueless to me so far.
[1] http://www.ryan-williams.net/hacker-news-hiring-trends/2014/...
[0] http://www.ryan-williams.net/hacker-news-hiring-trends/2014/...
It's not sharp on the edge but it _is_ pointy.
(Apple has only supported it for about three months now.)
When MS first shipped C++ for windows, quite commonly the recruiters wanted candidates with five years of windows C++ experience.
Has anyone ever had a favorable experience working with a hiring company or recruiter that is especially particular about how many years of experience a candidate has in some technology? Exactly how much a programmers knows isn't directly dependent on how long the programmer has been working with the tool. There is such a thing as "1 year of experience 5 times".
ozzy osbourne basically was holding out for rails 3
Specifically, that I'd probably hate to work there.
I have had some experiences with alcoholics I do not wish to repeat.
A recent employer was a raging alcoholic, I mean to the point that there were hundreds of beer bottles in the recycling bin, one-liter bottles of expensive hard liquor presented on display in the break room. The only room in the whole office that wasn't totally trashed, held a pool table that no one ever actually used, that had several of the kinds of mirrors that liquor distributors give to bars.
I didn't clue in to this right away. However the guy bet the farm on a technology without looking into whether that technology actually worked. When I had not gotten it working after just two hours, he started raging at me about how it was all my fault that it didn't work. This for a technology I'd never heard of, and would not touch with a hot rock now that I have experience with it.
I finally packed up my stuff, broadcast a terse, angry letter of resignation to the entire company, to the effect that I don't work for alcoholics, then walked out with no advance notice at all.
> When I had not gotten it working after just two hours, he started raging at me about how it was all my fault that it didn't work.
This is how most mid-sized non-technology companies operate when it comes to making technical decisions. If you have a couple of months to spare (the guy is verbose), I recommend reading the Gervais Principle[0].
[0] http://www.ribbonfarm.com/the-gervais-principle/
I like to stay awake for days on end, writing. I mean like essays, articles and stories.
Sometimes I even write poetry!
"Professional" strikes me as an overall requirement. I can't imagine companies are looking for unprofessional employees.
"Talented" is rather vague, and isn't the presumption that the candidate is talented anyway?
"Passionate" could be applied to a specific thing (e.g., technology, like "passionate about SPAs"), so that one makes sense.
"Awesome" is in the same category as the first group, I think.
Do you have any examples of how "professional", "talented", and "awesome" can be genuinely useful?
"rockstar" or "ninja"=naive or gullible
"hybrid"=1 to do work of previous >1
These are the people I would not work for even if they paid me <i>enough</i>; considering they're using silly buzzwords to attract warm bodies(not = talent) assures me their "competitive wage" puts the starting salary right on par with 'fry cook'.
Rock stars blow their royalties and ticket sales up their noses, sleep with groupies, trash hotel rooms and die young.
I'm sure you can visualize all the responses that were posted.
[1] https://code.google.com/p/gitinspector/
Ninjas spend 99% of their time practicing, but when they do work, you never see them. And you know them by their trail of bodies.
Neither of these sound like successful software developer case studies.
- 'Interested? Email me at ted@coolstartup.com, include hackernews in subject line'
Finally, just a few minutes ago, I put a vacation response in my gmail account:
(I was nominally responsible for a Clearcase installation for six months in 2001. I mentioned it on my CV in 2002. I still get the occasional ping from those last, last few Clearcase shops, desperate for someone who will admit to ever having touched it.)
If you've worked with some technology or product, but don't ever want to work with it again, don't mention it in your resume.
I mentioned doing some ColdFusion work because, well, that's what I did as part of a previous job, but when I started looking for a new job, I quickly found I wanted to take that out.
Of course, if word gets out you're a software developer looking for work, there are a whole slew of recruiters that will spam you for anything that even remotely involves computers. It's been 2-1/2 years since I was looking for work and I still get a couple e-mails a week spamming for jobs like a Linux Admin in Detroit or a Data Analyst in St. Louis (I live in Virginia and never had any intention of moving).
The recruiters seem to be catching my drift in a rather oblique way, in that just since yesterday, they've been sending me inquiries about jobs in Portland, Maine.
I cannot tell if that's a pun or typo..
Did you actually post that anywhere?
I got 11 solid leads, and 2 of those turned into hires.
More here: http://ceklog.kindel.com/2011/10/27/my-best-hiring-stunt-to-...
I just posted your job description to Craigslist.
This is why people who think it matters stay constantly confused at common turns of phrase and try to correct them, they've completely lost the forest for the trees.
I think you're underestimating the number of people who tell themselves things like that.
http://joblint.org/ - Test tech job specs for issues with sexism, culture, expectations, and recruiter fails.
Library source: https://github.com/rowanmanning/joblint
I can hardly think of a better way to advertise that you only want young people to apply than to advertise for a guru rockstar gamechanging ninja who is awesome and wants a vague job description.
Clearly this was a lose-lose proposition.
Hilariously, I naively took them at their word and described amongst other observations how their application used far too many HTTP requests (i.e. they weren't using concatenation) and that the page size was phenomenally large.
Needless to say I got no response.
Another time an in-house recruiter for a company that creates a light-blue VOIP client that everyone uses, mentioned that there were free soft drinks and that the executive management were really down to earth. At which point I moved the phone away from my mouth, took a breath and regained my composure.
The level of detail goes both ways, though. The vast majority of people who apply don't even submit a pgp resume, which gives the impression that they didnt read the job description.
[1]: http://www.indeed.com/viewjob?jk=66c8368e9c756e78
[1] http://webcache.googleusercontent.com/search?q=cache:5YIQ01r...