A: When is doesn't describe the job.
I've noticed recently that a lot of the "job descriptions" I receive when contacted about roles are simply list of pre-requisite skills/attributes/competencies/experience. When I reply to the effect that "this isn't a job description, what does the role actually entail?" I get told either that this is all that the client has given them, or that all will be revealed at interview. At this point I tell them to stop wasting their time (and mine).
This seems particularly common among the Wipro/Infosys/Sopra Steria/Zensar/Crisil Indian consultancy recruiters.
Is this a new phenomenon, or have I just noticed it? Or are these not actual jobs at all and the recruiters in question are just trying to harvest my information?
I've noticed recently that a lot of the "job descriptions" I receive when contacted about roles are simply list of pre-requisite skills/attributes/competencies/experience. When I reply to the effect that "this isn't a job description, what does the role actually entail?" I get told either that this is all that the client has given them, or that all will be revealed at interview. At this point I tell them to stop wasting their time (and mine).
This seems particularly common among the Wipro/Infosys/Sopra Steria/Zensar/Crisil Indian consultancy recruiters.
Is this a new phenomenon, or have I just noticed it? Or are these not actual jobs at all and the recruiters in question are just trying to harvest my information?
Comment