3 ms·
What you're saying is how interviews should work: a pure talent evaluation, unaffected by any non-job-related skills. However, in practice, interviews don't nec
by lmkg 15y ago
What you're saying is how interviews should work: a pure talent evaluation, unaffected by any non-job-related skills. However, in practice, interviews don't necessarily work that way. Spending a couple of minutes training on presentation skills can make you much more effective at communicating just how awesome your actual abilities are, far more than the equivalent time expenditure in getting marginally more awesome.
You can pretend that the world is perfect, or you can take steps to deal with the fact that it is not. Now tell me, which of those behaviors would you want from the programmer you want to hire? ;)
- SatvikBeri 15y agoHow often do you hear of a programmer saving a company millions of dollars/thousands of man-hours and receiving no reward for it? All the time! Excellent performance (saving the company ~$3MM) at my last job merited me a 15% raise. Learning and applying negotiation skills made that an 80% raise. Presentation matters.
- 286c8cb04bda 15y agoThe first time I read your comment I thought it was disagreeing with the parent post. Upon thinking about it, I now believe that you are agreeing with him. Right? I'm not trying to criticize your post, but I hope someone could point out why I read it so wrongly -- if there are attributes why make it more likely to be read that way, or if there's something flawed in my perception.
- SatvikBeri 15y agoI am agreeing with the parent and disagreeing with the grandparent post. I think the confusion comes from the "How often do you..." which is frequently used sarcastically-although in my case I meant it literally.