| ??? 04/12/10 19:16 Modified: 04/12/10 21:33 Read: times |
#175006 - HR shouldn't try to evaluate competence Responding to: ???'s previous message |
The problem here is that HR shouldn't really spend the time trying to figure out competent staff.
They should settle for figuring out if they think the person is trustworthy and reliable, and fork off any decisions about skills to people within the intended work field. Having HR figure out who is a good developer is like having them figure out what is a good processor... Edit - had to fix some spelling errors. |
| Topic | Author | Date |
| Do employers know what they are asking for? | 01/01/70 00:00 | |
| Of course, they don't | 01/01/70 00:00 | |
| often enough, they don't know what the acronyms mean | 01/01/70 00:00 | |
| HR shouldn't try to evaluate competence | 01/01/70 00:00 | |
| Well at my new job | 01/01/70 00:00 | |
| I stumbled over this laughable example | 01/01/70 00:00 | |
| Really important to protect company names | 01/01/70 00:00 | |
| Agency != Employer | 01/01/70 00:00 | |
| Not always the case | 01/01/70 00:00 | |
| Better to just ask for any additional skills | 01/01/70 00:00 | |
| what I have found is ... | 01/01/70 00:00 | |
| non-technical MBAs in technical management positions | 01/01/70 00:00 | |
| Maybe not ... | 01/01/70 00:00 | |
| The other issue.. | 01/01/70 00:00 | |
| Maybe ... | 01/01/70 00:00 | |
Well ... I don't know the answer ... | 01/01/70 00:00 |