4 ms·
It's an interest thing: if the applicant doesn't even know what type of product you make, then what happens when you bring them in for an interview and it turns
by wallacoloo 9y ago
It's an interest thing: if the applicant doesn't even know what type of product you make, then what happens when you bring them in for an interview and it turns out they just fundamentally don't care about your product? Either (a) they'll turn you down based on that _after_ learning more about your product during the interview, which has wasted both your times or (b) this will get glossed over, they'll work for you for a few months, and then search for a new job after discovering that working on your product gives them no fulfillment.
It's not an ego-driven "only consider the candidates who put in effort specifically to satisfy me" thing. It's more "there's a 50% chance that this applicant who did zero research wouldn't actually be happy in this line of work, whereas any applicant who spends ten minutes of research and then still applies has already decided that this line of work is probably a good fit for them."
Does this justify it for you? Or do you still feel that asking candidates to know generally what your company makes beforehand is unreasonable?
- avip 9y ago[EDITED] I think "knowing what the company does in general" is reasonable. Anything beyond that is on the unjustifiable-impractical plain. First quarter.