|
|
|
|
|
by philwelch
4914 days ago
|
|
That wasn't even my point. My point was that it's good to be able to treat the work history question as a normal question rather than having to try and compete on my ability to spin the answer. That means you still have to have good answers for that question, and for the behavioral questions, but you can just answer them straightforwardly since there are better ways than personal salesmanship to distinguish between different candidates. Around here, we hire technical people based on substance, not salesmanship. What the fuck do you do? |
|
It's part of an interview process that includes an in depth review of your projects and roles, a technical screen, some design questions, et al.
"Wtf do I do"? I don't hire people that become belligerent over or flustered over simple meta level questions.
You might reconsider your negative bias towards "spin", btw... http://www.codinghorror.com/blog/2008/10/the-one-thing-every...