3 ms·
4 pieces of anecdotical data: 1. I stopped writing good job descriptions when hiring because HR always killed it: they cut mine to half and add their crap all
by AdrianB1 5y ago
4 pieces of anecdotical data:
1. I stopped writing good job descriptions when hiring because HR always killed it: they cut mine to half and add their crap all over. I had open positions for SQL DBAs for 9 months, all candidates were developers in the best case and BI in the worst
2. From time to time I receive calls on LinkedIn with X years of experience required, where X was even 15. When I asked about it (I had more, I was just curious) they said the real number is X/2, but they wanted to cut off people with very low experience that are rounding up.
3. No job description in Europe that I've seen included any useful info on salary. All the discussions in the past 2-3 years ended when I found they were offering below the market and below current level. All this time could have been saved on both sides if at least some range would have been offered. This applies even for positions where they made me 1 offer per week with increasing salary (a few percent) for 2-3 months in a row, which is incredibly stupid.
4. In the past 2-3 years I never saw a job description that looked really professional and interesting. The positions were more interesting than the descriptions.
- perl4ever 5y ago>I had open positions for SQL DBAs for 9 months, all candidates were developers in the best case and BI in the worst Do you think the latter two categories of people could learn the job in nine months?
- AdrianB1 5y agoYes, if they would be interested. We hired one developer and 3 weeks later he said it is not what he was looking for (and I was very open upfront on what the work is, a combination of production DBA and development DBA).
- cutemonster 5y agoWhat's "BI"? Business intelligence?
- AdrianB1 5y agoYes