You are going to hate everything about this requirement page then: https://www.bunq.com/nl/en/job/
Actually it improved a little bit. Until a few weeks ago you had to sign an NDA to learn what the company actually does.
Things I wish people who write job postings would stop writing
71–80 of 109 posts
Re: Things I wish people who write job postings would stop writing
#72I've been tracking[1] the use of "passionate" in whoishiring threads, really getting out of control. It's now become one of the 10 most frequent terms used in posts. [1] http://www.ryan-williams.net/hacker-news-hiring-trends/2014/...
Everything is on the rise that you're tracking. Which would make me believe there are just more job postings and for all I know the term passionate may actually be on a decline in how often it's use vs how many job listings are made.
You're right, the chart needs some work. The rankings table below show the relative rise better than the chart.
Re: Things I wish people who write job postings would stop writing
#73I totally agree. Ironically I think current economical situation flips the coin. Companies are fighting for developers rather than employees applying for jobs. In rare cases ( google, facebook, twitter, etc. ) these writing actually doesn't exist.
Re: Things I wish people who write job postings would stop writing
#74I've been tracking[1] the use of "passionate" in whoishiring threads, really getting out of control. It's now become one of the 10 most frequent terms used in posts. [1] http://www.ryan-williams.net/hacker-news-hiring-trends/2014/...
I noticed by looking at the top 50 that there's also "passion" as a separate listing, and tracks almost perfectly [0]. [0] http://www.ryan-williams.net/hacker-news-hiring-trends/2014/...
Good catch, I forgot I had them broken out, makes it even more common perhaps, but there could be overlap with posts using both terms.
Re: Things I wish people who write job postings would stop writing
#75Re: Things I wish people who write job postings would stop writing
#76Can you give an example of a good job posting? I try to make our postings as real as possible[1], and would love feedback. 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
I liked the job posting but thought the list of requirements is very specific. JavaScript, Python, and Linux are the only things on that list that look like they should be a deal breaker for you. Everything else can be covered in a soft requirements list such as "have experience with web development (client and server side), relational databases, and queueing/caching". This gives people who have experience with the core of your stack an indication that they fit your main requirements. Of course you might only want people who fit your requirements 100% but I think you're getting into Unicorn territory at that point.
Re: Things I wish people who write job postings would stop writing
#77Earlier quoted context omitted.
back in the day, some clueless manager posted to usenet that he was looking for a coder who could - I swear I'm not making this up! - "write 1000 lines of code per day". I'm sure you can visualize all the responses that were posted.
Now, if they could average minus 1000 lines per day ...
Yes, for almost every existing project I've ever worked on, I had a net negative line of code count per day, and boy did that feel good.
Re: Things I wish people who write job postings would stop writing
#78Among my pet peeves is that when I search for telecommute jobs at Craigslist - which is often the case, as I am a consultant - it gets me posts that say "no telecommuting". It 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 otherwi…
> It 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. There's a workaround for this. Take a few sentences from the job description - some of…
I wonder how effective that is vs going through the middleman. I'd guess if the "end company" is small enough without the bloated HR structure, it's more effective to get in the door by contacting them directly. On the other hand, if it's a behemoth like GE or similar, it might be more effective to go through a middleman to get past clueless HR.
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.
Re: Things I wish people who write job postings would stop writing
#79What I'd really like to see, is a recruiter who actually looked at my resume from beginning to end before contacting me. Finally, just a few minutes ago, I put a vacation response in my gmail account: Dear Friend, Thank you for writing, I'll get back to you soon. If you are an agency recruiter seeking to place me in a job or contract position, please be advised that I find my own work. Please take me off your mailing…
Did it have any effect whatsoever on the flow of spam? (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.)
I learned this the hard way as well.
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).