News for hackers. Stuff that matters.
Re:Crafting the worst interview process in 8 easy steps by moocow01 on Friday January 06, 2012 @03:06AM (#3432501)
I guess at least they told you about the position change. A friend of mine graduated as an engineer, got a job at a top company and on the day he started they told him that there was an organizational shift in the department and he would have to take over for a data entry spot. Same pay but data entry. They said it was temporary (it wasn't) but since he was fresh to the working world he stayed at it for a couple years.
Re:Crafting the worst interview process in 8 easy steps by mwd_ on Friday January 06, 2012 @04:59PM (#3435238)
For my case it was not as bad as data entry. It was a build system job vs. graphics job (I have a grad degree and the equivalent of a few years of work experience), but they had primed me for something specific. Questions like "how do you feel about regularly working until midnight and hounding people you have no authority over who break the build?" did not help.

I assume that they were mostly incompetent rather than evil, but it doesn't matter from the perspective of a company attracting talent.

Many people looking to hire are clueless of this and cannot explain why they have trouble hiring (a guy once simultaneously complained to me that he couldn't find competent programmers and complained that I wouldn't do small, sporadic 3D geometry jobs for $50/hr). I have noticed a common smugness amongst people hiring (despite the fact that many quickly reveal themselves to be of less than stellar technical ability). This is probably a bad attitude in a market where the best talent can quickly get multiple job offers and where not every person hiring is a jerk.

Part of the problem seems to be that many companies get by on hiring cheap workers. In particular they take advantage of students just out of school. That doesn't work very well because it is hard to retain those people, but it appears to be enough to keep many companies afloat.